Supabase Mobile App Builder — Turn Your Supabase Project Into a Native iOS & Android App

In Choicely Studio you choose Connect Supabase and authorize Choicely, then pick which of your projects to use. Choicely reads your public schema into an editable document the AI builds from, and stores your project URL plus its anon / publishable key — the key designed to ship inside a client. Disconnecting is one click and revokes the token at Supabase, not just here. The integration documentation lists every permission we request and what each one is used for.

The anon key is meant to be public, and it ships inside the app — as it does in every mobile app on every backend, because anyone can read the keys inside an app they have downloaded. What protects your data is Row Level Security: your policies on your tables, enforced by Postgres for every request. Write your policies before you publish. Choicely never accepts a secret key: an sb_secret_ or service_role token is rejected in Studio and again by the backend, because that one really would hand every reader full admin access.

Today: sign-up and sign-in with an email and password, sign-in with a one-time code emailed to the user, reads and writes to your Postgres tables under your own RLS policies, realtime subscriptions, and sessions that survive an app restart. Not yet: Apple and Google sign-in, one-tap email links, photo and file uploads, and a helper for Edge Functions. Those are on the way, and we would rather say so up front.

Yes, once the table is published for realtime. In your Supabase dashboard go to Database → Replication and add the table to the publication; without that step the subscription connects but never fires, which is the single most common reason "realtime doesn’t work" in any Supabase app. Everything else — the channel, the cleanup, the reconnect — the app handles for you.

No copy. Your data stays in your Supabase project, on your account and your billing, and the app queries it directly. The only thing stored for the app is your project URL and the anon / publishable key. The token used to read your schema is encrypted server-side, is never returned by any API, and never reaches an app bundle.

Those are visual builders: you assemble screens on a canvas and bind your data to them yourself. With Choicely you describe the app in chat and the AI builds it from your imported schema, then you refine it. On price, checked on each vendor’s own pricing page on 16 August 2026: FlutterFlow’s cheapest plan with code download and store deployment is $39/month, and Draftbit’s cheapest plan with one-click publishing is $12/month. Choicely is $25/month, credit-based, and free to build and preview. If you want pixel-level control of a canvas, they are good tools — Choicely is for getting a working app from a description and a database.

No Mac and no Xcode — the native builds run on Choicely’s infrastructure. You do need your own Apple and Google developer accounts, because the app is published under your name: Apple charges $99 a year and Google a one-time $25 fee, neither marked up by us. The Publish Assistant walks you through creating them and handles the submission itself.

Building and previewing is free — 300 credits a month, no card. Paid plans are $25/month Premium and $50/month Business, credit-based. The output is a real native iOS and Android app published to the App Store and Google Play — not a website in a wrapper — and your Supabase bill stays between you and Supabase.