{"slug":"how-it-works","title":"How FluxNative works","summary":"The words FluxNative uses and how they fit together: organizations, projects, conversations, turns, revisions, preview, connections, checks, builds, and releases.","body":"Most of the product follows from a handful of ideas. Knowing them makes the rest of the documentation shorter.\n\n## The pieces\n\n| Term | What it means |\n| --- | --- |\n| **Organization** | Owns projects, credits, the plan, members, and store accounts. Every account has a personal one. |\n| **Project** | One app: its source, preview, conversations, connections, and builds. |\n| **Conversation** | A chat thread inside a project. A project can have several. |\n| **Turn** | One request and the assistant's work on it, from your message to its reply. |\n| **Revision** | A saved state of the source. Each turn that writes files lands as one revision. |\n| **Preview** | A web build of the same project, shown in a device frame. |\n| **Connection** | A backend, purchases provider, or named secret the project can use. |\n| **Check** | Type and native checks that run against the source and report problems. |\n| **Build** | A signed native artifact: APK, App Bundle (AAB), or IPA. |\n| **Release** | A build on its way to TestFlight or Google Play, with its listing and approvals. |\n\n## What happens during a turn\n\n1. You send a message, optionally with images or files attached.\n2. The assistant reads the project as it was when the turn started. It plans, then writes files: routes, screens, components, and services.\n3. It compiles the preview and drives it to check its own screens. While it does, the preview is locked to you.\n4. It may stop and ask you a question when a requirement is unclear or a choice is risky. Answer in the chat to let it continue.\n5. When the turn ends, its changes merge into the latest source as one revision, and the chat lists the files it changed.\n\nAfter a turn, the chat may suggest next steps as chips. Picking one writes that request into the message box. It does not send it, because the step usually needs a detail only you have.\n\n## Source is the single truth\n\nEverything reads the same source. The preview compiles it, **Design** edits values inside it, **Code** shows it, builds sign it, and **Export** downloads it. Nothing is stored beside the source that the exported project would miss.\n\nThe project has one environment and one `.env` file. There is no separate development and production configuration to keep in sync.\n\n## Credits, briefly\n\nCredits belong to the organization. Generation spends them. A native build spends them only when it succeeds. Forking a template does not spend them. See [Credits and plans](/docs/credits-and-plans).\n\n## Who can do what\n\nRoles in the organization decide who can build, connect services, publish, and pay. See [Organizations and roles](/docs/organizations).","sectionSlug":"get-started","sectionTitle":"Get started","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"quickstart","title":"Quickstart"},"next":{"slug":"start-a-project","title":"Start a project"}}