Describe your app idea and get detailed wireframe specs for every screen - flows, layouts, interactions, and edge cases all documented.
Paste into any LLM. Use the output as specifications for your wireframing in Figma, Sketch, or direct development.
You are a senior product designer who has shipped mobile apps with 10M+ downloads for both iOS and Android platforms. App concept: [WHAT THE APP DOES] Primary user: [WHO USES IT AND WHY] Platform: [IOS/ANDROID/BOTH] Key user goal: [THE MAIN THING USERS WANT TO ACCOMPLISH] Monetization: [FREE/FREEMIUM/SUBSCRIPTION/ONE-TIME PURCHASE] Create complete wireframe specifications: **1. Information Architecture** - App structure (tab bar items and their content) - Screen hierarchy map (which screens connect to which) - Navigation model (tab bar, drawer, stack, or hybrid) - User flow for the primary task (step-by-step screens) - User flow for onboarding (first-time experience) **2. Core Screens (detailed wireframes)** For each screen, specify: - Screen name and purpose - Layout description (header, body sections, footer/actions) - Every UI element with position and behavior - Content hierarchy (what's most important) - Scroll behavior and fixed elements - Loading state, empty state, error state Screens to design: - Splash / onboarding (3-4 screens) - Home / main dashboard - List view (browse/search results) - Detail view (single item full view) - Create / input form - Profile / settings - Notifications - Search with filters **3. Interaction Specifications** - Tap targets and touch areas - Swipe gestures (left, right, pull-to-refresh) - Long press actions - Transition animations between screens - Bottom sheet and modal behaviors - Haptic feedback moments **4. Edge Cases** - No internet connection state - Empty states for each screen (first use) - Permission requests (camera, location, notifications) timing - Deep link handling - Background to foreground resume - Keyboard appearance and avoidance **5. Platform-Specific Adaptations** - iOS: safe areas, Dynamic Island, large titles, SF Symbols - Android: Material 3 components, edge-to-edge, predictive back - Differences in navigation patterns - Platform-native vs custom components decisions Describe every element precisely enough that a developer could build it without seeing a visual mockup.
This prompt produces reliable output because it leverages sequential task breakdown and output formatting and context framing. Each element gives the AI model additional signal about what quality looks like for this specific task. The output you receive will be user-centered design specifications with component details, interaction states, and accessibility considerations, ready to use with minimal editing.
These ui/ux design tips will help you get stronger results when using "Mobile App Wireframe Specification" and similar prompts in this category.
"Mobile App Wireframe Specification" is particularly useful in these situations. If any of these scenarios sound familiar, this prompt will save you significant time.
When you use "Mobile App Wireframe Specification" with ChatGPT, Claude, or Gemini, here is what to expect in the AI output.
Adapt "Mobile App Wireframe Specification" to your specific situation by modifying these key areas. The more context you add, the better the results.