App Development
Lab Curriculum.

BUG FOUND: app learners who can build a demo screen, but cannot fix a crashing app.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. Flutter / React Native basics: widgets/components, layout, and navigation.
2. State management basics and why state bugs lose data.
3. API calls, loading states, and error handling on mobile.
4. Local storage and offline basics.
5. Debugging on emulator / device: logs, crash reports, and reproduction.
6. App structure: screens, services, and reusable components.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: Flutter / React Native toolchain, emulator, device logs, API mock / backend.

• BUG #1: App crashes on one screen — reproduce from a crash log, find the null / state cause, fix it.
• BUG #2: List scrolls slowly / freezes — find the rendering / data cause, optimise, show before/after performance.
• BUG #3: API failure leaves a blank screen — add loading, error, and retry states, test offline and slow-network cases.
• BUG #4: Form data lost on rotation / navigation — fix state persistence, verify across navigation paths.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Navigate an app codebase: state, navigation, and API layers; trace a bug across layers.
• Add a feature across multiple screens without regressions, with manual test cases.
• Refactor duplicated screen code into shared components safely.
• Review a peer's app change for crash risks, state bugs, and missing error states.

$ step-04 ship // weeks 8–9 — Shipping Features: capstone — an app build with a real feature, tested on emulator/device, with release notes and a demo video / walkthrough.

$ ship → PROOF — exact output: app build, release notes, a manual test report, and a demo walkthrough.

$ run --lab app-development → ✓ SHIPPED, job-ready

## // management-commerce-labs — Management & commerce labs