Mobile Design System
Philosophy: Touch-first. Battery-conscious. Platform-respectful. Offline-capable.
Core Principle: Mobile is not a small desktop. Think in mobile constraints; ask about platform choice.
Audit Script
Run this for validation (no need to read the source):
| Command |
Purpose |
Usage |
cardume-mobile-audit |
Mobile UX & touch audit |
cardume-mobile-audit <project_path> |
Reference Files: Read What the Task Needs
Before writing code, read the reference files relevant to the task. Start with mobile-design-thinking.md for any new screen or app — it counters memorized defaults by forcing context-based decisions.
Core
| File |
Content |
When to Read |
| mobile-design-thinking.md |
Anti-memorization: context-based thinking instead of AI defaults |
First, for new screens/apps |
| touch-psychology.md |
Fitts' Law, gestures, haptics, thumb zone |
Any interactive UI |
| mobile-performance.md |
RN/Flutter performance, 60fps, memory |
Lists, animations, perf work |
| mobile-backend.md |
Push notifications, offline sync, mobile API |
Data layer, sync, notifications |
| mobile-testing.md |
Testing pyramid, E2E, platform-specific |
Writing or planning tests |
| mobile-debugging.md |
Native vs JS debugging, React Native DevTools, Logcat |
Investigating bugs/crashes |
| mobile-navigation.md |
Tab/Stack/Drawer, deep linking |
Navigation structure |
| mobile-typography.md |
System fonts, Dynamic Type, a11y |
Type decisions |
| mobile-color-system.md |
OLED, dark mode, battery-aware |
Color/theme decisions |
| decision-trees.md |
Framework/state/storage selection |
Architecture choices |
Platform-specific (read based on target)
| Platform |
File |
Content |
When to Read |
| iOS |
platform-ios.md |
Human Interface Guidelines, SF Pro, SwiftUI patterns |
Building for iPhone/iPad |
| Android |
platform-android.md |
Material Design 3, Roboto, Compose patterns |
Building for Android |
| Cross-Platform |
Both above |
Platform divergence points |
React Native / Flutter — apply conditional platform logic |
Ask Before Assuming
If the request is open-ended, ask rather than defaulting to favorite tools — these choices shape everything downstream.
Ask if not specified
| Aspect |
Ask |
Why |
| Platform |
"iOS, Android, or both?" |
Affects every design decision |
| Framework |
"React Native, Flutter, or native?" |
Determines patterns and tools |
| Navigation |
"Tab bar, drawer, or stack-based?" |
Core UX decision |
| State |
"What state management? (Zustand/Redux/Riverpod/BLoC?)" |
Architecture foundation |
| Offline |
"Does this need to work offline?" |
Affects data strategy |
| Target devices |
"Phone only, or tablet support?" |
Layout complexity |
AI mobile anti-patterns
These are common AI default tendencies; avoid them.
Performance Sins
| ❌ Avoid |
Why It's Wrong |
✅ Do Instead |
| ScrollView for long lists |
Renders all items, memory explodes |
Use FlatList / FlashList / ListView.builder |
| Inline renderItem function |
New function every render, all items re-render |
useCallback + React.memo |
| Missing keyExtractor |
Index-based keys cause bugs on reorder |
Unique, stable ID from data |
| Skip getItemLayout |
Async layout = janky scroll |
Provide when items have fixed height |
| setState() everywhere |
Unnecessary widget rebuilds |
Targeted state, const constructors |
| Native driver: false |
Animations blocked by JS thread |
useNativeDriver: true always |
| console.log in production |
Blocks JS thread severely |
Remove before release build |
| Skip React.memo/const |
Every item re-renders on any change |
Always memoize list items |
Touch/UX Sins
| ❌ Avoid |
Why It's Wrong |
✅ Do Instead |
| Touch target < 44px |
Impossible to tap accurately, frustrating |
Minimum 44pt (iOS) / 48dp (Android) |
| Spacing < 8px between targets |
Accidental taps on neighbors |
Minimum 8-12px gap |
| Gesture-only interactions |
Motor impaired users excluded |
Always provide button alternative |
| No loading state |
User thinks app crashed |
Always show loading feedback |
| No error state |
User stuck, no recovery path |
Show error with retry option |
| No offline handling |
Crash/block when network lost |
Graceful degradation, cached data |
| Ignore platform conventions |
Users confused, muscle memory broken |
iOS feels iOS, Android feels Android |
Security Sins
| ❌ Avoid |
Why It's Wrong |
✅ Do Instead |
| Token in AsyncStorage |
Easily accessible, stolen on rooted device |
SecureStore / Keychain / EncryptedSharedPreferences |
| Hardcode API keys |
Reverse engineered from APK/IPA |
Environment variables, secure storage |
| Skip SSL pinning |
MITM attacks possible |
Pin certificates in production |
| Log sensitive data |
Logs can be extracted |
Never log tokens, passwords, PII |
Architecture Sins
| ❌ Avoid |
Why It's Wrong |
✅ Do Instead |
| Business logic in UI |
Untestable, unmaintainable |
Service layer separation |
| Global state for everything |
Unnecessary re-renders, complexity |
Local state default, lift when needed |
| Deep linking as afterthought |
Notifications, shares broken |
Plan deep links from day one |
| Skip dispose/cleanup |
Memory leaks, zombie listeners |
Clean up subscriptions, timers |
📱 Platform Decision Matrix
When to Unify vs Diverge
UNIFY (same on both) DIVERGE (platform-specific)
─────────────────── ──────────────────────────
Business Logic ✅ Always -
Data Layer ✅ Always -
Core Features ✅ Always -
Navigation - ✅ iOS: edge swipe, Android: back button
Gestures - ✅ Platform-native feel
Icons - ✅ SF Symbols vs Material Icons
Date Pickers - ✅ Native pickers feel right
Modals/Sheets - ✅ iOS: bottom sheet vs Android: dialog
Typography - ✅ SF Pro vs Roboto (or custom)
Error Dialogs - ✅ Platform conventions for alerts
Quick Reference: Platform Defaults
| Element |
iOS |
Android |
| Primary Font |
SF Pro / SF Compact |
Roboto |
| Min Touch Target |
44pt × 44pt |
48dp × 48dp |
| Back Navigation |
Edge swipe left |
System back button/gesture |
| Bottom Tab Icons |
SF Symbols |
Material Symbols |
| Action Sheet |
UIActionSheet from bottom |
Bottom Sheet / Dialog |
| Progress |
Spinner |
Linear progress (Material) |
| Pull to Refresh |
Native UIRefreshControl |
SwipeRefreshLayout |
🧠 Mobile UX Psychology (Quick Reference)
Fitts' Law for Touch
Desktop: Cursor is precise (1px)
Mobile: Finger is imprecise (~7mm contact area)
→ Touch targets need 44-48px minimum
→ Important actions in the thumb zone (bottom of screen)
→ Destructive actions away from easy reach
Thumb Zone (One-Handed Usage)
┌─────────────────────────────┐
│ HARD TO REACH │ ← Navigation, menu, back
│ (stretch) │
├─────────────────────────────┤
│ OK TO REACH │ ← Secondary actions
│ (natural) │
├─────────────────────────────┤
│ EASY TO REACH │ ← Primary CTAs, tab bar
│ (thumb's natural arc) │ ← Main content interaction
└─────────────────────────────┘
[ HOME ]
Mobile-Specific Cognitive Load
| Desktop |
Mobile Difference |
| Multiple windows |
One task at a time |
| Keyboard shortcuts |
Touch gestures |
| Hover states |
No hover (tap or nothing) |
| Large viewport |
Limited space, scroll vertical |
| Stable attention |
Interrupted constantly |
For deep dive: touch-psychology.md
⚡ Performance Principles (Quick Reference)
React Native Core Rules
// ✅ CORRECT: Memoized renderItem + React.memo wrapper
const ListItem = React.memo(({ item }: { item: Item }) => (
<View style={styles.item}>
<Text>{item.title}</Text>
</View>
));
const renderItem = useCallback(
({ item }: { item: Item }) => <ListItem item={item} />,
[]
);
// ✅ CORRECT: FlatList with all optimizations
<FlatList
data={items}
renderItem={renderItem}
keyExtractor={(item) => item.id} // Stable ID, not index
getItemLayout={(data, index) => ({
length: ITEM_HEIGHT,
offset: ITEM_HEIGHT * index,
index,
})}
removeClippedSubviews={true}
maxToRenderPerBatch={10}
windowSize={5}
/>
Flutter Core Rules
// ✅ CORRECT: const constructors prevent rebuilds
class MyWidget extends StatelessWidget {
const MyWidget({super.key}); // const constructor
@override
Widget build(BuildContext context) {
return const Column( // const subtree
children: [
Text('Static content'),
MyConstantWidget(),
],
);
}
}
// ✅ CORRECT: Targeted state with ValueListenableBuilder
ValueListenableBuilder<int>(
valueListenable: counter,
builder: (context, value, child) => Text('$value'),
child: const ExpensiveWidget(), // Won't rebuild!
)
Animation Performance
GPU-accelerated (fast): CPU-bound (slow):
├── transform ├── width, height
├── opacity ├── top, left, right, bottom
└── (prefer these) ├── margin, padding
└── (avoid animating these)
For complete guide: mobile-performance.md
Checkpoint (before mobile work)
Fill this in (in your thinking or as a short note) before writing mobile code. If you can't fill it, read the relevant reference files first.
🧠 CHECKPOINT:
Platform: [ iOS / Android / Both ]
Framework: [ React Native / Flutter / SwiftUI / Kotlin ]
Files Read: [ List the skill files you've read ]
3 Principles I Will Apply:
1. _______________
2. _______________
3. _______________
Anti-Patterns I Will Avoid:
1. _______________
2. _______________
Example:
🧠 CHECKPOINT:
Platform: iOS + Android (Cross-platform)
Framework: React Native + Expo
Files Read: touch-psychology.md, mobile-performance.md, platform-ios.md, platform-android.md
3 Principles I Will Apply:
1. FlatList with React.memo + useCallback for all lists
2. 48px touch targets, thumb zone for primary CTAs
3. Platform-specific navigation (edge swipe iOS, back button Android)
Anti-Patterns I Will Avoid:
1. ScrollView for lists → FlatList
2. Inline renderItem → Memoized
3. AsyncStorage for tokens → SecureStore
🔧 Framework Decision Tree
WHAT ARE YOU BUILDING?
│
├── Need OTA updates + rapid iteration + web team
│ └── ✅ React Native + Expo
│
├── Need pixel-perfect custom UI + performance critical
│ └── ✅ Flutter
│
├── Deep native features + single platform focus
│ ├── iOS only → SwiftUI
│ └── Android only → Kotlin + Jetpack Compose
│
├── Existing RN codebase + new features
│ └── ✅ React Native (bare workflow)
│
└── Enterprise + existing Flutter codebase
└── ✅ Flutter
For complete decision trees: decision-trees.md
📋 Pre-Development Checklist
Before Starting a Mobile Project
Before Every Screen
Before Release
📚 Reference Files
For deeper guidance on specific areas:
| File |
When to Use |
| mobile-design-thinking.md |
First: anti-memorization, context-based thinking |
| touch-psychology.md |
Understanding touch interaction, Fitts' Law, gesture design |
| mobile-performance.md |
Optimizing RN/Flutter, 60fps, memory/battery |
| platform-ios.md |
iOS-specific design, HIG compliance |
| platform-android.md |
Android-specific design, Material Design 3 |
| mobile-navigation.md |
Navigation patterns, deep linking |
| mobile-typography.md |
Type scale, system fonts, accessibility |
| mobile-color-system.md |
OLED optimization, dark mode, battery |
| decision-trees.md |
Framework, state, storage decisions |
| mobile-backend.md |
Push, offline sync, mobile API |
| mobile-testing.md |
Testing pyramid, E2E |
| mobile-debugging.md |
Native vs JS debugging |
Remember: Mobile users are impatient, interrupted, and using imprecise fingers on small screens. Design for the worst conditions: bad network, one hand, bright sun, low battery. If it works there, it works everywhere.
1---2name: mobile-design3description: "Mobile UX for iOS and Android: touch targets, lists, offline, navigation, platform conventions. Use when building or reviewing React Native, Expo, Flutter, SwiftUI or Kotlin screens."4allowed-tools: Read Glob Grep Bash5compatibility: "Claude Code with the Cardume plugins (uses cardume-* commands, subagents or plugin paths); the guidance itself is portable."6metadata:7 source: https://skillmd.com/skills/jeffersonvalente/mobile-design8---910# Mobile Design System1112> **Philosophy:** Touch-first. Battery-conscious. Platform-respectful. Offline-capable.13> **Core Principle:** Mobile is not a small desktop. Think in mobile constraints; ask about platform choice.1415---1617## Audit Script1819Run this for validation (no need to read the source):2021| Command | Purpose | Usage |22|---------|---------|-------|23| `cardume-mobile-audit` | Mobile UX & touch audit | `cardume-mobile-audit <project_path>` |2425---2627## Reference Files: Read What the Task Needs2829Before writing code, read the reference files relevant to the task. Start with `mobile-design-thinking.md` for any new screen or app — it counters memorized defaults by forcing context-based decisions.3031### Core3233| File | Content | When to Read |34|------|---------|--------------|35| [mobile-design-thinking.md](mobile-design-thinking.md) | Anti-memorization: context-based thinking instead of AI defaults | First, for new screens/apps |36| [touch-psychology.md](touch-psychology.md) | Fitts' Law, gestures, haptics, thumb zone | Any interactive UI |37| [mobile-performance.md](mobile-performance.md) | RN/Flutter performance, 60fps, memory | Lists, animations, perf work |38| [mobile-backend.md](mobile-backend.md) | Push notifications, offline sync, mobile API | Data layer, sync, notifications |39| [mobile-testing.md](mobile-testing.md) | Testing pyramid, E2E, platform-specific | Writing or planning tests |40| [mobile-debugging.md](mobile-debugging.md) | Native vs JS debugging, React Native DevTools, Logcat | Investigating bugs/crashes |41| [mobile-navigation.md](mobile-navigation.md) | Tab/Stack/Drawer, deep linking | Navigation structure |42| [mobile-typography.md](mobile-typography.md) | System fonts, Dynamic Type, a11y | Type decisions |43| [mobile-color-system.md](mobile-color-system.md) | OLED, dark mode, battery-aware | Color/theme decisions |44| [decision-trees.md](decision-trees.md) | Framework/state/storage selection | Architecture choices |4546### Platform-specific (read based on target)4748| Platform | File | Content | When to Read |49|----------|------|---------|--------------|50| **iOS** | [platform-ios.md](platform-ios.md) | Human Interface Guidelines, SF Pro, SwiftUI patterns | Building for iPhone/iPad |51| **Android** | [platform-android.md](platform-android.md) | Material Design 3, Roboto, Compose patterns | Building for Android |52| **Cross-Platform** | Both above | Platform divergence points | React Native / Flutter — apply conditional platform logic |5354---5556## Ask Before Assuming5758If the request is open-ended, ask rather than defaulting to favorite tools — these choices shape everything downstream.5960### Ask if not specified6162| Aspect | Ask | Why |63|--------|-----|-----|64| **Platform** | "iOS, Android, or both?" | Affects every design decision |65| **Framework** | "React Native, Flutter, or native?" | Determines patterns and tools |66| **Navigation** | "Tab bar, drawer, or stack-based?" | Core UX decision |67| **State** | "What state management? (Zustand/Redux/Riverpod/BLoC?)" | Architecture foundation |68| **Offline** | "Does this need to work offline?" | Affects data strategy |69| **Target devices** | "Phone only, or tablet support?" | Layout complexity |7071### AI mobile anti-patterns7273These are common AI default tendencies; avoid them.7475#### Performance Sins7677| ❌ Avoid | Why It's Wrong | ✅ Do Instead |78|-------------|----------------|--------------|79| **ScrollView for long lists** | Renders all items, memory explodes | Use `FlatList` / `FlashList` / `ListView.builder` |80| **Inline renderItem function** | New function every render, all items re-render | `useCallback` + `React.memo` |81| **Missing keyExtractor** | Index-based keys cause bugs on reorder | Unique, stable ID from data |82| **Skip getItemLayout** | Async layout = janky scroll | Provide when items have fixed height |83| **setState() everywhere** | Unnecessary widget rebuilds | Targeted state, `const` constructors |84| **Native driver: false** | Animations blocked by JS thread | `useNativeDriver: true` always |85| **console.log in production** | Blocks JS thread severely | Remove before release build |86| **Skip React.memo/const** | Every item re-renders on any change | Always memoize list items |8788#### Touch/UX Sins8990| ❌ Avoid | Why It's Wrong | ✅ Do Instead |91|-------------|----------------|--------------|92| **Touch target < 44px** | Impossible to tap accurately, frustrating | Minimum 44pt (iOS) / 48dp (Android) |93| **Spacing < 8px between targets** | Accidental taps on neighbors | Minimum 8-12px gap |94| **Gesture-only interactions** | Motor impaired users excluded | Always provide button alternative |95| **No loading state** | User thinks app crashed | Always show loading feedback |96| **No error state** | User stuck, no recovery path | Show error with retry option |97| **No offline handling** | Crash/block when network lost | Graceful degradation, cached data |98| **Ignore platform conventions** | Users confused, muscle memory broken | iOS feels iOS, Android feels Android |99100#### Security Sins101102| ❌ Avoid | Why It's Wrong | ✅ Do Instead |103|-------------|----------------|--------------|104| **Token in AsyncStorage** | Easily accessible, stolen on rooted device | `SecureStore` / `Keychain` / `EncryptedSharedPreferences` |105| **Hardcode API keys** | Reverse engineered from APK/IPA | Environment variables, secure storage |106| **Skip SSL pinning** | MITM attacks possible | Pin certificates in production |107| **Log sensitive data** | Logs can be extracted | Never log tokens, passwords, PII |108109#### Architecture Sins110111| ❌ Avoid | Why It's Wrong | ✅ Do Instead |112|-------------|----------------|--------------|113| **Business logic in UI** | Untestable, unmaintainable | Service layer separation |114| **Global state for everything** | Unnecessary re-renders, complexity | Local state default, lift when needed |115| **Deep linking as afterthought** | Notifications, shares broken | Plan deep links from day one |116| **Skip dispose/cleanup** | Memory leaks, zombie listeners | Clean up subscriptions, timers |117118---119120## 📱 Platform Decision Matrix121122### When to Unify vs Diverge123124```125 UNIFY (same on both) DIVERGE (platform-specific)126 ─────────────────── ──────────────────────────127Business Logic ✅ Always -128Data Layer ✅ Always -129Core Features ✅ Always -130 131Navigation - ✅ iOS: edge swipe, Android: back button132Gestures - ✅ Platform-native feel133Icons - ✅ SF Symbols vs Material Icons134Date Pickers - ✅ Native pickers feel right135Modals/Sheets - ✅ iOS: bottom sheet vs Android: dialog136Typography - ✅ SF Pro vs Roboto (or custom)137Error Dialogs - ✅ Platform conventions for alerts138```139140### Quick Reference: Platform Defaults141142| Element | iOS | Android |143|---------|-----|---------|144| **Primary Font** | SF Pro / SF Compact | Roboto |145| **Min Touch Target** | 44pt × 44pt | 48dp × 48dp |146| **Back Navigation** | Edge swipe left | System back button/gesture |147| **Bottom Tab Icons** | SF Symbols | Material Symbols |148| **Action Sheet** | UIActionSheet from bottom | Bottom Sheet / Dialog |149| **Progress** | Spinner | Linear progress (Material) |150| **Pull to Refresh** | Native UIRefreshControl | SwipeRefreshLayout |151152---153154## 🧠 Mobile UX Psychology (Quick Reference)155156### Fitts' Law for Touch157158```159Desktop: Cursor is precise (1px)160Mobile: Finger is imprecise (~7mm contact area)161162→ Touch targets need 44-48px minimum163→ Important actions in the thumb zone (bottom of screen)164→ Destructive actions away from easy reach165```166167### Thumb Zone (One-Handed Usage)168169```170┌─────────────────────────────┐171│ HARD TO REACH │ ← Navigation, menu, back172│ (stretch) │173├─────────────────────────────┤174│ OK TO REACH │ ← Secondary actions175│ (natural) │176├─────────────────────────────┤177│ EASY TO REACH │ ← Primary CTAs, tab bar178│ (thumb's natural arc) │ ← Main content interaction179└─────────────────────────────┘180 [ HOME ]181```182183### Mobile-Specific Cognitive Load184185| Desktop | Mobile Difference |186|---------|-------------------|187| Multiple windows | One task at a time |188| Keyboard shortcuts | Touch gestures |189| Hover states | No hover (tap or nothing) |190| Large viewport | Limited space, scroll vertical |191| Stable attention | Interrupted constantly |192193For deep dive: [touch-psychology.md](touch-psychology.md)194195---196197## ⚡ Performance Principles (Quick Reference)198199### React Native Core Rules200201```typescript202// ✅ CORRECT: Memoized renderItem + React.memo wrapper203const ListItem = React.memo(({ item }: { item: Item }) => (204 <View style={styles.item}>205 <Text>{item.title}</Text>206 </View>207));208209const renderItem = useCallback(210 ({ item }: { item: Item }) => <ListItem item={item} />,211 []212);213214// ✅ CORRECT: FlatList with all optimizations215<FlatList216 data={items}217 renderItem={renderItem}218 keyExtractor={(item) => item.id} // Stable ID, not index219 getItemLayout={(data, index) => ({220 length: ITEM_HEIGHT,221 offset: ITEM_HEIGHT * index,222 index,223 })}224 removeClippedSubviews={true}225 maxToRenderPerBatch={10}226 windowSize={5}227/>228```229230### Flutter Core Rules231232```dart233// ✅ CORRECT: const constructors prevent rebuilds234class MyWidget extends StatelessWidget {235 const MyWidget({super.key}); // const constructor236237 @override238 Widget build(BuildContext context) {239 return const Column( // const subtree240 children: [241 Text('Static content'),242 MyConstantWidget(),243 ],244 );245 }246}247248// ✅ CORRECT: Targeted state with ValueListenableBuilder249ValueListenableBuilder<int>(250 valueListenable: counter,251 builder: (context, value, child) => Text('$value'),252 child: const ExpensiveWidget(), // Won't rebuild!253)254```255256### Animation Performance257258```259GPU-accelerated (fast): CPU-bound (slow):260├── transform ├── width, height261├── opacity ├── top, left, right, bottom262└── (prefer these) ├── margin, padding263 └── (avoid animating these)264```265266For complete guide: [mobile-performance.md](mobile-performance.md)267268---269270## Checkpoint (before mobile work)271272Fill this in (in your thinking or as a short note) before writing mobile code. If you can't fill it, read the relevant reference files first.273274```275🧠 CHECKPOINT:276277Platform: [ iOS / Android / Both ]278Framework: [ React Native / Flutter / SwiftUI / Kotlin ]279Files Read: [ List the skill files you've read ]2802813 Principles I Will Apply:2821. _______________2832. _______________2843. _______________285286Anti-Patterns I Will Avoid:2871. _______________2882. _______________289```290291**Example:**292```293🧠 CHECKPOINT:294295Platform: iOS + Android (Cross-platform)296Framework: React Native + Expo297Files Read: touch-psychology.md, mobile-performance.md, platform-ios.md, platform-android.md2982993 Principles I Will Apply:3001. FlatList with React.memo + useCallback for all lists3012. 48px touch targets, thumb zone for primary CTAs3023. Platform-specific navigation (edge swipe iOS, back button Android)303304Anti-Patterns I Will Avoid:3051. ScrollView for lists → FlatList3062. Inline renderItem → Memoized3073. AsyncStorage for tokens → SecureStore308```309310---311312## 🔧 Framework Decision Tree313314```315WHAT ARE YOU BUILDING?316 │317 ├── Need OTA updates + rapid iteration + web team318 │ └── ✅ React Native + Expo319 │320 ├── Need pixel-perfect custom UI + performance critical321 │ └── ✅ Flutter322 │323 ├── Deep native features + single platform focus324 │ ├── iOS only → SwiftUI325 │ └── Android only → Kotlin + Jetpack Compose326 │327 ├── Existing RN codebase + new features328 │ └── ✅ React Native (bare workflow)329 │330 └── Enterprise + existing Flutter codebase331 └── ✅ Flutter332```333334For complete decision trees: [decision-trees.md](decision-trees.md)335336---337338## 📋 Pre-Development Checklist339340### Before Starting a Mobile Project341342- [ ] **Platform confirmed?** (iOS / Android / Both)343- [ ] **Framework chosen?** (RN / Flutter / Native)344- [ ] **Navigation pattern decided?** (Tabs / Stack / Drawer)345- [ ] **State management selected?** (Zustand / Redux / Riverpod / BLoC)346- [ ] **Offline requirements known?**347- [ ] **Deep linking planned from day one?**348- [ ] **Target devices defined?** (Phone / Tablet / Both)349350### Before Every Screen351352- [ ] **Touch targets ≥ 44-48px?**353- [ ] **Primary CTA in thumb zone?**354- [ ] **Loading state exists?**355- [ ] **Error state with retry exists?**356- [ ] **Offline handling considered?**357- [ ] **Platform conventions followed?**358359### Before Release360361- [ ] **console.log removed?**362- [ ] **SecureStore for sensitive data?**363- [ ] **SSL pinning enabled?**364- [ ] **Lists optimized (memo, keyExtractor)?**365- [ ] **Memory cleanup on unmount?**366- [ ] **Tested on low-end devices?**367- [ ] **Accessibility labels on all interactive elements?**368369---370371## 📚 Reference Files372373For deeper guidance on specific areas:374375| File | When to Use |376|------|-------------|377| [mobile-design-thinking.md](mobile-design-thinking.md) | First: anti-memorization, context-based thinking |378| [touch-psychology.md](touch-psychology.md) | Understanding touch interaction, Fitts' Law, gesture design |379| [mobile-performance.md](mobile-performance.md) | Optimizing RN/Flutter, 60fps, memory/battery |380| [platform-ios.md](platform-ios.md) | iOS-specific design, HIG compliance |381| [platform-android.md](platform-android.md) | Android-specific design, Material Design 3 |382| [mobile-navigation.md](mobile-navigation.md) | Navigation patterns, deep linking |383| [mobile-typography.md](mobile-typography.md) | Type scale, system fonts, accessibility |384| [mobile-color-system.md](mobile-color-system.md) | OLED optimization, dark mode, battery |385| [decision-trees.md](decision-trees.md) | Framework, state, storage decisions |386| [mobile-backend.md](mobile-backend.md) | Push, offline sync, mobile API |387| [mobile-testing.md](mobile-testing.md) | Testing pyramid, E2E |388| [mobile-debugging.md](mobile-debugging.md) | Native vs JS debugging |389390---391392> **Remember:** Mobile users are impatient, interrupted, and using imprecise fingers on small screens. Design for the worst conditions: bad network, one hand, bright sun, low battery. If it works there, it works everywhere.