Mobile Design Skill
This skill guides creation of distinctive, production-grade mobile interfaces that feel native to the platform while maintaining a unique aesthetic identity. Implement real working code with exceptional attention to platform conventions and creative design choices.
The user provides mobile UI requirements: a screen, widget, feature, or complete app interface. They may include context about the platform (iOS/Android), audience, or technical constraints.
Design Thinking
Before coding, understand the context and commit to a platform-aware aesthetic direction:
- Platform: iOS (Cupertino), Android (Material 3), or cross-platform? Each has distinct expectations.
- Tone: Pick a direction — refined luxury, playful/energetic, utilitarian/efficient, editorial/content-first, organic/warm, bold/geometric, soft/pastel, etc.
- Constraints: Performance on low-end devices, offline capability, accessibility.
- Differentiation: What makes this app memorable? What's the signature interaction?
CRITICAL: Mobile users have muscle memory. Respect platform conventions (navigation patterns, gesture zones, system UI) while injecting personality through typography, color, motion, and layout composition.
Mobile Design Guidelines
Platform Conventions
- iOS: Bottom tab bar, large title navigation, swipe-to-go-back, Cupertino widgets
- Android: Material 3, navigation rail/drawer, FAB, top app bar
- Cross-platform: Use adaptive widgets that render platform-appropriate UI
Typography
- Choose distinctive but highly readable fonts at mobile sizes (16px+ body)
- Respect dynamic type / font scaling — never hardcode font sizes
- Use
TextTheme in Flutter, keep a consistent type scale
- Pair a characterful display font with a supremely legible body font
Color & Theme
- Support both light and dark themes — always
- Use
ColorScheme / ThemeData for consistency
- Ensure contrast ratios work on OLED (pure black) and LCD displays
- Use color purposefully — primary actions, status indicators, brand identity
Motion & Animation
- Use meaningful motion — animations should communicate state changes, not decorate
- Keep animations under 300ms for interactions, up to 500ms for transitions
- Use
Hero animations for shared element transitions
- Stagger list item animations for visual polish
- Respect
reduceMotion / accessibility settings — always provide a static fallback
Layout & Spacing
- Design for one-handed use — critical actions in thumb-reach zone (bottom 60% of screen)
- Use safe area insets — never overlap system UI (notch, home indicator, status bar)
- Design for varying screen sizes — phones, tablets, foldables
- Use responsive breakpoints: compact (<600dp), medium (600-840dp), expanded (>840dp)
- Generous touch targets: minimum 48x48dp
Performance
- Avoid rebuilding expensive widget trees — use
const constructors
- Lazy-load lists with
ListView.builder (never ListView for large lists)
- Optimize images — use
cached_network_image, proper resolution variants
- Profile on real devices, not just emulators
Flutter-Specific Patterns
// ✅ Good: Adaptive widget that respects platform
Widget buildButton(BuildContext context) {
return Platform.isIOS
? CupertinoButton(child: text, onPressed: onTap)
: ElevatedButton(child: text, onPressed: onTap);
}
// ✅ Good: Responsive layout with breakpoints
Widget build(BuildContext context) {
final width = MediaQuery.of(context).size.width;
if (width >= 840) return _expandedLayout();
if (width >= 600) return _mediumLayout();
return _compactLayout();
}
// ❌ Bad: Hardcoded sizes that break on different devices
Container(width: 375, height: 812) // iPhone X only!
Rule Compliance
Before implementing, verify against:
- Project Structure @project-structure.md (Flutter/Mobile layout, feature organization)
- Testing Strategy @testing-strategy.md (widget tests, integration tests)
- Security Principles @security-principles.md (secure storage, API key handling)
- Accessibility Principles @accessibility-principles.md (screen reader, dynamic type, contrast)
- Architectural Patterns @architectural-pattern.md (BLoC/Cubit, repository pattern)
IMPORTANT: Mobile has unique constraints — battery life, network variability, and user context (one-handed, on-the-go). Every design choice should respect these realities. Beautiful UI that drains battery or stutters on scroll is a failure.
Remember: The best mobile apps feel like they were designed specifically for the device in your hand. Make every pixel and every interaction intentional.
1---2name: mobile-design-43description: Generates distinctive, production-grade mobile interfaces for Flutter and React Native. Prioritizes platform-native patterns, adaptive layouts, and fluid motion. Use when building mobile apps, screens, widgets, or when the user requests to style or create visually striking mobile UI.4metadata:5 source: https://skillmd.com/skills/irahardianto/mobile-design-46---78# Mobile Design Skill910This skill guides creation of distinctive, production-grade mobile interfaces that feel native to the platform while maintaining a unique aesthetic identity. Implement real working code with exceptional attention to platform conventions and creative design choices.1112The user provides mobile UI requirements: a screen, widget, feature, or complete app interface. They may include context about the platform (iOS/Android), audience, or technical constraints.1314## Design Thinking1516Before coding, understand the context and commit to a platform-aware aesthetic direction:17- **Platform**: iOS (Cupertino), Android (Material 3), or cross-platform? Each has distinct expectations.18- **Tone**: Pick a direction — refined luxury, playful/energetic, utilitarian/efficient, editorial/content-first, organic/warm, bold/geometric, soft/pastel, etc.19- **Constraints**: Performance on low-end devices, offline capability, accessibility.20- **Differentiation**: What makes this app memorable? What's the signature interaction?2122**CRITICAL**: Mobile users have muscle memory. Respect platform conventions (navigation patterns, gesture zones, system UI) while injecting personality through typography, color, motion, and layout composition.2324## Mobile Design Guidelines2526### Platform Conventions27- **iOS**: Bottom tab bar, large title navigation, swipe-to-go-back, Cupertino widgets28- **Android**: Material 3, navigation rail/drawer, FAB, top app bar29- **Cross-platform**: Use adaptive widgets that render platform-appropriate UI3031### Typography32- Choose distinctive but highly readable fonts at mobile sizes (16px+ body)33- Respect dynamic type / font scaling — never hardcode font sizes34- Use `TextTheme` in Flutter, keep a consistent type scale35- Pair a characterful display font with a supremely legible body font3637### Color & Theme38- Support **both light and dark themes** — always39- Use `ColorScheme` / `ThemeData` for consistency40- Ensure contrast ratios work on OLED (pure black) and LCD displays41- Use color purposefully — primary actions, status indicators, brand identity4243### Motion & Animation44- Use **meaningful motion** — animations should communicate state changes, not decorate45- Keep animations under 300ms for interactions, up to 500ms for transitions46- Use `Hero` animations for shared element transitions47- Stagger list item animations for visual polish48- Respect `reduceMotion` / accessibility settings — always provide a static fallback4950### Layout & Spacing51- Design for **one-handed use** — critical actions in thumb-reach zone (bottom 60% of screen)52- Use safe area insets — never overlap system UI (notch, home indicator, status bar)53- Design for varying screen sizes — phones, tablets, foldables54- Use responsive breakpoints: compact (<600dp), medium (600-840dp), expanded (>840dp)55- Generous touch targets: minimum 48x48dp5657### Performance58- Avoid rebuilding expensive widget trees — use `const` constructors59- Lazy-load lists with `ListView.builder` (never `ListView` for large lists)60- Optimize images — use `cached_network_image`, proper resolution variants61- Profile on real devices, not just emulators6263## Flutter-Specific Patterns6465```dart66// ✅ Good: Adaptive widget that respects platform67Widget buildButton(BuildContext context) {68 return Platform.isIOS69 ? CupertinoButton(child: text, onPressed: onTap)70 : ElevatedButton(child: text, onPressed: onTap);71}7273// ✅ Good: Responsive layout with breakpoints74Widget build(BuildContext context) {75 final width = MediaQuery.of(context).size.width;76 if (width >= 840) return _expandedLayout();77 if (width >= 600) return _mediumLayout();78 return _compactLayout();79}8081// ❌ Bad: Hardcoded sizes that break on different devices82Container(width: 375, height: 812) // iPhone X only!83```8485## Rule Compliance86Before implementing, verify against:87- Project Structure @project-structure.md (Flutter/Mobile layout, feature organization)88- Testing Strategy @testing-strategy.md (widget tests, integration tests)89- Security Principles @security-principles.md (secure storage, API key handling)90- Accessibility Principles @accessibility-principles.md (screen reader, dynamic type, contrast)91- Architectural Patterns @architectural-pattern.md (BLoC/Cubit, repository pattern)9293**IMPORTANT**: Mobile has unique constraints — battery life, network variability, and user context (one-handed, on-the-go). Every design choice should respect these realities. Beautiful UI that drains battery or stutters on scroll is a failure.9495Remember: The best mobile apps feel like they were designed specifically for the device in your hand. Make every pixel and every interaction intentional.