Taking a little longer than usual…

Loading FluxNative
FluxNative

FluxNative documentation

Guides to build React Native apps with AI: prompts, Figma import, Supabase and Firebase, signed builds without a Mac, TestFlight and Google Play.

Get started

  • Introduction — FluxNative turns a description, a Figma design, screenshots or a template into a real iOS and Android app you can preview, build, publish and export.
  • Quickstart — From sign-up to a working app in minutes: describe it, check the preview, ask for a change, and on Creator install it on your phone.
  • How FluxNative works — The few words the product uses, from organization to release, and what happens during one turn of the assistant.
  • Start a project — Four ways to begin an app: your idea, a design (Figma screens sent with the plugin, or images), a template, or an Expo app you already have.
  • Import an existing Expo app — On paid plans, upload an Expo app as a .zip, on Expo Router or React Navigation. FluxNative checks it and previews it before anything is created; your code comes in as it is, apart from the changes the report lists.

Build your app

  • Tour the workspace — Find your way around a project: the chat, the project panel, the preview, and the project bar's pages and tools.
  • Work with the assistant — Send requests with images, files or picked elements, plan big changes first, answer questions, and stop, continue or rewind a turn.
  • Write better prompts — Get the result you want: name the people, the job and the screens, change one thing at a time, and say what to keep.
  • Preview — Click through your app in a device frame, switch route or device, edit text and styles in place, and share a link.
  • App structure — See every screen the assistant planned and built, how they connect, and which ones failed to open, in the App tab.
  • Design tokens — Change brand colour, corners, spacing, type, typefaces or a whole direction in the Design tab, without spending a turn.
  • Edit the source — Open any file in Code, edit it with autosave, search the project, move or replace files, or send highlighted lines with a request.
  • Revisions and undo — Undo a turn with Rewind, and see how two conversations working at once merge instead of overwriting each other.
  • App name and icon — Set the app's name, launcher icon, launch screen and store identifiers in App settings; identifiers lock after the first store upload.
  • Checks — When a type or native check fails, read the diagnostic and fix it in chat or Code; the revision stays so you can repair it.
  • Export the project — Download the whole Expo project as a .zip, or push it to your own GitHub repository, with notes on running and building it without FluxNative.

Designs and templates

  • Build from a Figma design — Send the screens you choose from Figma straight into your app with the FluxNative plugin, and the assistant builds them from the frames. Images of a design work too.
  • Templates — Copy a full app or a screen design into your organization, then follow its setup checklist: make it yours, try it, connect your backend.
  • Explore and Validate an idea — Study about 900 apps that already earn, check your own idea against them, and start building from the result. Neither is a forecast.

FluxNative Commerce

  • FluxNative Commerce — Native apps for your WooCommerce, Shopify, WordPress or Odoo site. Pick your platform to see what it gets: app types, paying, the AI assistant and what to install. $79 a site, with unlimited apps and builds for it and every new version free.
  • AI shopping assistant — The assistant in a Commerce app and on your website: it finds products, reads size charts, adds several items at once, compares, suggests what goes well, helps with orders and remembers if asked. Where it runs per platform, what it needs and how to turn it on.
  • Plugins by platform — Every plugin, theme and Shopify app a Commerce app reads, by platform and app type: each linked to its own page, Free or Paid, what it turns on in the app, and whether it needs the FluxNative plugin. A Shopify store installs no WordPress plugin.
  • WooCommerce: Store app — A Commerce app for any WooCommerce store: its catalog, cart, checkout and orders, live from the store. Each feature with a picture, the product types it sells, the plugins it needs and the ones it works with.
  • WooCommerce: Marketplace app — A Commerce app for a Dokan or WCFM marketplace on WooCommerce: every vendor, their stores and products, one cart and the sellers' own area. Each feature with a picture, the plugins it needs and the ones it works with.
  • WooCommerce: Seller app — Sellers on a Dokan or WCFM marketplace run their store in a Commerce app: dashboard, orders, products, inventory, coupons, payouts and store settings. Inside the marketplace app, or as its own app on the same site.
  • WooCommerce: Driver app — Drivers see and deliver their orders in a Commerce app, on WooCommerce, Dokan or WCFM with a delivery plugin. Inside the store app, or as its own app on the same site.
  • Shopify: Store app — A Commerce app for any Shopify store, through the Storefront API: collections, products, cart and Shopify's own checkout. What it has, what Shopify does not get, how it connects and what it needs.
  • WordPress: Directory app — A Commerce app for a Listeo or MyListing WordPress site: places on Home and a map, listing pages, reviews, Listeo bookings with Pay Now and owners' listings. With WooCommerce keys, the shop stays too.
  • WordPress: News app — A Commerce app for a WordPress site as a news app: posts, categories, tags, search, saved posts and comments. No products, cart or checkout.
  • Create a Commerce app — In the Commerce dialog: bring a FluxBuilder app from its env.dart and config files, start from the template as one app type on your own store, or copy one of your Commerce apps.
  • Connect your store and website — Build › Connect website ties a Commerce app to one of your sites, so it builds and its source can be taken out. Your store, under Server › Backend, changes the store the app reads.
  • Sign-in and notifications on WordPress — Set up Google and Apple sign-in and push for a Commerce app in the FluxNative plugin: upload your app's Firebase files, the Firebase key and the APNs key, then check that each line says Ready.
  • Update a Commerce app — New FluxNative Commerce versions are free. Remake on the App tab brings one into your app as one version you can undo, keeping its bundle ID, signing and site.

