Premium Mobile App Interface Director

Premium Mobile App Interface Director is a specialist mobile product-design skill for transforming an app concept, feature brief, workflow, wireframe, prototype, or existing mobile product into a complete premium UI/UX architecture for iOS and Android.

It is designed for:

Startup Founders Mobile Product Teams UX Designers UI Designers Product Designers iOS Developers Android Developers React Native Teams Flutter Teams Product Managers Mobile Agencies SaaS Companies Consumer Apps Fintech Apps Health and Wellness Apps Ecommerce Apps Marketplace Apps AI Mobile Apps Education Apps Travel Apps Delivery Apps Mobility Apps Subscription Apps Productivity Apps Internal Enterprise Apps

The skill solves a common mobile-product problem:

Teams often begin designing screens before defining how users actually move through the product.

This creates:

Disconnected Screens Inconsistent Navigation Overloaded Bottom Navigation Long Onboarding Poor Permission Timing Hidden Essential Actions Desktop Patterns Compressed Into Mobile Missing Loading States Missing Empty States Missing Error States Undefined Keyboard Behavior Inconsistent Gestures Excessive Modal Usage Weak Tablet Support Unclear Android Back Behavior Unsafe Destructive Actions Poor Accessibility Unstructured Design Systems

The skill creates a complete product architecture using:

App Concept → User Roles → Jobs to Be Done → Primary Tasks → Activation → User Flows → Screen Inventory → Screen Hierarchy → Navigation → Onboarding → Interaction Patterns → Gestures → Microinteractions → States → Platform Adaptation → Responsive Behavior → Accessibility → Design System → Implementation Specifications

The central principle is:

A premium mobile app is not a smaller desktop interface.

Mobile interfaces must be designed around:

Limited Screen Space Touch Input Thumb Reach Virtual Keyboards Safe Areas System Navigation Platform Conventions Shorter Attention Windows Network Variability Notifications Permissions Device Capabilities Interruptions Operating-System Behavior

The skill begins by identifying the primary job to be done.

For each user role it can define:

Primary Objective Core Tasks Task Frequency High-Risk Actions Required Permissions Primary Entry Points Key Screens

Jobs can be structured as:

When... I want to... So I can...

This prevents the interface from becoming a collection of unrelated features.

The skill creates complete user-flow architecture.

Potential flows include:

Sign Up Sign In Verification Password Reset Onboarding Profile Setup Browse Search Create Edit Book Purchase Checkout Upload Scan Message Schedule Approve Complete Task Review Activity Manage Subscription Manage Notifications Contact Support

Each flow can define:

Entry Point Goal Steps Decision Points Success State Failure State Exit Recovery Deep-Link Behavior

The skill creates complete screen inventories.

Typical screen groups include:

Access: Splash Sign In Sign Up Verification Password Reset

Onboarding: Welcome Value Orientation Permission Education Profile Setup Preferences Activation

Core Product: Home Search Browse Detail Create Edit Tasks Messages Activity

Account: Profile Settings Notifications Privacy Subscription Help

System States: Loading Empty Error Offline Permission Denied Restricted Maintenance

The skill creates screen hierarchy.

Level 1: Primary destinations.

Level 2: Entity and workflow screens.

Level 3: Details, edits, configuration, and secondary states.

It avoids excessive hierarchy depth.

The skill selects the correct navigation architecture.

Possible patterns include:

Bottom Navigation Navigation Stack Top Tabs Segmented Controls Drawer Navigation Contextual Tabs Search-First Architecture Hub-and-Spoke Master-Detail for Tablets

Bottom navigation is recommended only for a small number of high-frequency peer destinations.

Typical range:

3–5 top-level destinations.

The skill avoids:

Six or More Bottom Tabs Settings as a Primary Destination Ambiguous Icons Actions Disguised as Destinations

Primary creation actions can use:

Screen-Level CTA Contextual Toolbar Action Floating Action Button Centered Navigation Action

only when the product context justifies the pattern.

The skill defines predictable navigation stacks.

Detail screens should preserve context.

Returning from detail may preserve:

Scroll Position Search Query Filter State Selection Previous Tab

The skill defines back behavior.

iOS and Android back navigation should not be treated as identical.

Deep-link behavior can be defined for:

Push Notifications Email Links Shared Links Web-to-App Links Universal Links App Links

A deep link should open the relevant screen with enough context to understand the destination.

The skill creates onboarding architecture.

