Every earlier lesson in this course taught one skill in isolation — navigation, offline caching, certificate pinning, RTL layout — the way a training session isolates one skill to build it properly. A capstone is the actual match: nothing here is new content, and everything here is graded on whether the pieces work together under the same constraints a real release actually has, not on whether you can demonstrate each skill separately once more.
This capstone is deliberately scoped as a small, real, production-shaped app — not a toy, not a UI-only prototype — called MatchDay Live: a companion app for following live cricket scores, saving favorite teams, and getting notified of key match moments, built offline-first, secured, internationalized, and shipped through an actual release pipeline. The domain is intentionally familiar so the engineering decisions, not the product idea, are what's actually being tested.
Each of the four stages below ships as its own reviewable deliverable with explicit, checkable acceptance criteria — not vibes, not 'looks good to me.' A stage that technically runs but silently fails its stated criteria is not complete, the same way a feature that works only when nothing goes wrong is not actually production-ready. Treat the acceptance criteria as the actual spec; everything else in this lesson is guidance toward meeting it.
Analogy🏏Cricket
🏏 Think of it like cricket: A batter can look completely correct in the nets against a bowling machine set to a fixed, predictable length and pace, and still fail completely in an actual match, because a match tests something nets sessions deliberately isolate away from — reading a bowler's changing field, adjusting to a pitch that's deteriorating over a session, managing the scoreboard pressure of a run chase, all happening at once, under real consequences. The nets session where a batter drills the cover drive against a fixed length is genuinely valuable — it's where the technique gets built — but a coach who only ever evaluates a batter in the nets, and never in the messier, integrated conditions of a real innings, is measuring a different thing than what the team actually needs. This capstone is the real innings, not another net session: the individual skills — navigation, offline sync, secure storage, RTL layout, a CI pipeline — were each drilled in isolation across the earlier lessons, the same way a cover drive gets drilled against a fixed length. Shipping MatchDay Live end to end, meeting every stage's acceptance criteria under the same constraints a real release imposes, is what actually tests whether those isolated skills combine into something that survives contact with reality. The insight is that competence at an isolated skill and competence at the integrated whole are genuinely different things, and only one of them is what a real production release actually demands.
🏏 Showing the Cricket analogy — a Cricket version isn’t available for this concept yet.