{"slug":"faq","title":"FAQ","summary":"Short answers about ownership, code, backends, stores, pricing, and teams.","body":"## Do I own the code?\n\nYes. The project is standard Expo and React Native in TypeScript. [Export](/docs/export) downloads all of it at any time.\n\n## Is the app native?\n\nYes. Builds are signed native binaries: APK and App Bundle for Android, IPA for iOS. The browser preview is a web build of the same source, used for review.\n\n## Do I need to know how to code?\n\nNo. You can build entirely in chat and the Design tab. If you do code, the full source is open in **Code** and through [Connect an editor](/docs/remote-mcp).\n\n## Which backends are supported?\n\nSupabase, Firebase, Cloudflare, and any HTTP or GraphQL API you run, plus RevenueCat for in-app purchases. See [Connections](/docs/connections).\n\n## Can the assistant see my API keys?\n\nNo. It sees each secret's name and one-line description, never the value. Values are stored encrypted and delivered to your backend on the server.\n\n## Do I need a Mac for iOS?\n\nNo. FluxNative compiles the IPA. You do need an Apple Developer account, a distribution certificate, and a provisioning profile for the app. See [iOS builds](/docs/ios-builds).\n\n## Can FluxNative publish to the App Store and Google Play?\n\nIt builds the signed binaries, uploads them to TestFlight and the Play internal testing track, and tracks the checklist, listing, and approvals. The production submission itself is completed in App Store Connect and Play Console, and review stays with Apple and Google. See [Publishing overview](/docs/publishing-overview).\n\n## Can FluxNative submit my app for App Store review?\n\nIt prepares everything up to that point: the signed build on TestFlight, the listing text, the checklist, and the approvals. You select the build and submit in App Store Connect, which takes a few minutes. See [Production release](/docs/production-release).\n\n## How long does a first store release take?\n\nBuilding and uploading take minutes. The long parts are the stores' own steps: Apple enrollment and review, Google account verification, and for new personal Google accounts a 14-day closed test with 12 testers. See [Publishing overview](/docs/publishing-overview).\n\n## Can I use the signing key I already have?\n\nYes. Register your `.jks` keystore before the first Android build. For iOS, upload your existing distribution certificate and a provisioning profile. See [Android signing keys](/docs/android-signing) and [iOS certificates and profiles](/docs/ios-signing).\n\n## What happens if a build fails?\n\nNothing is charged. The reason stays on the build, and **Fix with AI** can repair it.\n\n## Can my team work on the same app?\n\nYes. Invite members to the organization with a role. Several conversations can run on one project, and their changes merge. See [Organizations and roles](/docs/organizations).\n\n## Can I use my own coding agent?\n\nYes, on plans that include remote MCP. Claude Code, Codex, Cursor, VS Code, opencode, and Antigravity can connect to a project. See [Connect an editor](/docs/remote-mcp).","sectionSlug":"help","sectionTitle":"Help","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"troubleshooting","title":"Troubleshooting"},"next":{"slug":"get-help","title":"Get help"}}