/about/story

Built where shipping meets pedagogy

Turboexcel began as late-night code reviews for Brisbane product teams who kept missing store deadlines. We formalised the rituals—device matrices, reviewer packets, CI receipts—into cohort-sized labs so designers and engineers learn with the same artefacts they will use Monday morning.

We are not a bootcamp factory: cohorts stay small enough that mentors can cite your repo in critique. We also publish limitation notes upfront because mobile policies shift faster than any syllabus PDF.

// principles

Evidence over theatre

Show crash logs, diff stats, and reviewer threads—not slide decks with stock gradients.

Limitations on the same page as promises

If a module cannot cover legal or billing advice, we say so before enrolment, not in fine print buried later.

AU-first scheduling

Live blocks default to AEST/AEDT; field testing guidance references local carriers and transit conditions.

Fork-friendly kits

Starters intentionally include TODO markers so teams practice deletion as much as addition.

/timeline

Milestones

2019
Pilot mentor sprints

First mobile release labs run with two Brisbane product teams.
2022
Cross-platform track

Flutter and RN pathways added with shared architecture critiques.
2025
AU-focused compliance refresh

Store policy modules updated for current Apple and Google public guidance.