Its primary goal is:

Reach first value quickly.

A recommended pattern is:

Value → Minimal Setup → Required Permission Education → First Meaningful Action → Activation

The skill does not recommend explaining every feature before product use.

Supported onboarding styles include:

Value-Led Setup-Led Personalization-Led Permission-Led Progressive

It avoids:

Seven-Slide Marketing Carousels Forced Tutorials Requesting Every Permission at Launch Collecting Unnecessary Profile Data Unskippable Education

The skill defines permission timing.

Before requesting operating-system access, the product should explain:

Why the Permission Is Needed What It Enables What Happens If It Is Denied

Potential permissions include:

Camera Location Microphone Photos Files Contacts Notifications Biometrics

Only verified capabilities should be designed.

Permission-denied states can include:

Alternative Workflow Limited Mode Open Settings Additional Explanation

Users should not become trapped when optional permissions are denied.

The skill identifies an activation moment.

Examples:

First Project Created First Booking Completed First Item Saved First Payment Sent First Lesson Completed First Workflow Configured First Product Added First AI Session Completed

The home screen is then designed around meaningful value rather than generic feature cards.

First-use home and returning-user home may differ.

First-use home may emphasize:

Setup Education Create First Item

Returning-user home may emphasize:

Continue Recent Activity Pending Tasks Alerts Recommendations

The skill creates touch-first layout hierarchy.

Typical phone structure:

Top Navigation → Context → Primary Content → Primary Action → Supporting Content

It avoids desktop-style multi-column layouts on small screens.

The skill respects:

Notches Status Bars Home Indicators System Navigation Areas Keyboard Areas Device Safe Areas

It considers thumb reach.

High-frequency actions should generally remain reachable.

Possible patterns include:

Bottom Controls Sticky Bottom CTA Bottom Sheets Swipe Actions Contextual Toolbars

The skill does not place every critical control in the top-right corner.

It creates top app-bar architecture.

Possible elements:

Back Title Search Primary Action Overflow Context

It avoids excessive toolbar controls.

The skill determines when large titles are appropriate and when they waste valuable vertical space.

Bottom sheets are used for:

Contextual Actions Filters Short Selections Confirmation Quick Details

They should not become containers for complex multi-step workflows.

Full-screen modals may be appropriate for:

Creation Editing Immersive Tasks Significant Interruptions

The skill avoids modal-on-modal interaction.

Mobile forms are optimized for:

Minimal Fields Correct Keyboard Type Autofill Autocomplete Persistent Labels Inline Validation One-Handed Use Keyboard-Safe CTAs Error Recovery

The skill explicitly defines keyboard behavior.

Potential requirements include:

Next Field Return Key Dismiss Scroll Into View Error Focus CTA Visibility

Correct input types may be assigned for:

Email Phone

URL

Number Decimal Search

Validation should be contextual rather than aggressively showing errors before interaction.

The skill supports authentication flows including:

Email Phone

SSO

Passkeys Biometrics

but only when those capabilities are verified.

Biometric UX can include:

Opt-In Fallback Authentication System Prompt Recovery

The skill designs mobile lists.

List rows can contain:

Title Subtitle Metadata Status Trailing Control Primary Action

It balances information density with appropriate touch targets.

The skill avoids wrapping every list item in a large decorative card.

Cards should represent meaningful content grouping.

Detail screens can use:

Top Bar → Identity → Status → Primary Action → Core Detail → Secondary Sections → Activity

Primary actions can appear as:

Sticky Bottom CTA Inline Action Screen Footer Toolbar Action

depending on task context.

The skill defines gesture architecture.

Potential gestures include:

Swipe Back Swipe Actions Pull to Refresh Long Press Drag to Reorder Drag and Drop Pinch Context Gestures

Essential actions should also have visible alternatives unless the gesture is a standard operating-system behavior.

Swipe actions may be appropriate for:

Archive Mark Read Delete

but destructive actions require safe interaction patterns.

Long press can expose secondary contextual actions.

It should not become the only way to reach important functionality.

Pull to Refresh is used only when manual refresh is meaningful.

Drag-and-drop flows define:

Drag Affordance Movement Feedback Drop Target Completion Feedback Accessibility Alternative Where Possible

The skill creates haptic strategy.

Potential uses include:

Selection Success Warning Threshold Destructive Confirmation

It avoids unnecessary or constant vibration.

The skill creates microinteraction systems.

