Mobile App Planning Prompt: Screens, State and Device Checks
Scope a mobile app feature with loading, offline and error behavior. Test permissions, navigation and accessibility on a real device.
Illustrative cover; not a verified result from this prompt.
Read the full prompt
Help create a [FRAMEWORK AND VERSION] mobile app for [PURPOSE]. First feature: [USER FLOW]. Devices and constraints: [DETAILS]. Propose a small project structure, navigation, state handling, data storage and interface states. Request only permissions the feature actually needs. Include offline and error behavior, accessibility considerations and device tests. Use official documentation for platform-specific setup when available and mark unverified assumptions. Do not claim the code has been built, tested or accepted by a store without evidence.
Describe the first task on the phone
Choose a task that can be exercised from start to finish. List the screens and what should happen when someone returns after closing the app. Avoid adding notifications, accounts or location access without a reason.
Example: a personal shopping checklist
Ask for a screen where the user adds “milk,” marks it purchased and can undo that change. Store the list locally for the prototype. Include an empty-state message and a clear indication of checked items that does not depend only on color.
Test a long item name, duplicate entries, an empty submission and restarting the app. Open the keyboard and confirm that it does not cover the input or action button.
Check beyond the emulator
Try navigation, text scaling and touch targets on a real phone when available. Verify how data survives upgrades before connecting an existing app's storage. A generated permission declaration, push setup or release configuration is only a starting point; review it against the framework version and the actual platform requirements.