Skip to content
WaveFluxon
Display mode

Mobile App Development

Kotlin Multiplatform Mobile Lab

Shared domain models and networking between Android and iOS with a realistic module map you can explain in portfolio reviews.

Lead visual describing Kotlin Multiplatform Mobile Lab
This cohort follows a build-measure-iterate loop: you architect a small banking-style demo app, isolate shared logic in Kotlin Multiplatform modules, and publish divergent UI shells on each platform. Weekend labs emphasize Gradle ergonomics, expect/actual seams, and CI sketches so teammates see where contracts land.

Module inclusions

  • Expect/actual boundaries with lint-friendly folder conventions
  • Network caching experiments measured with structured traces
  • Screenshot-guided mentor passes focused on merge readiness
  • Pair rotations mirroring distributed squad habits
  • Optional instrumentation hooks for crash breadcrumbs
  • Playbook for shrinking artifacts before App Store submission

Outcomes we assess

  1. Ship a two-platform repo where reviewers can trace domain flows.
  2. Document integration seams clearly enough for a hiring loop.
  3. Prepare smoke checklist references tailored to your cohort build.

Cohort FAQ

We operate lab benches on campus for pairing sessions; remote participants receive detailed minimum specs and emulator profiles.

Mentor-attributed notes

“The Gradle troubleshooting sprint was oddly calming—Mira walked through why task graphs stalled during shared networking merges.”
— Junseo · QA-turned-mobile · Regional logistics app · survey
“Mentor passes flagged ambiguous domain naming early; I reworked module folders before capstone review.”
— Client in finance tooling

Next step

Reference this syllabus with advisors—share blockers, employer deadlines, and desired mentor cadence.

Open contact desk