Chapter 1: How React Native Actually Works
- 1.1: What you should be able to do by the end
- 1.2: The core mental model of React Native
- 1.3: The rendering pipeline
- 1.4: Threading model
- 1.5: What actually happens when state changes
- 1.6: Platform differences
- 1.7: Failure modes introduced early
- 1.8: Why this mental model matters
- Next chapter preview
Chapter 2: Formal Architecture Model
- 2.1: By the end of this chapter
- 2.2: Why architecture matters in React Native
- 2.3: The four-layer architecture model
- 2.3.1: UI Layer
- 2.3.2: Domain Layer
- 2.3.3: Data Layer
- 2.3.4: Infrastructure Layer
- 2.4: Dependency rules
- 2.4.1: Dependency diagram
- 2.4.2: Why downward-only dependencies matter
- 2.5: A practical example
- 2.6: Evolution path for beginners
- 2.7: Common mistakes
- 2.8: Key takeaway
- Next chapter preview: Chapter 3: Feature Isolation and Boundaries
Chapter 3: Feature Isolation & Boundaries
- 3.1: Context from the previous chapter
- 3.2: By the end of this chapter
- 3.3: What feature isolation actually means
- 3.4: Feature boundary rules
- 3.5: Visual model of feature isolation
- 3.6: Cross feature communication strategies
- 3.7: Scaling implications
- 3.8: Common failure patterns
- 3.9: Practical enforcement rules
- 3.10: End of chapter summary
- 3.11: Next chapter preview
Chapter 4: Core Components with Performance Budgets
- 4.1: By the end of this chapter
- 4.2: Core component model in React Native
- 4.3: The core building blocks
- 4.4: The performance rule of UI construction
- 4.5: ScrollView vs FlatList decision model
- 4.6: Image rendering and hidden cost
- 4.7: Layout system and Flexbox in Yoga
- 4.8: Layout thrashing and re-render cost
- 4.9: Practical component hierarchy rule
- 4.10: Performance debugging mindset
- 4.11: Key mental model summary
- 4.12: Chapter preview
Chapter 5: Styling & Flexbox
- 5.1: By the end of this chapter
- 5.2: Mental model of styling in React Native
- 5.3: Flexbox as the primary layout system
- 5.4: The Flexbox mental model that actually works
- 5.5: Style architecture and StyleSheet discipline
- 5.6: Layout performance model
- 5.7: Platform differences in styling
- 5.8: Layout debugging strategy
- 5.9: Performance considerations in styling decisions
- 5.10: Key takeaway model
- 5.11: Chapter summary mental model
- 5.12: Next chapter preview
Chapter 6: Navigation
- 6.1: By the end of this chapter
- 6.2: Navigation as a state machine
- 6.3: Core navigation structures
- 6.4: Deep linking as controlled entry points
- 6.5: Navigation state persistence
- 6.6: Navigation and authentication coupling
- 6.7: Common failure modes
- 6.8: Practical mental model
- 6.9: Engineering rules
- 6.10: Summary
- Next chapter preview: Chapter 7 State Management – The Exact Rule
Chapter 7: State Management
- 7.1: Why state management needs rules, not opinions
- 7.2: The mental model of state in a mobile app
- 7.3: State taxonomy and strict tool selection
- 7.4: Decision framework for state placement
- 7.5: Re-render control and performance discipline
- 7.6: Common architecture mistakes
- 7.7: Feature boundary rule for state ownership
- 7.8: Mental model summary
- 7.9: Chapter recap
- Next chapter preview: Chapter 8: Forms and Input Handling
Chapter 9: Device Features
- 9.1: Introduction and mental model shift
- 9.2: The device interaction model
- 9.3: Core Expo device APIs
- 9.4: Permission strategy and timing
- 9.5: Performance considerations for device APIs
- 9.6: Architectural placement of device logic
- 9.7: Failure modes specific to device features
- 9.8: Summary of rules
- 9.9: Next chapter preview
Chapter 10: Projects
- 10.1: Purpose of this chapter
- 10.2: Project 1 Weather App (Beginner System)
- 10.3: Project 2 Todo App (Intermediate System)