Track · ~6 months · 35 nodes

Mobile.

React Native or Flutter, native APIs, store deployment.

Start the path →See full graph →

Foundations

How mobile apps work and the React Native toolchain.

  1. How mobile apps workNative vs cross-platform, the app lifecycle, and the stores.
  2. JS & TypeScript for RNThe language baseline React Native development assumes.
  3. React Native fundamentalsComponents, JSX, props, and state on mobile.
  4. Expo & toolingThe fastest way to build, run, and ship RN apps.

UI & layout

Building screens with core components and flexbox.

  1. Core componentsView, Text, Image, ScrollView — the building blocks.
  2. Flexbox in RNLayout on mobile, where flexbox is the only game.
  3. Styling & themesStyleSheet, design tokens, dark mode, and consistency.
  4. Lists & performanceFlatList, virtualization, and smooth scrolling.
  5. Responsive & safe areasNotches, dimensions, and many screen sizes.

Navigation & state

Moving between screens and managing app state.

  1. React NavigationStacks, tabs, and drawers — the standard nav library.
  2. Navigation patternsParams, nested navigators, and auth flows.
  3. State managementLocal state, context, and when to reach for a store.
  4. Data fetchingTalking to APIs, caching, and loading states with TanStack Query.

Native capabilities

Reaching the device: modules, permissions, camera, maps.

  1. Native modulesBridging to native code when JS is not enough.
  2. Platform APIsPlatform differences and writing iOS/Android-aware code.
  3. PermissionsRequesting and handling device permissions gracefully.
  4. Camera & mediaPhotos, video, and the media library on device.
  5. Maps & locationGPS, map views, and location-aware features.

Polish

Animations, gestures, notifications, and deep links.

  1. AnimationsReanimated and 60fps motion that feels native.
  2. GesturesSwipes, drags, and the gesture handler.
  3. Push notificationsRemote and local notifications, tokens, and delivery.
  4. Deep linksOpening the right screen from a URL or notification.

Data & offline

Storage, offline-first, and keeping data in sync.

  1. Local storageAsyncStorage, MMKV, and on-device databases.
  2. Offline-firstDesigning apps that work without a connection.
  3. Secure storageKeychain, Keystore, and storing tokens safely.
  4. Sync & conflictReconciling local and server data without losing changes.

Ship

Store submission, device testing, and performance.

  1. Icons & splash screensThe first impression: icons, splash, and store assets.
  2. Testing on devicesSimulators, real devices, and TestFlight/internal testing.
  3. Performance profilingFinding jank, slow renders, and memory issues.
  4. App store submissionBuilds, review, and getting onto the App Store and Play.
  5. Over-the-air updatesShipping JS updates without a full store review.

Beyond the basics

Native depth, system design, and the job hunt.

  1. Native iOS & Android basicsEnough Swift and Kotlin to debug the native layer.
  2. Working with AI toolsUsing AI assistants on RN code without shipping bugs.
  3. Mobile system designDesigning an app: offline, sync, and the API contract.
  4. Get hired (mobile)A published app, portfolio, resume, and interviews.

Outcomes

When you finish this track:

Schedule

~199 hours total.

At 8–10 hours a week, that’s about 6 months. Each stage has its own pace.

  1. Foundations4 nodes28–36h
  2. UI & layout5 nodes26–34h
  3. Navigation & state4 nodes25–33h
  4. Native capabilities5 nodes23–30h
  5. Polish4 nodes23–30h
  6. Data & offline4 nodes18–23h
  7. Ship5 nodes26–34h
  8. Beyond the basics4 nodes30–39h

Other tracks

Not what you wanted?

Frontend

HTML, CSS, JS, React, and the patterns real teams use.

Backend

APIs, databases, auth, and shipping production services.

DevOps

Linux, Docker, CI/CD, cloud, and the on-call mindset.

AI / ML

Python, math foundations, models, and shipping ML in production.

Full-Stack

Frontend + Backend depth, with the seams that connect them.