This glossary defines the terms that FlutterFlow uses, grouped by area, and notes terms that are easy to confuse.

FlutterFlow and your app

The following table defines the terms for FlutterFlow itself, your app, and the places where you work:

Term	Meaning	Not to be confused with
FlutterFlow	The app builder where you describe the app that you want and the agent builds it.	FlutterFlow Studio
FlutterFlow Studio	FlutterFlow’s visual builder for designing screens and logic by hand.	FlutterFlow
app	What you build and what people use. Some labels use the word project instead, such as Project Settings and Project id.
Overview	The area that opens first in an app. It shows your app’s threads and recent changes alongside your running app, plus the Road to launch card.	Releases › Overview, the first section of Releases
Project Settings	The area where you manage an app’s General details, Team, Connections, App stores, Emails, and Store pictures.
Theme	The account menu row where you choose light (sun), dark (moon), or your system setting (screen) for FlutterFlow itself.	Your app’s look

Building with the agent

The following table defines the terms for describing your app and working with the agent:

Term	Meaning	Not to be confused with
prompt	Your initial description of the app that you want. A thread shows it as Your brief.	A request you send in a thread later
first version	The app that the agent builds from your prompt in your app’s first thread (initially named First version).	A numbered store version
Initial generation	The lightning icon next to the first version’s thread name in the thread switcher. Point to the icon to see this label.
the agent	What builds and changes your app when you ask.
thread	One idea or change that you work on with the agent, with its own copy of your app and its own data.	Your app
turn	One round of the agent’s work after you send a message. When the turn ends, you can open its Summary. To stop a running turn, click Stop current turn.	A thread
card	A request that the agent shows above the message box when it needs your input. Its label shows its type, such as Question, Proposal, Private (a key), Connect (a service to connect), Setup (a service’s settings), or Approval (a service action awaiting your approval).
signal	A chart in the agent’s reply that shows how a number changed. While the agent waits for your choice, the chart also appears on the Question card above the message box.

Preview and push

The following table defines the terms for testing changes in a thread and moving them into your app:

Term	Meaning	Not to be confused with
your app	The app that you use and share. Pushing a thread adds its changes to your app, and Releases builds versions from it.	A thread’s Copy of your app
Copy of your app	The isolated copy of your app that a thread runs. Changes in a thread stay in this copy until you push them.	Your app
Preview	Your app running beside Overview or a thread. It appears as a tab above your app in a thread, and as the label above your app on Overview.	The phone previews in Releases › Store listing, which show how your app appears in the stores
push	Moving a thread’s changes into your app with Push to your app. Everyone with your app’s link gets the change, and the thread stays open. The thread shows Pushing to your app during the push and In your app when the push finishes.	Sharing a link or sending a version to the stores
Changes	The tab beside a thread’s preview that lists the thread’s changes and marks whether each one is in your app.

Backend, data, and connections

The following table defines the terms for what your app stores and the services that it calls:

Term	Meaning	Not to be confused with
Backend	Everything your app stores: table records, signed-up people, saved files, and secrets.
Activity	The first section of Backend, listing changes to your app’s backend and the threads they came from.
live data	Your app’s real data in Backend. Saving a record here updates your app for everyone immediately.	This thread’s data; Live in Releases
this thread’s data	A thread’s isolated copy of the data on its Data tab. Edits here affect only the thread, not your app.	Live data
starter data	The accounts and records that every new thread starts with, managed in Backend › Starter data.	Live data
builder account (You)	The test account signed in to the preview. It’s listed in Backend › Starter data, and records mark it as You.
People (in Backend)	Everyone who has signed up for your app.	Your app’s teammates
Files (in Backend)	Photos and documents saved in your app.	Files in a version’s menu in Releases, which holds that version’s built app files
Secrets	Hidden private keys that your app uses to call external services.
backend usage	How much of this month’s backend allowance your app has used, shown in Backend › Usage.	Your allowance for the agent
Connections	The services that your app uses, managed in Project Settings › Connections. Your own accounts, which the agent uses as you in chats, are in Account › Connections. Store accounts are separate: you connect them in Account › App stores and choose one for each app in Project Settings › App stores.

Sharing and releases

The following table defines the terms for sharing your app and launching it on the App Store and Google Play:

Term	Meaning	Not to be confused with
share link	A link from Share › Link that opens your app (or one thread’s copy of it) for anyone with the link.	A push
Road to launch	The checklist from your first version to the stores. Overview shows it on a card until one week after you finish the last step, unless you select Hide from Overview.
Releases	The area where you connect store accounts, test your app, and submit versions for review.
Up next	The list in Releases showing your next actions and remaining setup.
Set up, Test, Review, Live	The four stages that each store moves through in Releases.	Live data
version	A numbered build of your app for the stores.	The first version
test build	A build that you install on your own phone from On your phone in Releases: a downloadable app on Android, or a TestFlight build on iPhone after you connect your Apple account.	An Android version sent to testers
send to testers	Uploading a version to TestFlight or Google Play for testing. Testing is separate from public release.	Submit for review
submit for review	Sending a version to Apple or Google for store review.	Send to testers
Go back to this version	The button at the bottom of a version’s drawer that rebuilds that version so that you can test and submit it again, leaving your app and current store releases unchanged.
Store listing	What people see about your app in both stores and on their phones.

Teammates, plans, and allowance

The following table defines the terms for the people who you build with and your budget for the agent:

Term	Meaning	Not to be confused with
Team	Everyone working on or invited to your app in Project Settings › Team (also shown under People in Share).	People in Backend, the people who use your app
role	What a teammate can do in your app: owner, developer, billing, or viewer.
invitation	A single-view link, valid for seven days, that adds someone to your app’s team with a chosen role.
allowance	Your budget of agent work. Plan & usage shows how much remains and when it resets.	Backend usage
refill	A paid top-up that adds a week of usage immediately, available on eligible plans.
Plan & usage	The account menu page for your plan, allowance, refills, and billing.	Backend › Usage