Connect services

  • Server — Server, on the project bar, holds the app's backend, payments and secret keys. Enter credentials once; the assistant uses them without seeing them.
  • Supabase — Save the project URL and an access token; the assistant then creates the tables, row-level security, Edge Functions and their secrets.
  • Firebase — Paste a service-account key once; the assistant reads the config, publishes tested security rules and registers Android fingerprints for Google sign-in.
  • Appwrite — Save the endpoint, project ID and a server API key; the assistant creates tables and buckets and registers the app with Appwrite.
  • Cloudflare — Save your account ID and an API token so the assistant can deploy Workers and use R2 and Queues.
  • Your store, site or API — Connect WooCommerce, WordPress, Shopify, or a REST or GraphQL API you already run; your key never ships in the app.
  • In-app purchases — Sell a subscription by following the checklist on Publish › Purchases: the stores, RevenueCat, the paywall, the products and a test purchase.
  • Ads — Add your AdMob app and ad unit IDs and your test phones; the assistant places the ads and asks for consent first.
  • API keys and secrets — Store server keys by name; the assistant sees only the name and a description, and delivers them to your backend's functions.

Build for devices

  • Native builds overview — Build a signed APK, App Bundle or IPA from one revision, with no Xcode, Android Studio or Mac; you pay only when it succeeds.
  • Android builds — Build an APK to install on phones, or an App Bundle for Google Play, then send the bundle to Play from Publish.
  • Android signing keys — Every Android build is signed with the app's key: let FluxNative create it or register your own, copy its fingerprints, and keep it safe.
  • iOS builds — Build a signed IPA without a Mac and send it to TestFlight from Publish; you need an Apple Developer account and its API key.
  • iOS certificates and profiles — With an App Store Connect API key, FluxNative makes the certificate and profiles for you; without one, create them yourself and upload them.
  • Versions and build numbers — Set the version customers see and the build number every upload needs, both next to the build button in Build.
  • Install and test on a device — Install an APK on Android with a QR code, or test through TestFlight and Play internal testing, then check what the preview cannot run.
  • Fix a failed build — Read who fixes a failed build, use Fix with AI for code problems, fix settings where the reason says, then retry; failures are never charged.

Publish to stores

  • Publishing overview — Pick a store in Publish, do the step it marks next, and follow your app through review to release.
  • Connect store accounts — Connect the organization's App Store Connect API key and Google Play service account once; every app in the organization uses them.
  • The Publish steps — Every step in Publish for the App Store and Google Play, where each one happens, and what the Release and Security checks look for.
  • Release to TestFlight — Send a signed IPA to TestFlight from Publish, let FluxNative follow Apple's processing, then add testers in App Store Connect.
  • Google Play testing — Put an App Bundle on Play's internal testing track, the first by hand, add testers, open it to anyone with the link, and run Google's closed test if needed.
  • Store page — Write the store text with AI, frame screenshots, host privacy and support pages, and send it all from Publish › Store page.
  • Production release — Submit an iOS version for App Review and release it once Apple approves, or roll an App Bundle out to Google Play production.
  • Push notifications — Turn push on, choose FluxNative or OneSignal, connect its keys, build, then send or schedule from Push notifications and see who it reached and who opened it.
  • Video ads — Make a 15 or 30 second ad filmed from your real app, voiced and captioned in your language, plus the App Store's app preview video.
  • Landing pages — Make a one-page website for your app from chat that links to its store pages, and put it online on a host you own.

Teams and billing

  • Organizations and roles — Invite your team, pick each person's role, and limit developers and viewers to selected apps; the organization owns apps, credits and store accounts.
  • Hand an app to a client — Show a client the app with a preview link, give them access to just their app, or hand the app over: build it in their workspace, or export it with its signing key and move the store app to their developer account.
  • Manage your apps — Find, filter and sort your apps, jump between them with ⌘K, and restore a deleted app within 7 days.
  • Credits and plans — See what spends credits, which credits expire when, what Free includes and each plan adds, and what happens when the balance runs out.
  • Connect an editor — Connect Claude Code, the Claude app, Codex, Cursor, VS Code, opencode or Antigravity over MCP to find, create and edit your apps and landing pages.
  • Your account — Change your name, photo, password and two-factor sign-in, connect Google or GitHub, sign out old sessions, or delete the account.
  • Notifications and settings — Choose which notices reach your inbox, see the emails FluxNative sends, and set your theme, language, workspace and editor connections.

Help

  • Troubleshooting — Quick fixes for the problems people hit most: the preview, a stopped turn, conflicts, the Figma plugin, builds, store uploads and review, credits and keys.
  • FAQ — Short answers about Free, owning the code, native apps, backends, keys, the stores, signing, teams and your own coding agent.
  • Get help — Search Help, ask the assistant, report a bug or send support a request; replies come by email, usually within 1–2 business days.
  • What support covers — Every plan, Free included, can ask support about FluxNative itself; replies usually come within 1–2 business days, Monday to Friday (GMT+7).
  • What a change costs, and questioning a charge — Every reply shows its cost; Credits & billing › Activity lists each request, and Ask about this charge sends support the details.
  • Is FluxNative down? — Check whether FluxNative is up, updating, and taking Android and iOS builds, and see any incident in progress.
  • Delete your account — Profile › Delete account removes your account and every workspace you own, with their apps; workspaces you only belong to stay.