{"sections":[{"slug":"get-started","title":"Get started","pages":[{"slug":"introduction","title":"Introduction","summary":"FluxNative builds real iOS and Android apps from a description, a Figma flow, or a template. You get an Expo project you can preview, edit, build, publish, and export."},{"slug":"quickstart","title":"Quickstart","summary":"Go from sign-up to an app running on your phone: describe it, review the preview, ask for a change, and build an APK you install with a QR code."},{"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."},{"slug":"start-a-project","title":"Start a project","summary":"Four ways to begin: describe the app, answer a short guided brief, fork a template, or import a Figma flow. Each creates a project in the current organization."}]},{"slug":"build","title":"Build your app","pages":[{"slug":"the-workspace","title":"Tour the workspace","summary":"A project opens in three columns: the project panel (App, Design, Code), the device preview, and the assistant chat, under a project bar with Connections, Export, Publish, and Build."},{"slug":"work-with-the-assistant","title":"Work with the assistant","summary":"Send requests with images or files attached, answer the assistant's questions, stop or undo a turn, and keep several conversations on one project."},{"slug":"writing-prompts","title":"Write better prompts","summary":"The assistant builds what you describe. Name the people, the job, and the screens; change one thing at a time; and say what to keep."},{"slug":"preview","title":"Preview","summary":"The preview is a web build of the same Expo project in a device frame. Pick a route or device, open the console, switch light and dark, rotate, or reload."},{"slug":"app-structure","title":"App structure","summary":"The App tab shows the app as it describes itself: the screens the assistant planned and built, the navigation tree, and shared components."},{"slug":"design-tokens","title":"Design tokens","summary":"The Design tab changes brand color, corner radius, density, type scale, typefaces, and whole directions without spending a turn. Each change is saved to the project source."},{"slug":"edit-the-source","title":"Edit the source","summary":"Open any file in Code, edit it yourself with autosave, search the project, or highlight lines and send them with a request."},{"slug":"revisions","title":"Revisions and undo","summary":"Every turn that changes the project lands as one revision. Undo puts the previous one back. Parallel conversations merge instead of overwriting each other."},{"slug":"app-icon","title":"App name and icon","summary":"Rename the app and set its launcher icon from the project bar. Upload an image or generate options; a generated icon is not applied until you pick it."},{"slug":"checks","title":"Checks","summary":"Type and native checks run against the project and stay visible in the workspace. A failure leaves the revision in place so you can repair it."},{"slug":"export","title":"Export the project","summary":"Export downloads the current Expo project as a .zip, so you can open it in another editor or build it yourself. The app is not locked to FluxNative."}]},{"slug":"designs","title":"Designs and templates","pages":[{"slug":"figma","title":"Import from Figma","summary":"Paste one frame link or sync the open file with the plugin. You confirm the screens, and the assistant builds those screens from the real frames."},{"slug":"templates","title":"Templates","summary":"A template is a complete working app. Forking it creates an editable project in your organization, with a setup checklist for the steps that remain."}]},{"slug":"connect","title":"Connect services","pages":[{"slug":"connections","title":"Connections","summary":"Connections is where a project keeps its backend, in-app purchases, and secret vault. You enter credentials once; the assistant uses them without seeing the values."},{"slug":"supabase","title":"Supabase","summary":"Save the project URL and an account access token. The assistant then creates tables, row-level security, Edge Functions, and function secrets."},{"slug":"firebase","title":"Firebase","summary":"Paste the service-account JSON once. The assistant reads the Firebase config, tests security rules before publishing them, and can register Android SHA fingerprints."},{"slug":"cloudflare","title":"Cloudflare","summary":"Save the account ID and an API token so the assistant can deploy Workers and use R2 and Queues without the token appearing in chat."},{"slug":"your-api","title":"Your own API","summary":"Point the project at an HTTP or GraphQL API you already run. The credential stays on the server; the app does not embed it."},{"slug":"in-app-purchases","title":"In-app purchases","summary":"Save a RevenueCat v2 secret key. The assistant discovers the project, its apps, and their public SDK keys, then wires subscriptions into the app."},{"slug":"secrets","title":"API keys and secrets","summary":"The vault holds backend keys by name. The assistant sees the name and a one-line description, never the value, and delivers secrets to your backend."}]},{"slug":"native-builds","title":"Build for devices","pages":[{"slug":"builds-overview","title":"Native builds overview","summary":"A native build compiles one pinned revision of the project into a signed APK, App Bundle, or IPA on FluxNative's build workers. It is charged only when it succeeds."},{"slug":"android-builds","title":"Android builds","summary":"Build a signed APK to install on phones, or a signed App Bundle for Google Play. Install an APK with a QR code, or send an App Bundle straight to Play's internal testing track."},{"slug":"android-signing","title":"Android signing keys","summary":"Every Android build is signed with the app's key. Create one in FluxNative or register your existing keystore, copy its SHA fingerprints, and never replace it after release without a plan."},{"slug":"ios-builds","title":"iOS builds","summary":"Build a signed IPA without a Mac and send it to TestFlight. You need an Apple Developer account, a distribution certificate, and this app's provisioning profile."},{"slug":"ios-signing","title":"iOS certificates and profiles","summary":"How to create the Apple distribution certificate and an App Store provisioning profile, and where each one goes in FluxNative."},{"slug":"versions-and-build-numbers","title":"Versions and build numbers","summary":"Stores see two numbers: the version customers read, which you control in the project, and a build number, which FluxNative assigns and never reuses."},{"slug":"install-on-device","title":"Install and test on a device","summary":"Install an Android APK by scanning a QR code, or add testers to TestFlight and Play internal testing. Check native features the preview cannot run."},{"slug":"build-failures","title":"Fix a failed build","summary":"Read the reason on the build, use Fix with AI for code problems, fix signing in Publish and Build, then retry. Failed builds are never charged."}]},{"slug":"publish","title":"Publish to stores","pages":[{"slug":"publishing-overview","title":"Publishing overview","summary":"The path from a finished build to the App Store and Google Play: store accounts, the readiness checklist, testing uploads, listing, approvals, and the production release you complete in the store consoles."},{"slug":"connect-store-accounts","title":"Connect store accounts","summary":"Connect the organization's App Store Connect API key and distribution certificate, and a Google Play service account. Only the owner can connect them; every app in the organization can use them."},{"slug":"store-readiness","title":"Store readiness checklist","summary":"Readiness lists every Apple and Google step between you and a release, who owns it, and whether it is done. Some steps FluxNative can fix; the rest link straight to the right console page."},{"slug":"testflight","title":"Release to TestFlight","summary":"Send a signed IPA to TestFlight from the Build panel, wait for Apple to process it, then add testers in App Store Connect."},{"slug":"google-play-testing","title":"Google Play testing","summary":"Send an App Bundle to Play's internal testing track, add testers, and meet Google's closed-testing rule before production."},{"slug":"store-listing","title":"Store listing","summary":"Write the title, subtitle, descriptions, keywords, and release notes in Publish, with a drafted first version. Saving a new listing clears approvals of older snapshots."},{"slug":"production-release","title":"Production release","summary":"Approve an exact build for production, attest compliance, set the production target, then submit for review in App Store Connect or roll out in Play Console."}]},{"slug":"teams","title":"Teams and billing","pages":[{"slug":"organizations","title":"Organizations and roles","summary":"Projects, credits, and store accounts belong to an organization. Four roles with editable permissions decide who can build, publish, invite, and pay, and developers and viewers can be limited to selected apps."},{"slug":"manage-apps","title":"Manage your apps","summary":"Find, sort, and filter apps in My apps, jump between them with the app switcher, and restore a deleted app from Recently deleted for 7 days."},{"slug":"credits-and-plans","title":"Credits and plans","summary":"Credits belong to the organization. Chat turns and icon generation spend them; a native build spends them only when it succeeds. Billing shows the plan, the balance by source, credit activity, and invoices."},{"slug":"remote-mcp","title":"Connect an editor","summary":"Connect Claude Code, Codex, Cursor, VS Code, opencode, or Antigravity to one project over MCP, so an external coding agent reads and edits the same source."},{"slug":"your-account","title":"Your account","summary":"Your profile holds the name, title, and photo teammates see. Password, Google and GitHub sign-in, and active sessions are managed from the same place."},{"slug":"settings","title":"Notifications and settings","summary":"Choose which events notify you, pick a light, dark, or system theme, rename the organization, and manage Figma and editor connections."}]},{"slug":"help","title":"Help","pages":[{"slug":"troubleshooting","title":"Troubleshooting","summary":"Fixes for the problems people hit most: a preview that will not compile, a locked preview, a turn that stops, conflicts, failed builds, Figma limits, and credits."},{"slug":"faq","title":"FAQ","summary":"Short answers about ownership, code, backends, stores, pricing, and teams."},{"slug":"get-help","title":"Get help","summary":"Search the in-app help articles or send a request to support. Replies stay under My requests."}]}]}