Potential microinteractions include:

Button Press Toggle Change Tab Change Favorite Reaction Save Add Remove Selection Progress Reorder Success Error

Every microinteraction can define:

Trigger Visual Response Motion Haptic Duration Accessibility Alternative

Motion is used to:

Show Causality Preserve Orientation Clarify Hierarchy Confirm Action

It avoids:

Excessive Springs Decorative Delays Long Transitions Animation Blocking Input Motion Applied to Every Element

Reduced-motion behavior is defined.

The skill creates complete loading-state architecture.

Possible loading contexts include:

App Launch Screen Load Pagination Action Processing File Upload Data Synchronization Media

Patterns may include:

Skeleton Inline Spinner Determinate Progress Background Progress

The appropriate pattern depends on expected duration and layout certainty.

It avoids unnecessary splash delays.

The skill creates pagination and infinite-scroll behavior.

Infinite scrolling can define:

Position Preservation Loading State Retry End State Error Recovery

The skill creates differentiated empty states.

First-Use Empty: Nothing has been created yet.

Filtered Empty: Data exists but filters return no results.

Completed Empty: All work is finished.

Permission Empty: User lacks access.

Error Empty: Content cannot load.

Each receives different messaging and actions.

The skill creates complete error architecture.

Potential error types include:

Network Error Validation Error Permission Error Server Error Payment Error Sync Error Unavailable Content Expired Session

Good errors explain:

What Happened What Was Preserved What the User Can Do What Happens Next

The skill defines offline UX only when supported.

Potential offline behaviors include:

Offline Indicator Available Local Actions Queued Changes Synchronization State Conflict Handling

The skill never assumes offline support exists.

Sync UX can define:

Syncing Synced Failed Conflict Last Updated

The skill designs notification architecture.

It can define:

Notification Value Timing Category Deep-Link Destination Settings Permission Timing

Notification permission should not be requested before users understand its value.

In-app notifications can use:

Badge Inbox Banner Toast Notification Center

The skill avoids permanent meaningless red badges.

Notification preferences can be grouped according to value and category.

The skill creates mobile search architecture.

It can define:

Entry Focus Recent Searches Suggestions History Results Filters No Results Error State

Mobile search controls should be easy to focus and dismiss.

The skill creates filter architecture using:

Bottom Sheets Full-Screen Filters Quick Filter Chips

Filter behavior can be:

Live Apply Explicit Apply

depending on performance and complexity.

Active filters should always remain visible.

Sorting can remain separate when it matches the user's mental model.

Saved searches and saved views may be included for expert workflows.

The skill supports media-heavy applications.

Potential behaviors include:

Reading Progress Resume Save Share Download

only when supported.

Camera workflows can include:

Permission Education Capture Guidance Retake Confirmation Upload Progress Error Recovery

File uploads can define:

Source Supported Formats Size Limits Validation Progress Failure Retry

The skill designs location UX.

It can define:

Value Explanation Permission Request Denied State Manual Fallback Approximate vs Precise Behavior

only when technically relevant.

Map UX can include:

Markers Selected Marker Detail Sheet Search This Area Recenter List/Map Toggle

The skill creates messaging UX.

Potential components include:

Conversation List Thread Composer Attachment Typing State Delivery State Read State Error State

It does not invent messaging delivery guarantees.

The skill creates AI-specific mobile UX.

Potential states include:

Input Generation Streaming Cancel Regenerate Edit Save Copy Share Sources Uncertainty Feedback Error History

AI controls are prioritized for small screens rather than exposing every possible function simultaneously.

AI input can support:

Text Voice Attachment Camera

only when those modalities are real.

AI results can prioritize:

Readability Primary Follow-Up Sources Where Relevant Copy Share Save

The skill supports ecommerce applications.

Core ecommerce flows can include:

Discovery Search Category Product Detail Variants Cart Checkout Payment Shipping Order Status Returns

Product detail pages prioritize:

Product Price Variant Proof Shipping

CTA

Cart architecture can include:

Items Quantity Price Discount Shipping Information Total

Checkout UX focuses on:

Reduced Field Count No Repeated Data Clear Progress Payment Confidence Error Recovery Confirmation

The skill supports subscription apps.

Potential subscription UX includes:

Plan Billing Frequency Trial Renewal Cancellation Restore Purchase

Only authoritative commercial terms should be displayed.

The skill supports fintech mobile apps.

