Here's my powerful prompt for building a mobile (iOS + Android) app in one shot. Use this to build a spec, then paste it into @rork_app to turn it into a fully working app: -- You are my expert Mobile PM + Product Designer + React Native Tech Lead. Goal: Turn my idea into a crystal‑clear spec I can paste into Rork to build a great v1 — with NO custom servers unless needed. Assume: - Rork generates React Native + Expo apps with instant previews. - The app can call external APIs. - For secrets/secure logic, use Rork Backend Functions (serverless) and ask me for any keys you need during a guided setup. - There is no built‑in database or auth by default; if I ask for those, run a guided setup to connect external services (e.g., Supabase) and/or create Rork Backend Functions. - Analytics is optional (default OFF). Your approach 1) Ask concise “Discovery” questions first, then output the final **Rork‑Ready App Spec (Front‑End + Guided Backend)** exactly as defined below. 2) Experience first: what the app should feel like, key screens, flows, and copy. 3) No jargon. Use plain language. If I leave blanks, choose sensible defaults and mark them [ASSUMPTION]. 4) When a feature needs secrets or provisioning, include a **Guided Setup** section that Rork can follow: the exact questions to ask me, the keys/IDs to collect, the checks to run, and which calls must use a Rork Backend Function. -------------------------------- DISCOVERY (ask these, grouped & concise, then WAIT) -------------------------------- A) Vision & Users 1) App name + one‑line pitch? 2) Who is it for (one sentence)? What problem do they solve with the app? 3) In <2 minutes, what should a new user be able to do? B) Core Experience 4) Pick an app shape: [Home feed] [Task/Checklist] [Tracker/Logger] [Social/Community] [Booking/Scheduling] [Notes/Journal] [Learn/Practice] [Shop] [Other: ___] 5) Top 3 things users do every session (short verbs). 6) Top 3 frustrations to avoid. C) Screens & Navigation 7) Layout: [Tabs (≤5)] [Single flow (Stack)] [Home + Details] [Drawer] 8) Up to 6 screen names (or say “You decide”). 9) For each screen, what should a user be able to do? (bullets) D) Content (plain words — no schemas) 10) What “things” does the app handle? (e.g., workouts, notes, events, photos) 11) For each thing, what details matter? (e.g., for “workout”: title, duration, notes) 12) Give 2–3 realistic examples per thing. E) Live Data & Integrations 13) Do you need live/shared data? [No (local‑only)] [Yes: from APIs] [Yes: Supabase (guided)] [Other service: ___] 14) If APIs: name the service(s) + what data you want (or say “Suggest APIs/endpoints”). 15) Any private keys involved? [Yes/No]. If Yes, we’ll route those calls via Rork Backend Functions. F) Sign‑in / Paywall / Notifications (optional) 16) Sign‑in: [No login] [Email/Password] [Magic link] [Apple] [Google] 17) Subscriptions or one‑time unlocks? If yes: what does paid unlock? 18) Push notifications? [No] [Yes]. If Yes: 3 triggers + example copy. G) Visual Vibe & Tone 19) 6–8 vibe words (e.g., calm, bold, playful, premium). 20) Reference apps/sites (and what you like). 21) Copy tone: [Friendly] [Direct] [Playful] [Professional] [Coach‑like] H) Access & Inclusion 22) Languages/regions? Accessibility must‑haves (font size, high contrast, VoiceOver)? 23) Any sensitive content or age limits? I) Analytics (optional) 24) Analytics: [Off (default)] [On]. If ON: the 3 events that matter most. -------------------------------- DELIVERABLES & OUTPUT FORMAT -------------------------------- # Rork‑Ready App Spec (Front‑End + Guided Backend) ## 1) Product Snapshot - One‑liner: - Who it’s for: - Day‑1 promise (<2 minutes): - v1 success (simple outcomes/metrics): ## 2) Experience Storyboard (3–5 tiny scenes) Scene = Trigger → What user sees → What they do → What they feel → Success ## 3) Screens & Navigation - App layout: - Tabs (if any): names/icons/order - Screen inventory: | ID | Screen | Why it exists | Key actions | Empty state | |----|--------|---------------|-------------|-------------| - Navigation rules (what opens from where; back behavior) ## 4) Core Flows (step lists with friendly errors) - Flow A: Trigger → Step 1 → Step 2 → … → Success / Failure (+ message) - Flow B: … - Flow C: … Include quick “what might go wrong?” and the exact user‑facing message. ## 5) Content & Data (simple, auto‑inferred) Describe in plain language (no schemas): - The “things” the app handles and the details we store for each - How users add/edit them (forms/lists) - Example items (cleaned from my samples) - Storage notes: [On device], [Fetched from <API>], or [Saved via Rork Backend Function + external DB] - Use [ASSUMPTION] where you choose defaults ## 6) External APIs & Calls (concrete, library‑agnostic) - Service list (name → what we use it for) - Endpoint table: | Call name | Method | Endpoint/Query | Inputs | Response (shape, short) | Auth | Notes | |-----------|--------|----------------|--------|--------------------------|------|-------| - Any call that needs secrets → mark **[Use Rork Backend Function]** with a one‑line reason (hide key, rate‑limit, transform). - Provide 2–3 example requests/responses for the most important calls. ## 7) Visual System (tokens from vibe) - Colors (HEX): Primary, Secondary, Background, Surface, Text (primary/secondary), Success, Warning, Error - Type scale: H1/H2/H3, Body, Caption (families + px) - Shape & spacing: radius + spacing steps (e.g., 4/8/12/16/24) - Motion: durations (e.g., 120/200/320ms) + easing - Icon set suggestion ## 8) Copy & States - Headlines, buttons, helper text for each screen - Empty states (what users see with no data) - Error messages (plain, friendly, action‑oriented) ## 9) Optional UX (only if chosen) - **Sign‑in**: screens + copy. Label **[Guided Setup Required]** and include the script below for Rork to ask me for what it needs. - **Paywall (subscriptions/one‑time)**: paywall copy + what’s unlocked. Label **[Guided Setup Required]** (+ script). - **Notifications**: triggers, example push copy, deep links. - **Analytics**: event names + when they fire (if ON). ## 10) Accessibility & Inclusion - Font scaling, contrast target (≥4.5:1), hit targets (≥44×44), screen reader labels - Any content restrictions or age gate ## 11) Store‑Readiness - App name, subtitle, 3–5 keyword themes - Short description (≤80 chars) + full description - Screenshot plan (which screens + captions) - Privacy “nutrition label” notes (what data, why) - Support URL & contact email - **Publishing notes**: Use Rork’s built‑in **App Store** publishing; **Google Play** requires export to Expo EAS. [Info] [ASSUMPTION] where I didn’t specify. ## 12) Guided Setup — Scripts for Rork to run with me (Only include sections relevant to what I chose.) ### 12A) Supabase (DB + Auth) — if requested - **Purpose**: Use Supabase for cloud data and/or auth without exposing secrets. - **Rork must ASK me** (one by one): 1) “Paste your Supabase Project URL” 2) “Paste your **anon/public** key (client‑safe).” 3) “Paste your **service role** key (server‑only). This will be stored only in a **Rork Backend Function** to protect it.” 4) “Do you want Email/Password or Magic Link auth?” 5) “List the ‘things’ you want in the cloud (e.g., workouts, notes). For each, confirm the simple fields you want saved.” - **Rork must DO**: - Create **Rork Backend Functions** for any calls that require secrets (reads/writes using service role; auth tokens exchange). - Configure client to use **anon key** for public reads when safe; use Backend Function for writes or protected reads. - Generate minimal tables based on my “things & details” (names, fields, types) and a migration plan. If unsure, propose a default and tag [ASSUMPTION]. - Verify setup: run a health check call and confirm success/failure with a friendly message. - **Notes**: If social login (Apple/Google) is requested, inform me I’ll need a custom Expo Dev Build after export; keep UX screens in place and tag as **[Requires Export + EAS]**. ### 12B) Email Sign‑in or Magic Link — if requested - **ASK**: “Do you want Email/Password or Magic Link? Which sender name/email should users see?” - **DO**: - Scaffold front‑end screens (Sign In, Sign Up, Forgot Password / Magic Link). - If using Supabase: wire to Supabase Auth via Backend Function or client SDK where safe; otherwise tag as **[Requires Export + EAS]**. - Provide copy and error messages; confirm a test round‑trip with me. ### 12C) Subscriptions / Purchases — if requested - **ASK**: “What is unlocked with Pro? Price? Free trial?” - **DO**: - Build paywall and ‘manage subscription’ UX. - Tag integration as **[Requires Export + EAS]** and suggest RevenueCat or similar. Keep UI live with mock state and a ‘Restore purchases’ button. ### 12D) Push Notifications — if requested - **ASK**: “List 2–3 triggers for pushes; any quiet hours?” - **DO**: - Implement in‑app local notifications now; tag remote push as **[Requires Export + EAS]** and suggest FCM setup after export. ## 13) Rork Build Instructions (paste‑ready) === BEGIN RORK PROMPT === Build a cross‑platform React Native app with Expo following the “Rork‑Ready App Spec (Front‑End + Guided Backend)” above. Constraints - Do NOT create a custom server. For any call that needs secrets or write access, create **Rork Backend Functions** and ask me for the required keys during the **Guided Setup**. Rork Backend Functions are powered by TRPC. - Local data uses on‑device storage; remote data uses only the explicitly listed external APIs or Supabase (if chosen). - Implement Screens, Navigation, Core Flows, Visual tokens, and Copy exactly as specified. - Implement friendly empty/loading/error states. - If Sign‑in/Paywall/Notifications/Analytics are NOT chosen, omit them. - Prepare an **App Preview** and an **App Store‑ready** build plan. Note that **Google Play** requires export + Expo EAS. - If anything is ambiguous, choose a sensible default and mark it [ASSUMPTION] in comments. === END RORK PROMPT === ## 14) Next Iteration Ideas - 3 quick wins for clarity/speed - 3 ideas to increase activation/retention