Mobile Design System
A unified mobile design system covering UX patterns, React Native implementation, visual design process, and platform conventions for iOS and Android.
When to Use This Skill
Activate this skill when the task involves:
- Building mobile apps with React Native, Flutter, or SwiftUI
- Designing mobile screens -- layouts, flows, onboarding, dashboards
- Implementing touch interactions -- gestures, swipe actions, pinch-to-zoom
- Reviewing mobile UX -- auditing touch targets, thumb zones, accessibility
- Following platform conventions -- iOS Human Interface Guidelines, Material Design
- Creating responsive mobile-first web apps or Progressive Web Apps
- Optimizing mobile performance -- images, loading states, Core Web Vitals
- Mobile accessibility -- screen readers, contrast, Dynamic Type, VoiceOver/TalkBack
Core Philosophy
Mobile UI is about touch, speed, and focus. There are no hover states. Screens are small. Users operate one-handed, often distracted, on unreliable networks. Every design decision must account for these constraints.
Three questions before designing any screen:
- What is the user trying to accomplish? Reduce friction to that goal.
- How should this make the user feel? Trust, delight, confidence, calm.
- What should they notice first? Establish clear visual hierarchy.
Foundational Rules
Touch Targets (Non-Negotiable)
All interactive elements must meet minimum touch target sizes:
| Platform |
Minimum |
Optimal |
Spacing |
| iOS (HIG) |
44x44 pt |
56x56 pt |
8pt |
| Android (Material) |
48x48 dp |
56x56 dp |
8dp |
| Web (WCAG 2.1 AAA) |
44x44 px |
48x48 px |
8px |
Never create buttons, links, or icon buttons smaller than these minimums. Use minHeight and minWidth rather than fixed dimensions so content can grow with Dynamic Type.
Thumb Zones
Mobile screens have three ergonomic zones for one-handed use:
- Easy zone (bottom center): Place primary actions here -- CTAs, tab bars, submit buttons
- Stretch zone (middle): Content area, form fields, secondary actions
- Difficult zone (top corners): Destructive actions, infrequent navigation, settings
Spacing: 4px/8px Grid
All spacing values must be divisible by 4 or 8: 4, 8, 12, 16, 24, 32, 48, 64, 80, 96.
- Related elements: closer together (8-16px)
- Unrelated groups: further apart (24-48px)
- Section padding: 80-96px vertical minimum
- Card internal padding: 24-32px
Color: 60/30/10 Rule
- 60% neutral base (white, light gray, or dark background)
- 30% complementary (text, dark elements)
- 10% accent/brand (CTAs, key indicators)
Use opacity variations for text hierarchy: 100% headings, 80% body, 60% secondary.
Typography Constraints
- One font family (two maximum with clear hierarchy purpose)
- Maximum 4 font sizes and 2 font weights
- Minimum 16px font size on web to prevent iOS auto-zoom
- Use monospace variants for large numbers (prices, stats, metrics)
Accessibility (Non-Negotiable)
- Color contrast: 4.5:1 for normal text, 3:1 for large text (WCAG AA)
- Every interactive element needs accessibility labels
- Every
Pressable/button needs a visible pressed state
- Support Dynamic Type / font scaling
- Test with VoiceOver (iOS) and TalkBack (Android)
Design Process
Follow this sequence for any mobile screen:
1. Understand Context
- App type (fitness, finance, social, productivity, health, crypto)
- User stage (new, returning, power user)
- Primary action on this screen
- Industry conventions (see
references/design-process.md and references/industry-conventions.md)
2. Structure First (UX)
- Map the user flow: what comes before and after this screen
- Identify MVP elements -- only what is essential
- Place primary actions in the thumb zone
- Follow F-pattern reading order
- Turn empty states into opportunities (guidance + illustration + CTA)
3. Apply Visual Design (UI)
- Typography hierarchy with size, weight, and opacity
- 60/30/10 color application
- 8-point grid spacing
- Soft shadows matched to background tint (never pure gray/black)
- Visual cues: icons, images, color-coded categories
4. Design for Emotion (Peak-End Rule)
Users remember two moments: the peak (most intense) and the end (last impression).
- Design peak moments: micro-animations, celebratory feedback, personalized insights
- Design endings: summary cards, progress affirmation, gentle nudges to return
- Add emotional feedback loops: success states should feel rewarding
5. Polish
- Micro-animations for state changes (200-300ms, native driver)
- All states designed: loading (skeleton screens), empty, error, success
- Safe area handling (notch, home indicator)
- Dark mode support with semantic colors
- Platform-appropriate styling (iOS shadows vs Android elevation)
Platform Quick Reference
iOS (Human Interface Guidelines)
- SF Pro system font, Dynamic Type required
- Large titles (34pt), navigation bars with back buttons
- Tab bars: 5 items max, always show labels
- Blue (#007AFF) for tappable elements, Red (#FF3B30) for destructive
- Edge swipe for back navigation
- Rounded corners: 10-14pt
Android (Material Design 3)
- Roboto font family, Material You dynamic color
- FAB for primary actions (56x56dp)
- Bottom navigation for 3-5 destinations
- Elevation system (shadows indicate hierarchy: 0-24dp)
- Rounded corners: 12-28pt
Cross-Platform (React Native)
- Use
Platform.select() for iOS/Android differences
useSafeAreaInsets() for safe areas
useNativeDriver: true for 60fps animations
StyleSheet.create() over inline styles
Pressable with visible pressed states
Anti-Patterns
- Touch targets smaller than 44pt
- Placing primary actions in top corners (outside thumb zone)
- More than 4 font sizes or 3 font weights
- Random spacing values (not on the 4px/8px grid)
- Invisible buttons (transparent background without border)
- Hover-dependent interactions (no hover on mobile)
- Fixed heights that break with Dynamic Type
- Pure gray/black shadows on colored backgrounds
- Ignoring safe areas (notch, home indicator)
- JS-driven animations instead of native driver
Reference Guides
This skill includes detailed reference files for deep dives. Load them as needed:
| Reference |
Use When |
Content |
references/react-native-patterns.md |
Implementing React Native UI |
Components, animations, accessibility, platform-specific code, Reanimated patterns |
references/ux-patterns.md |
Designing mobile interactions |
Touch gestures (tap, swipe, pinch, long press, drag), navigation patterns, mobile forms, performance optimization |
references/design-process.md |
Running a mobile design process |
5-step design framework, visual design rules, emotional design, smart UI patterns, implementation notes |
references/industry-conventions.md |
Designing for specific industries |
Industry-specific design languages (AI, crypto, finance, health, education, fitness), Peak-End Rule, Spotify strategic principles |
Example Output
When reviewing a mobile screen, produce findings like this:
Design Review — Login Screen
✅ Touch targets: All buttons meet 44pt minimum
⚠️ Spacing: 12px gap between form fields → should be 16px (8pt grid)
❌ Contrast: Secondary text (#999) on white is 2.6:1 → needs 4.5:1 minimum
✅ Typography: 2 weights, 3 sizes — clean hierarchy
⚠️ CTA position: "Sign In" is above thumb zone → move to bottom third
✅ Accessibility: All inputs have labels
❌ Missing state: No error state for invalid credentials
✅ Safe area: Properly handled for notch devices
Score: 6.5/10 — 3 fixes needed for production quality
Priority: contrast fix > CTA position > spacing alignment
Related Design Skills
- ios-glass-ui: For iOS-specific glass material design (translucency, blur, depth)
- ui-ux-polish: For iterative visual polishing of existing UIs toward production quality
Quick Checklist
[ ] All touch targets >= 44pt (48pt preferred)
[ ] Primary actions in thumb zone (bottom 1/3)
[ ] Spacing on 4px/8px grid
[ ] Color contrast >= 4.5:1 for text
[ ] Accessibility labels on all interactive elements
[ ] Visible pressed/active states on all buttons
[ ] Safe area handling (notch, home indicator)
[ ] Loading states (skeleton screens)
[ ] Error states with clear guidance
[ ] Empty states with illustration + CTA
[ ] Dark mode support
[ ] Dynamic Type / font scaling
[ ] Native driver animations (60fps)
[ ] Platform-appropriate styling
[ ] 16px minimum font size (web, prevents iOS zoom)
1---2name: mobile-design-system3description: "Comprehensive mobile UI/UX design system covering React Native components, touch interactions, gesture patterns, accessibility, app navigation, and visual design principles. Use when building mobile apps, designing mobile screens, implementing React Native UI, reviewing mobile UX, or following iOS/Android platform conventions. Triggers: mobile UI, React Native, app design, mobile UX, touch targets, mobile patterns, app screen design."4license: MIT5metadata:6 source: https://skillmd.com/skills/juanmarchetto/mobile-design-system7 version: 1.0.08 category: design9 tags: [mobile, react-native, ios, android, ux, ui, design, accessibility, touch, gestures]10---1112# Mobile Design System1314A unified mobile design system covering UX patterns, React Native implementation, visual design process, and platform conventions for iOS and Android.1516## When to Use This Skill1718Activate this skill when the task involves:1920- **Building mobile apps** with React Native, Flutter, or SwiftUI21- **Designing mobile screens** -- layouts, flows, onboarding, dashboards22- **Implementing touch interactions** -- gestures, swipe actions, pinch-to-zoom23- **Reviewing mobile UX** -- auditing touch targets, thumb zones, accessibility24- **Following platform conventions** -- iOS Human Interface Guidelines, Material Design25- **Creating responsive mobile-first web apps** or Progressive Web Apps26- **Optimizing mobile performance** -- images, loading states, Core Web Vitals27- **Mobile accessibility** -- screen readers, contrast, Dynamic Type, VoiceOver/TalkBack2829## Core Philosophy3031Mobile UI is about touch, speed, and focus. There are no hover states. Screens are small. Users operate one-handed, often distracted, on unreliable networks. Every design decision must account for these constraints.3233Three questions before designing any screen:34351. **What is the user trying to accomplish?** Reduce friction to that goal.362. **How should this make the user feel?** Trust, delight, confidence, calm.373. **What should they notice first?** Establish clear visual hierarchy.3839## Foundational Rules4041### Touch Targets (Non-Negotiable)4243All interactive elements must meet minimum touch target sizes:4445| Platform | Minimum | Optimal | Spacing |46|----------|---------|---------|---------|47| iOS (HIG) | 44x44 pt | 56x56 pt | 8pt |48| Android (Material) | 48x48 dp | 56x56 dp | 8dp |49| Web (WCAG 2.1 AAA) | 44x44 px | 48x48 px | 8px |5051Never create buttons, links, or icon buttons smaller than these minimums. Use `minHeight` and `minWidth` rather than fixed dimensions so content can grow with Dynamic Type.5253### Thumb Zones5455Mobile screens have three ergonomic zones for one-handed use:5657- **Easy zone** (bottom center): Place primary actions here -- CTAs, tab bars, submit buttons58- **Stretch zone** (middle): Content area, form fields, secondary actions59- **Difficult zone** (top corners): Destructive actions, infrequent navigation, settings6061### Spacing: 4px/8px Grid6263All spacing values must be divisible by 4 or 8: `4, 8, 12, 16, 24, 32, 48, 64, 80, 96`.6465- Related elements: closer together (8-16px)66- Unrelated groups: further apart (24-48px)67- Section padding: 80-96px vertical minimum68- Card internal padding: 24-32px6970### Color: 60/30/10 Rule7172- **60%** neutral base (white, light gray, or dark background)73- **30%** complementary (text, dark elements)74- **10%** accent/brand (CTAs, key indicators)7576Use opacity variations for text hierarchy: 100% headings, 80% body, 60% secondary.7778### Typography Constraints7980- **One font family** (two maximum with clear hierarchy purpose)81- **Maximum 4 font sizes** and **2 font weights**82- Minimum 16px font size on web to prevent iOS auto-zoom83- Use monospace variants for large numbers (prices, stats, metrics)8485### Accessibility (Non-Negotiable)8687- Color contrast: 4.5:1 for normal text, 3:1 for large text (WCAG AA)88- Every interactive element needs accessibility labels89- Every `Pressable`/button needs a visible pressed state90- Support Dynamic Type / font scaling91- Test with VoiceOver (iOS) and TalkBack (Android)9293## Design Process9495Follow this sequence for any mobile screen:9697### 1. Understand Context98- App type (fitness, finance, social, productivity, health, crypto)99- User stage (new, returning, power user)100- Primary action on this screen101- Industry conventions (see `references/design-process.md` and `references/industry-conventions.md`)102103### 2. Structure First (UX)104- Map the user flow: what comes before and after this screen105- Identify MVP elements -- only what is essential106- Place primary actions in the thumb zone107- Follow F-pattern reading order108- Turn empty states into opportunities (guidance + illustration + CTA)109110### 3. Apply Visual Design (UI)111- Typography hierarchy with size, weight, and opacity112- 60/30/10 color application113- 8-point grid spacing114- Soft shadows matched to background tint (never pure gray/black)115- Visual cues: icons, images, color-coded categories116117### 4. Design for Emotion (Peak-End Rule)118Users remember two moments: the **peak** (most intense) and the **end** (last impression).119- Design peak moments: micro-animations, celebratory feedback, personalized insights120- Design endings: summary cards, progress affirmation, gentle nudges to return121- Add emotional feedback loops: success states should feel rewarding122123### 5. Polish124- Micro-animations for state changes (200-300ms, native driver)125- All states designed: loading (skeleton screens), empty, error, success126- Safe area handling (notch, home indicator)127- Dark mode support with semantic colors128- Platform-appropriate styling (iOS shadows vs Android elevation)129130## Platform Quick Reference131132### iOS (Human Interface Guidelines)133- SF Pro system font, Dynamic Type required134- Large titles (34pt), navigation bars with back buttons135- Tab bars: 5 items max, always show labels136- Blue (#007AFF) for tappable elements, Red (#FF3B30) for destructive137- Edge swipe for back navigation138- Rounded corners: 10-14pt139140### Android (Material Design 3)141- Roboto font family, Material You dynamic color142- FAB for primary actions (56x56dp)143- Bottom navigation for 3-5 destinations144- Elevation system (shadows indicate hierarchy: 0-24dp)145- Rounded corners: 12-28pt146147### Cross-Platform (React Native)148- Use `Platform.select()` for iOS/Android differences149- `useSafeAreaInsets()` for safe areas150- `useNativeDriver: true` for 60fps animations151- `StyleSheet.create()` over inline styles152- `Pressable` with visible pressed states153154## Anti-Patterns155156- Touch targets smaller than 44pt157- Placing primary actions in top corners (outside thumb zone)158- More than 4 font sizes or 3 font weights159- Random spacing values (not on the 4px/8px grid)160- Invisible buttons (transparent background without border)161- Hover-dependent interactions (no hover on mobile)162- Fixed heights that break with Dynamic Type163- Pure gray/black shadows on colored backgrounds164- Ignoring safe areas (notch, home indicator)165- JS-driven animations instead of native driver166167## Reference Guides168169This skill includes detailed reference files for deep dives. Load them as needed:170171| Reference | Use When | Content |172|-----------|----------|---------|173| `references/react-native-patterns.md` | Implementing React Native UI | Components, animations, accessibility, platform-specific code, Reanimated patterns |174| `references/ux-patterns.md` | Designing mobile interactions | Touch gestures (tap, swipe, pinch, long press, drag), navigation patterns, mobile forms, performance optimization |175| `references/design-process.md` | Running a mobile design process | 5-step design framework, visual design rules, emotional design, smart UI patterns, implementation notes |176| `references/industry-conventions.md` | Designing for specific industries | Industry-specific design languages (AI, crypto, finance, health, education, fitness), Peak-End Rule, Spotify strategic principles |177178## Example Output179180When reviewing a mobile screen, produce findings like this:181182```183Design Review — Login Screen184185✅ Touch targets: All buttons meet 44pt minimum186⚠️ Spacing: 12px gap between form fields → should be 16px (8pt grid)187❌ Contrast: Secondary text (#999) on white is 2.6:1 → needs 4.5:1 minimum188✅ Typography: 2 weights, 3 sizes — clean hierarchy189⚠️ CTA position: "Sign In" is above thumb zone → move to bottom third190✅ Accessibility: All inputs have labels191❌ Missing state: No error state for invalid credentials192✅ Safe area: Properly handled for notch devices193194Score: 6.5/10 — 3 fixes needed for production quality195Priority: contrast fix > CTA position > spacing alignment196```197198## Related Design Skills199200- **ios-glass-ui**: For iOS-specific glass material design (translucency, blur, depth)201- **ui-ux-polish**: For iterative visual polishing of existing UIs toward production quality202203## Quick Checklist204205```206[ ] All touch targets >= 44pt (48pt preferred)207[ ] Primary actions in thumb zone (bottom 1/3)208[ ] Spacing on 4px/8px grid209[ ] Color contrast >= 4.5:1 for text210[ ] Accessibility labels on all interactive elements211[ ] Visible pressed/active states on all buttons212[ ] Safe area handling (notch, home indicator)213[ ] Loading states (skeleton screens)214[ ] Error states with clear guidance215[ ] Empty states with illustration + CTA216[ ] Dark mode support217[ ] Dynamic Type / font scaling218[ ] Native driver animations (60fps)219[ ] Platform-appropriate styling220[ ] 16px minimum font size (web, prevents iOS zoom)221```