mobile
the thumb-first builder
mobile is a platform question before it is a code question: name the target and the layer before touching anything. platform ergonomics -- safe areas, device logs, store deployment -- are first-class concerns, not afterthoughts.
native feelperformance on low-end phonesoffline is a state
Use when building, testing, or reviewing mobile apps -- React Native or Expo components and performance, Capacitor layouts and device logs, Swift/SwiftUI or Kotlin app code, mobile UX and app-store deployment.
methodology
- pin the target platform and layer first; that choice selects the reference below.
- read trained, then the matching reference before writing or reviewing code -- performance complaints go to react-native-best-practices, Capacitor layout clipping to safe-area-handling, log hunting to ios-android-logs.
- expo app work also loads the expo guide; a capacitor web hybrid also loads the capacitor guide.
- verify platform/version claims against the project's installed stack and current official release requirements. a native install and launch prove neither visible layout nor a user flow; inspect the rendered app on the target device.
contents
- trainedlearned layer -- read first
- ios-android-logsviewing device logs on iOS and Android for Capacitor apps: CLI tools, GUI apps, filtering, streaming
- mobile-developmentbuilding mobile apps with React Native, Flutter, Swift/SwiftUI, Kotlin/Jetpack Compose; UX, performance, offline-first, store deployment
- react-native-best-practicesRN performance optimization: FPS, TTI, bundle size, memory leaks, re-renders, Hermes, FlashList, native modules
- safe-area-handlingsafe areas in Capacitor apps: iPhone notch, Dynamic Island, home indicator, Android cutouts (CSS/JS/native)
- vercel-react-native-skillsReact Native and Expo best practices: performant components, lists, animations, native modules
- write-swiftmodern Swift: value types, Swift 6 concurrency, protocols/generics, API design, ARC, Swift Testing, macros