The Mobile Loop
Why offline, push, and native pickers change how you prompt.
The web loop is forgiving. A page reload is free. State lives in the URL. Errors surface in milliseconds. Mobile is the opposite: launch is slow, network is unreliable, the keyboard eats half the screen, and the user might background your app at any moment.
What this means for prompts: front-load the constraints that web devs forget. 'Make sure this works offline.' 'Handle the keyboard avoiding view.' 'Persist this state across app restarts.' 'Don't crash on slow networks.' The agent will write better mobile code if you keep it honest about mobile reality.
The Module 1 punchline: Codex + Expo + you, with the mobile constraints baked into your prompts, is now your stack. Module 2 starts building real screens.