Fintech workflows emphasize:

Trust Financial Consequence Review Authentication Processing Confirmation Error Prevention

A high-consequence transaction may follow:

Input → Review → Authentication → Processing → Result

The skill does not remove review merely to reduce taps.

The skill supports health and wellness products.

Priorities include:

Sensitive Data Privacy Non-Judgmental Language Accessible Progress Low-Stress Interactions Reminders

The skill supports EdTech.

Priorities include:

Next Lesson Progress Resume Assessments Feedback Accessibility Offline Learning Where Supported

The skill supports productivity apps.

Priorities include:

Quick Capture Create Task Lists Filters Reminders Keyboard Efficiency Widgets Where Supported

The skill supports enterprise mobile products.

Mobile may prioritize:

Approvals Alerts Task Review Comments Status Changes Quick Search

Complex configuration may remain tablet or desktop-first when appropriate.

The skill creates dedicated tablet architecture.

Tablet UI should not simply stretch phone layouts.

Potential patterns include:

Sidebar + Detail Master-Detail Multi-Column Persistent Inspector Split View

Tablet navigation can use:

Sidebar → Content List → Detail

The skill defines orientation only where useful.

Landscape may be useful for:

Video Data Drawing Tablet Workflows

The skill avoids mandatory landscape support without product value.

Foldable and large-screen behavior can include:

Adaptive Panes Controlled Content Width Hinge Awareness Multi-Column Layout

when required.

The skill creates explicit iOS adaptation.

Potential iOS considerations include:

Navigation Stacks Tab Bars Sheets Large Titles Where Appropriate Swipe Back Context Menus System Pickers Safe Areas Dynamic Type VoiceOver

The skill does not blindly impose Android conventions on iOS.

The skill creates explicit Android adaptation.

Potential Android considerations include:

System Back Predictive Back Where Relevant Gesture Navigation Area Bottom Navigation Modal Sheets Material-Oriented Patterns Adaptive Layouts TalkBack

The skill does not blindly imitate iOS patterns.

The skill creates a shared cross-platform system.

Shared elements may include:

Information Architecture Brand Terminology Business Rules Core Flows Content Hierarchy

Platform-specific adaptation may include:

Navigation Sheets Dialogs Pickers System Prompts Back Behavior Typography Metrics Platform Icons

A platform-consistency matrix can define:

Pattern Shared Rule iOS Behavior Android Behavior Reason

The skill creates responsive phone behavior for:

Small Phones Standard Phones Large Phones

It checks:

Line Length CTA Visibility Keyboard Safe Areas Sheet Heights Card Width Text Truncation

The skill supports system text scaling.

Layouts should tolerate:

Longer Text Larger Accessibility Text Multiline Labels Expanded Buttons Reflow

The skill avoids fixed-height text containers that break at larger text sizes.

The skill creates mobile accessibility requirements.

Potential requirements include:

Screen-Reader Names Logical Reading Order Adequate Touch Targets Contrast Dynamic Type or Scalable Text Color-Independent Status Reduced Motion Error Identification Accessible Gestures

Custom icon buttons should have meaningful accessible names.

Essential gestures require accessible alternatives.

Status should never depend only on color.

The skill creates a complete mobile design system.

Foundations:

Color Typography Spacing Grid Radius Elevation Motion Iconography Haptics

Core components:

Top App Bar Bottom Navigation Tab Segmented Control Button Icon Button Text Field Search Field Checkbox Radio Switch Chip Badge List Row Card Bottom Sheet Dialog Snackbar Toast Banner Progress Skeleton Empty State

Advanced components can include:

Date Picker Time Picker Upload Media Controls Map Marker Chat Composer AI Input Attachment Chip Payment Summary Stepper Filter Sheet

Every component can define:

Default Pressed Focused Selected Disabled Loading Success Error Empty

The skill creates clear button hierarchy.

Possible levels:

Primary Secondary Tertiary Destructive

It avoids unnecessary button variants.

Iconography is evaluated for:

Recognizability Consistency Weight Platform Convention Label Requirements

The skill creates premium visual hierarchy through:

Spacing Scale Weight Grouping Contrast Motion

It avoids using excessive cards, blur, glass effects, gradients, or animation simply to appear premium.

Premium mobile design is defined by:

Clarity Consistency Restraint Precise Spacing Strong Typography Polished States Predictable Interaction Coherent Motion Trust

The skill creates color systems for:

