Pre-launch B2C mobile application, taken over after the collaboration with the original team ended. The public launch date was four weeks away.
Audit an existing Flutter and NestJS codebase, determine what could be stabilised within four weeks and what should move to a later release, then prepare a reliable production launch on the agreed date without a full rewrite.
Week 1: audit and technical-debt mapping across architecture, tests, security, builds and performance. Weeks 2 and 3: isolate the three critical journeys — authentication, payment and the core feature — then stabilise them with integration tests and Sentry monitoring. Retained debt on secondary journeys was documented in a README provided to the client. Week 4: deployment, continuous monitoring and handover.
Launch hit on the planned date. Application stable in production on critical paths. The client could take ownership of what came next with documented technical debt and a remediation plan.