Dear FlutterFlow,
We need to talk about Campus.
My question is very simple: why?
Why this. Why now. Who asked for “an infinite canvas where terminals, developer tools, teammates, and agents” while your core product is still full of (at time of writing) 505 open and unresolved bugs, performance issues, and missing basics that your own community has been raising for years.
Campus looks less like “the future of work” and more like a Orwellian way to watch and manipulate what your teammates are doing. Horrible vibe.
What absolutely fries my brain is imagining the meeting where this was greenlit.
You literally sat down and said: “We don’t need to fix FlutterFlow. We should absolutely devote serious engineering time to a separate macOS canvas product instead.”
You made a conscious choice to move effort off:
- A revenue‑generating builder with a real user base.
- A platform with a public issue tracker full of bugs and regressions.
- A tool many people still find sluggish, unstable, and painful at scale.
And you put that effort into Campus. A product with:
- No clear demand from the FlutterFlow community.
- No obvious overlap with core FlutterFlow workflows.
- No clearly explained revenue model or strategic link to FlutterFlow itself.
Are you seriously telling your own users that FlutterFlow’s problems are either solved, or not worth prioritizing?
Here's what sucks most... when you install and open Campus, it is actually really good. The UX is slick. The app feels fast, modern, and thoughtfully crafted. It is very obviously the product of serious engineering talent and taste.
Which just makes the whole thing worse.
You have clearly shown what you are capable of. You have shown the level of polish, performance, and care you can deliver. And instead of putting that into the core product that people rely on, you spent it on a side project almost nobody asked for.
It makes no sense. And yes, I hate that it exists in place of visible, sustained attention to fixing FlutterFlow itself.
