---
name: mobile-app-wireframe-description-generator
description: "Screen-by-screen wireframe descriptions for a mobile app concept, with layout, elements, actions, navigation, and empty and loading states a designer can sketch from. Use when a founder or designer has a mobile app concept and needs written wireframes before sketching or building. Do not use for visual design, colour systems, or desktop web layouts. Related topics: product, design, mobile."
---

# Mobile App Wireframe Description Generator

Screen-by-screen wireframe descriptions for a mobile app concept, with layout, elements, actions, navigation, and empty and loading states a designer can sketch from.

## When to use

Use this skill when a founder or designer has a mobile app concept and needs written wireframes before sketching or building. Do not use it for visual design, colour systems, or desktop web layouts.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Define the primary user journey that delivers the core value and place each chosen screen on it.
3. Draw the navigation map in words, done when every screen is reachable and the back path is clear.
4. Describe each screen top to bottom with the requested details and platform-specific components.
5. Place the primary action within thumb reach and cut elements that do not serve the core value.
6. List open design questions to test.

## Inputs

- **App name** (free text, e.g. "Name")
- **Platform** (choose one: iOS, Android, Cross-platform)
- **Category** (choose one: Social, Productivity, Health and fitness, Finance, E-commerce, Education, Entertainment, Other)
- **Core value in one sentence** (longer free text)
- **Screens to describe** (choose any: Onboarding, Sign in or sign up, Home or dashboard, Profile, Settings, Main feature, Detail view, Notifications, Search, Payment or checkout)
- **Details for each screen** (choose any: Screen title, Component layout, Key UI elements, User actions, Navigation transitions, Empty state, Loading state)

## Output

A navigation map followed by one section per screen with the requested details, and a closing list of questions to test.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Mobile Wireframe Descriptions

Describe wireframes for the app below.

- App name: {{App name}}
- Platform: {{Platform}}
- Category: {{Category}}
- Core value in one sentence: {{Core value in one sentence}}
- Screens to describe: {{Screens to describe}}
- Details for each screen: {{Details for each screen}}

Start with a short navigation map (tab bar or drawer, and how screens link). Then for each screen give the requested details, ordering the layout top to bottom, naming components with their platform convention (navigation bar and tab bar on iOS, app bar and bottom navigation on Android), and placing the primary action where a thumb reaches it. Keep each screen to what supports the core value. Close with open design questions worth testing.

## Pitfalls

- Giving every screen equal weight instead of centring the core value screen.
- Using iOS patterns on Android or the reverse, which feels foreign to users.
- Describing only the filled state, so empty and loading cases surprise developers.
