Onboarding Screens and Empty States
Design the first-run experience.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design the first-run experience for my app. Product and its main value: [PRODUCT_AND_VALUE]. Target users and their goal on day one: [USERS_AND_GOAL]. Platforms: [PLATFORMS]. Data needed from the user: [DATA_NEEDED]. Use this decision tree: 1. What is the quickest path to the first moment of value? Design for that path and remove anything not required to get there. 2. Do users need an account before they see value? If not, let them try first and ask for sign-up later. 3. Which information is truly required now versus later? Move everything else to progressive prompts. 4. Is a tour needed? IF the interface is self-explanatory THEN use contextual hints on first use rather than a carousel. IF the product has a novel model THEN use at most three screens with one idea each, with a skip option. 5. Permissions (notifications, location, camera): ask in context with a reason, not at launch. 6. Empty states: for each main screen, design what appears with no data: an explanation, a primary action, and sample content. 7. Return visits: a checklist of next steps that tracks progress. Output a screen-by-screen specification (purpose, content, copy, primary action, secondary action, error states), 12 microcopy lines, accessibility notes, and the metrics (completion, time to first value, drop-off by step). Provide a test plan with five users.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.