Which FlutterFlow builder is this?

FlutterFlow Studio is the visual builder previously called FlutterFlow. Existing visual projects stay in Studio.

Studio lets you place interface elements and choose what happens when a button is pressed. It uses Flutter to generate the app. The company now also offers a separate prompt-first builder called FlutterFlow. The vendor says projects cannot currently transfer between the two.

What can you learn from a list and a detail screen?

Use a volunteer shift list to check navigation and fit before deciding how to save anything. Studio’s Preview is useful for layout and navigation. It does not verify Firebase sign-in, Firestore data or API calls.

Choose a disposable example
Start a new sample project with only invented shifts. Verify it has no real records, live accounts or external connections before opening Preview. Use paper if you cannot confirm the setup.
Give the button one action
Put two fictional shifts on the list. Make the morning shift open a detail page that shows its name and time. Leave sign-in, saving, notifications and payments out of this exercise.
Check the route and the layout
Open the morning shift, check that its details match, then go back to the two-item list. Try a narrow and a wide layout in Preview. This check covers screen behavior. Check a real device separately if you will release a phone app.

Where will real shift sign-ups and accounts live?

Studio can connect to Firebase or Supabase for shared records and sign-in. The rules on that service determine which records each account can read or change.

When you need a working sign-up, choose a separate test project at the service that stores the records. Studio’s additional development environments can point to separate Firebase or Supabase projects when your plan supports them. A different editor branch or preview address alone leaves the underlying connection unchanged.

Before starting Test Mode or another functional run, verify the selected database and sign-in project actually use test records and accounts, and that outgoing email, payments and other integrations are disabled or test-only. If you cannot check that, stay with the paper or disconnected layout exercise.

How do people get the finished app?

Studio can publish a web app at a web address. For a native phone release, set up the appropriate Apple or Google developer account and follow that store’s release process.

Enable web support and verify the web layout and integrations before publishing. A phone layout preview cannot prove that a native build works on the target device. The web host delivers the compiled screen code, while your chosen data service handles the app’s shared records.

Which plan lets you take the code with you?

The public Studio matrix puts source-code downloads on Basic and higher. The US monthly Basic price was US$39 when checked on November 12, 2026. Free includes the visual builder and web publishing on a Studio subdomain.

Pro adds a separate development environment beyond the default and the option to push project code to GitHub. Check the current matrix for plan, team and AI limits. The public plans share an AI allowance across FlutterFlow and Studio. Database, hosting and app-store costs can be separate.

The downloaded Flutter project gives you source files and assets to maintain. Keep backups and migration access for the database, files and user accounts separately. Before pushing or sharing the code, inspect any generated server function files and remove or exclude private values from what you share. Studio says a private value used for a private API call can appear in those files. Before trying a downloaded copy, verify its service destinations. The code export does not move the records or create a new test backend.