FlutterFlow
Build cross-platform mobile apps visually
4.4•43 reviews•3.2K followers
Build cross-platform mobile apps visually
4.4•43 reviews•3.2K followers
Create beautiful UI, generate clean code, and deploy to the app stores or web in one click. Fully extensible with custom code.
This is the 10th launch from FlutterFlow. View more
Campus
Launching today
Campus gives builders a shared space to build with teammates and AI agents. Keep your repo, terminal, project knowledge, conversations, and agent work together in one persistent workspace, instead of scattering context across Slack threads, docs, tickets, canvases, and one-off AI chats. Campus is organized around the thing you are building, so humans and agents can pick up where the work left off.
Free
Launch Team
Congratulations on the launch! Qq: as rooms and projects pile up, does the canvas itself start to become the thing you have to navigate e.g. the same clutter, just in one place? Curious how it holds up once there's a lot on it.
FlutterFlow
@alieksia Thanks! And yes, we noticed things cluttering up a bit if you only have a singular space with everybody on it.
For this, we created rooms - they let you organize work in multiple canvases! Besides that, rooms also act as a nice collaboration boundary. You can choose who can access rooms and collaborate with any set of people!
@norbert1 Thank you for your reply! That makes sense. One thing I'm trying to understand: how is this different from something like Miro? They also do infinite canvas, boards, and access control. Is the real difference that your canvas runs live things like terminals, browsers, agents actually doing work rather than static content?
FlutterFlow
@alieksia yeah exactly. Campus is for the full work cycle, brainstorming, implementing and testing.
Jotting down notes and planning with colleagues in the morning, pulling coding agents right into Campus to implement said notes and reviewing work by using the built in web browser - all right within Campus!
FlutterFlow
@alieksia great question! Like Norbert said, rooms help but also something about it being arranged in 2D makes it easier. And lastly, the whole canvas is searchable!
One space for humans and agents is the right direction, the tab-switching between "my work" and "agent work" is real overhead. How do you handle permissions, can an agent touch anything a human can, or are there locked lanes?
FlutterFlow
@vladimir_iudin yeah exactly one of the core pillars is that the agent can do anything a human can. More specifically, Campus ships with a CLI + a skill which an agent can use, so everything is just a tool call from your agent, gated by your agent's own permission management.
@norbert1 Huh, so the workspace itself stays dumb and all the gating lives in the agent's permission config. That inverts how I'd have built it, I'd have put locks on the workspace side by default. Makes sense for a CLI-first setup though. Thanks Norbert.
FlutterFlow
@vladimir_iudin that's actually good insight!
We do have a couple of features cooking up in that area (remote workspaces), but a local sandboxed workspace is definitely something that could be interesting for Campus as well! Thanks for the feedback :)
I've played with visual app builders before, but the extensibility with custom code is a big plus. How does FlutterFlow handle complex state management or third-party library integration?
FlutterFlow
@aymnart hey Aymen! This particular launch is for our new tool Campus, an infinite canvas for organizing your work (including FlutterFlow!). Hope you can check it out.
For FlutterFlow, I'd recommend checking out our YouTube channel for tutorials on building complex apps!
FlutterFlow
@aymnart you can use FlutterFlow (and Designer) INSIDE of Campus, alongside your other agents and tools!
AISA AI Skills Test
the context-switching problem is real, especially when you've got agents running across different tools that don't share state. curious whether Campus handles agent-to-agent handoffs — like when one agent's output needs to feed into another's context without manual copy-paste.
FlutterFlow
@ozandag Campus is built to be a sandbox. Every tile has a dedicated API for the agent to interact with. If you want agents to collaborate, just tell them! They will be able to figure out the details :)
FlutterFlow
@ozandag let us know if you have any other questions!
This feels like a step beyond AI chat by giving agents a shared workspace instead of isolated conversations. I'm curious how well it handles long running projects with multiple contributors.
FlutterFlow
@tumblar_kevin yes the sharing of context across agents on the same projects is one of the most crucial pieces that was missing for us. We've had no issue with long running projects (relying on git in most cases) but eager to hear how it works for you!
Love to see more connections between human and AI. Wondering whether other messaging tools are also supported as I dont use slack that much. And why do you folks pick slack?
FlutterFlow
@pjsu largely because we are Slack native - this was initially built for our team to develop, so we wanted it to feel familiar. What types of messaging tools would you like to see?
I agree that most of the pain in juggling AI agents is rebuilding the mental map every time you switch tools. How Campus handles version history once a room gets busy, if an agent makes a change overnight, is it easy to see what happened and why?
FlutterFlow
@mshen316 great question! We always defer to git for version control, since we think it's the best technology for the job. So your agents can run overnight and provide you a visual of what they did, but you'll always be able to view git as the source of truth for its changes. At least that's what we'd recommend!