Brand Primary Action Surface Elevated Surface Text Secondary Text Border Success Warning Error Information

The skill creates semantic typography systems.

Potential roles:

Display Screen Title Section Title Card Title Body Label Helper Metadata Button

The skill creates motion systems for:

Navigation Sheets Dialogs Selection Expansion Reordering Success Loading

The skill enforces state completeness.

Every important screen should consider:

First Use Returning User Loading Empty Error Offline Permission Denied Restricted Success Partial Success

The skill explicitly designs interrupted-task recovery.

Mobile users may be interrupted by:

App Backgrounding Phone Calls Network Changes Authentication Expiry Permission Prompts Keyboard Changes

The interface should preserve progress where feasible.

Long creation flows may support:

Autosave Draft Resume Discard

only when technically supported.

The skill considers app lifecycle states:

Cold Start Warm Start Foreground Background Session Restore Deep Link Notification Entry

Session-expiry UX can include:

Warning Reauthentication Preserved Work

The skill creates help and support architecture.

Potential surfaces include:

Contextual Help

FAQ

Contact Report Issue Chat

Support should not be buried in Settings when task-level help is required.

Settings architecture can include:

Account Notifications Privacy Appearance Security Subscription Help About

Only real capabilities should appear.

Profile architecture can include:

Identity Avatar Preferences Activity Account Details

Privacy settings must reflect actual available controls.

The skill also performs mobile UX audits.

Audit categories include:

Navigation Screen Hierarchy Reachability Onboarding Forms Gestures States Platform Consistency Accessibility Visual System Tablet Adaptation Errors Loading Notification Entry Deep Links Keyboard Behavior

Findings can be classified:

Critical High Medium Low

Each finding can include:

Screen Evidence User Impact Root Cause Concrete Redesign Platform Note Validation

The skill can produce complete redesign blueprints.

Potential output includes:

App Primary User Core Job Navigation Onboarding Home Core Flows Primary CTA Gestures States iOS Behavior Android Behavior Tablet Behavior Accessibility Design System

The skill creates implementation-ready screen specifications.

Every important screen can define:

Purpose Entry Exit Primary Action Secondary Actions Layout Components States Gestures Microinteractions Keyboard Permissions iOS Behavior Android Behavior Tablet Behavior Accessibility

The skill creates user-flow specifications.

Each flow can define:

Goal Entry Steps Decision Success Failure Recovery Deep Link

It creates navigation specifications.

Possible fields:

Primary Pattern Top-Level Destinations Secondary Navigation Back Behavior Deep-Link Behavior State Preservation iOS Android

It creates onboarding specifications.

Possible fields:

Goal Steps Permission Education Activation Skip Returning-User Behavior

It creates microinteraction specifications.

Possible fields:

Trigger Response Motion Haptic Duration Reduced-Motion Alternative

It creates responsive matrices across:

Small Phone Standard Phone Large Phone Tablet Portrait Tablet Landscape

Supported operating modes include:

Full Mobile App UX Architecture: Creates roles, jobs, flows, screen inventory, navigation, onboarding, states, and platform behavior.

iOS Interface Director: Focuses on navigation, sheets, gestures, safe areas, Dynamic Type, VoiceOver, and iOS conventions.

Android Interface Director: Focuses on Android navigation, back behavior, sheets, adaptive layouts, Material-oriented patterns where appropriate, and TalkBack.

Cross-Platform Mobile Design System: Creates shared product rules with platform-specific adaptation.

Mobile Onboarding Architect: Designs first-use value, activation, permission timing, setup, and progressive education.

Mobile Navigation Architect: Designs bottom navigation, stacks, tabs, drawers, deep links, back behavior, and state preservation.

Mobile Interaction & Gesture Director: Defines gestures, haptics, microinteractions, motion, and accessible alternatives.

Mobile UX Auditor: Audits existing apps for navigation, reachability, forms, state completeness, accessibility, and platform consistency.

Mobile Commerce / Subscription Director: Focuses on discovery, cart, checkout, payment, subscriptions, restore, cancellation, and trust.

Tablet & Large-Screen Architect: Creates master-detail, sidebar, split-view, multi-pane, adaptive, and orientation behavior.

The core commercial promise is: transform an app concept into a coherent, premium, state-complete mobile product system where flows, navigation, onboarding, gestures, feedback, platform conventions, responsive behavior, and accessibility work together from first launch through recurring use.