Build a mobile app with Claude and Blink (full guide)

You are my product planner and app-building coach. I am not technical. I am going to give you a rough app idea, and I want you to help me turn it into a clear, complete build plan I can paste into an AI app builder called Blink to generate a real mobile app for iPhone and Android.

Work in two steps, and do not skip step one.

STEP 1: interview me first.
Before you write any plan, ask me the questions below so the app is actually mine and not a guess. Ask them all at once, grouped and numbered, in plain friendly language, then stop and wait for my answers.

A. The idea
1. In one or two sentences, what does the app do?
2. What is the one main problem it solves?
3. Who is it for, specifically? (for example "busy parents", not "everyone")

B. The core job
4. When someone opens the app, what is the single most important thing they should be able to do?
5. What are the 3 to 5 things version 1 must let them do? (keep this list small)

C. How it works
6. Does it need any phone features, and why? (camera, photos, microphone, location, notifications, contacts, calendar)
7. What does the app need to remember or store? (for example entries, photos, bookings, messages)
8. Do people sign in? If yes, how (email, Apple, Google), and is anyone's content private to just them?

D. Money and look
9. Is it free, paid once, or a subscription? If parts are paid, which parts stay free and which are locked?
10. What should it feel like (calm, playful, premium, minimal), any colors, and do you have a name in mind?

If you would rather not answer everything, just answer what you can and tell me to fill in the rest. I will pick sensible defaults and clearly mark every one with "(assumption)" so you can change it later.

STEP 2: write the build plan.
Once I have answered, write a complete plan in plain language, no code and no developer jargon, using the sections below. Make it specific enough that Blink can build it without guessing, and keep version 1 a small, focused MVP. If something would bloat version 1, move it to the "later, not now" list instead of dropping it silently.

1. App name and one-line pitch. A working name plus a single sentence a stranger would understand.
2. Who it is for and the problem. One short paragraph.
3. What "done" looks like for version 1. The one core action a user can complete, so we know the app works.
4. How you move around the app. The main navigation (for example a bottom tab bar) and the tabs or main sections, each named.
5. The screens, one by one. For each screen: what it shows, what the user can do, what it looks like when it is empty with no data yet, while it is loading, and when something goes wrong. Include the first-time experience: what a brand new user sees, and any quick welcome or setup.
6. Phone features and permissions. Each phone feature it uses, why it needs it, the friendly one-line message to show when the app asks permission, and what still works if the person says no.
7. Notifications. Whether it sends any, what triggers each one, and an example of what one says. If there are none in version 1, say so.
8. Works offline. What a person can still do with no internet, and what needs a connection.
9. What the app stores. The main things it saves, the key details under each, and who can see each one (just that person, or shared).
10. Accounts and sign-in. Whether people sign in and how, what a guest can do without an account, and how someone resets or deletes their account.
11. Money. Free versus paid stated clearly, whether it is a one-time purchase or a subscription, exactly what is locked, and where in the app the upgrade is offered.
12. Look and feel. Colors, overall vibe, the tone of the words, and a simple idea for the app icon.
13. Made for everyone. Basic accessibility: readable text sizes, strong color contrast, and labels so it works with screen readers.
14. What to measure. A few simple things to track so I know if it is working (for example sign-ups, the core action completed, upgrades).
15. Care and safety. Anything sensitive to handle carefully (personal details, photos, anything involving kids), plus a plain note that private data stays private.
16. Ready for the app stores. A store name and short subtitle, the app icon idea, what the screenshots should show, the category, the age rating, and a one-paragraph plain-language privacy summary of what data is collected and why.
17. Later, not now. The features we are deliberately leaving out of version 1 so it can ship.
18. Build instruction for Blink. A final paragraph written straight to the builder, telling it to build this as a mobile app for iPhone and Android, set up the navigation and screens above, wire up the phone features and permissions, add the sign-in and payments as described, generate an app icon, handle the empty, loading and error states, and keep version 1 to the MVP so it is ready to submit to the App Store and Google Play.

Write it so I, a non-technical person, can read every word, and so Blink has everything it needs to start building. Do not include code.

Here is my app idea:
[describe your idea in a sentence or two, then send]

Act as a product strategist. Based on my skills and the audience I want to serve, suggest 5 small mobile app ideas a non-technical person could build and sell. For each one, tell me who pays, the problem it solves, and why it could work. Rank them by how easy they are to build and how likely people are to pay.

Here is my app idea: [your idea]. Act as a skeptical investor. Tell me honestly who would actually pay for this, what would stop them, three ways it could fail, and the single fastest way to test if anyone wants it before I build.

I built an app that [what it does] for [who it is for]. Act as a growth marketer. Give me a simple two-week plan to get my first 100 downloads with no ad budget, using content and communities. Be specific about where to post and what to say.