{"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.","body":"This walkthrough takes one app from nothing to a phone. It uses the Android APK path because it needs no store account. Plan on a few minutes of your time and a few minutes of building.\n\n## Before you start\n\n- An account. Sign up with email and a password, or with Google or GitHub when those are offered.\n- Credits in your organization. Free accounts start with a one-time welcome grant. See [Credits and plans](/docs/credits-and-plans).\n- An Android phone for the last step. You can stop after the preview if you do not have one.\n\n## 1. Describe the app\n\nAfter you sign in, the first-run page asks how you want to start. Choose to describe it and write a short brief. Say who uses the app, what they do, and the first screens you expect.\n\n```\nA habit tracker for students. Home lists today's habits with a check button.\nA habit detail screen shows a 30-day streak calendar. A stats tab shows weekly\ncompletion. Calm, friendly look with a green accent. No sign-in yet.\n```\n\nSend it. The project opens and the assistant starts writing. It names the app from your brief. You can rename it later.\n\n## 2. Watch and review\n\nWhile the assistant works, it drives the preview itself to check its own screens, so the preview is locked. The chat shows what it is doing and which files it changed.\n\nWhen the turn finishes, click through the app in the preview. Use the route picker to jump to a screen, and the device picker to see it on an iPad mini or a Pixel 8. Open **App** on the left to see every screen the assistant planned and built.\n\n## 3. Ask for a change\n\nWrite a focused follow-up. Name the screen, what is wrong, and what you want instead.\n\n```\nOn the habit detail screen, make the streak calendar bigger and show the\ncurrent streak number above it. Keep the rest of the screen as it is.\n```\n\nIf a change goes the wrong way, use **Undo** on that turn in the chat. The project returns to the revision before it.\n\n## 4. Build an APK\n\n1. Click **Build** in the project bar.\n2. Choose **Android**, then **Installable APK**.\n3. The first build can create the app's signing key. Accept it unless you already have a keystore for this app.\n4. Start the build and wait for it to finish. You are charged only if it succeeds.\n\n## 5. Install it on your phone\n\nWhen the build finishes, click the QR code button next to it and scan the code with your Android phone. The link works for one hour. You can also download the APK and copy it to the device.\n\n> [!TIP]\n> Android asks for permission to install apps from outside the Play Store the first time. That is expected for an APK you built yourself.\n\n## Next steps\n\n- Store real data: [Connections](/docs/connections).\n- Improve your requests: [Write better prompts](/docs/writing-prompts).\n- Ship to testers and the stores: [Publishing overview](/docs/publishing-overview).","sectionSlug":"get-started","sectionTitle":"Get started","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"introduction","title":"Introduction"},"next":{"slug":"how-it-works","title":"How FluxNative works"}}