Mobile app prompt examples: describe a useful first version

A reusable prompt template, three worked examples and review prompts for planning mobile app screens without a long feature list.

By Cicrew · Updated September 29, 2026

Download the prompt worksheet

Give the app one clear job

Start with the person using the app and the task they want to finish. A list of technologies or a request for a beautiful app leaves the important decisions open. A short journey explains what the screens need to support.

Use this worksheet before starting a project. Replace every bracketed phrase with a concrete choice. The examples below are suggested prompts; their exact wording has not been run as a benchmark.

Create a mobile app for [specific audience] who need to [task]. The main journey is [starting point], then [action], then [visible result]. Include [three to five screens], plus [the first-use or empty state]. Use [visual direction] with [readability or accessibility requirement]. Use fictional demo data while designing. Leave out [features that can wait]. Start with the design so I can review the screens before building.

Example: a plant-care log

The important distinction is checking the soil versus watering. Put it in the journey and labels so the design does not encourage an automatic action the app cannot justify. Our Leaflet case study shows an actual design session for this problem.

Design a mobile app for people with a few houseplants who forget their last care task. The journey is to see which plant needs checking, open it, record a soil check or watering, and find the entry in its history. Include Today, My plants, Plant details and Add a plant, plus an empty collection. Use cream and forest green with large readable labels. Use demo plants. Leave out plant diagnosis, live notifications and shopping.

Example: a reading tracker

Define what the input represents. Current page and pages read are different quantities. A good prompt names the one the reader enters and the result the app should show.

Design a mobile app for casual readers to track their current book. The journey is to open the book, enter the page reached, and see the updated progress. Include Today, Bookshelf, Book details, Log progress and an empty bookshelf. Use warm paper, dark ink and restrained terracotta. Label the input Page reached. Use demo reading history. Leave out social feeds, recommendations and external book search.

Example: a packing checklist

Specify where an item belongs and how progress should be understood. A general request for travel planning would invite a much broader product than a reusable packing list.

Design a mobile app for people packing for short trips. The journey is to select a trip, see items grouped by category, tick an item and see how many remain. Include My trips, Trip setup, Checklist and Add an item. Show no-trips and all-packed states. Use sky blue, navy and white with clear touch targets. Use fictional trips. Leave out bookings, live weather and maps.

Ask for a change you can check

Review the first result at phone size. Name the screen, the problem, the intended change and what should remain. Keep the request focused enough that you can compare the next output with the previous one.

On [screen], [specific problem] makes [task] unclear. Change [element or behavior] so [expected result]. Keep [parts that already work]. Also show [missing empty, error or completed state]. Review the affected screens together.

A design prompt is the start of a build brief

Before implementation, turn the main journey into an acceptance check: given a starting state, a person takes an action and sees an observable result. Include what must still be true after closing and reopening the app.

Design screenshots do not verify persistence, authentication, purchases or device behavior. Add those requirements when they become necessary and test the implemented flows. Keep the first version small enough to review end to end.