How FluxNative works
The few words the product uses, from organization to release, and what happens during one turn of the assistant.
Updated Oct 15, 2026
The words
| Word | Means |
|---|---|
| Organization | Owns apps, credits, the plan, members and store accounts. |
| Project | One app: source, preview, chats, connections and builds. |
| Turn | One request and the assistant's work on it. |
| Revision | A saved state of the source. Each turn that writes files is one. |
| Build | A signed APK, App Bundle (AAB) or IPA. |
| Release | A build sent to TestFlight or Google Play, through review to the public. |
One turn
- You send a message, with images or files if you like.
- The assistant plans, writes the screens and services, then compiles the preview and tests it in a browser of its own. Your preview follows along until you click it.
- It may stop to ask you a question. Answer in the chat and it continues.
- Its changes land as one revision you can undo. Suggested next steps appear as chips; picking one fills the message box without sending it. A chip to connect a backend or RevenueCat opens Server on its form instead: only you can enter the credentials, so it never starts a paid turn.
Good to know
- Everything reads one source: the preview, Design, Code, builds and the exported project. There is one
.env, no separate production config. - Credits belong to the organization. Generation spends them; a native build spends them only when it succeeds; forking a template spends none. See Credits and plans.
- Roles decide who can build, connect, publish and pay. See Organizations and roles.
Did this page help?