Loading…

    Add a Supabase backend: sign-in, database and file storage

    Written by the Fastshot team from the Fastshot user guides. Updated .

    A new Fastshot app runs on sample data kept on your device. To go live, you create a Fastshot-managed Supabase backend from a connect card (your plan must include one), and the AI moves the app onto it: sign-in with email, Google and Apple, a PostgreSQL database and file storage. You do not need your own Supabase account.

    Start building your app

    A new app first runs on sample data kept on the device, so every screen works while you shape it. A backend makes sign-in real and shares data between devices.

    1. 1. Shape the app on sample data

      Until a backend is connected, the editor shows a Sample data label above the preview. There is no real sign-in and nothing is shared between devices yet.

    2. 2. Start the connection

      When the app works the way you want, click Sample data above the preview, open the Backend tab, or ask the AI to connect a backend. It shows a connect card in the chat.

    3. 3. Create the backend

      Create it from that card. If your plan does not include a backend, the card offers an upgrade. Fastshot provisions and manages the backend for the app, so you do not need a separate Supabase account.

    4. 4. Let the AI move the app onto it

      When the backend is ready, the AI creates tables with access rules for the app’s data, adds real sign-in where data belongs to a person, and points the same screens at the backend. The label then reads Live data.

    Good to know

    • The backend offers sign-up and sign-in with email, Google and Apple, a PostgreSQL database, file and image uploads, and real-time data subscriptions.
    • Sample records are not copied, so new accounts start empty. Content the app ships with, such as categories, is added to the database.
    • The connect card creates a new Fastshot-managed backend. It cannot attach an existing external project or migrate existing users and tables.

    Frequently asked questions

    Do I need my own Supabase account?
    No. Fastshot provisions and manages a Supabase backend for the app from a connect card in the chat, so a separate Supabase account is not required. If your plan does not include a backend, the card offers an upgrade.
    How do I add a Supabase backend to my app?
    Click Sample data above the preview, open the Backend tab, or ask the AI to connect a backend. Create it from the connect card; the AI then adds tables and real sign-in and points the same screens at it. The label changes to Live data.
    How do I add login and sign-in to my app?
    Connect a backend. The AI then adds real sign-in where data belongs to a person. Supported sign-up and sign-in methods are email, Google and Apple. Before that, the app runs on sample data with no real sign-in.
    What does the backend include?
    A PostgreSQL database for app data, sign-up and sign-in with email, Google and Apple, file and image uploads through storage buckets, and real-time data subscriptions.
    What is the “Sample data” label?
    Until a backend is connected, the app runs on sample data kept on the device. Every screen works, but there is no real sign-in and nothing is shared between devices. After connecting, the label reads Live data.
    Can I connect an existing Supabase project?
    No. The connect card creates a new Fastshot-managed backend. It cannot attach an external project or migrate existing users and tables.
    Is my sample data copied to the backend?
    No. Sample records are not copied, so new accounts start empty. Content the app ships with, such as categories, is added to the database. Data typed while testing the preview stays on that device.

    Next lesson: Add subscriptions with Adapty or RevenueCat

    Start building your app