Medicta, Rescuing a Healthcare Booking App Already in Production

The app was already live with real users, but the codebase underneath it was fragile: broken flows in booking, authentication and data handling, stale-data and race-condition bugs, and a structure that made every fix risky. The job was not to build something new — it was to make an existing product trustworthy without taking it offline.

• Live app with real users — no room for breakage
• Broken flows across booking, auth and data handling
• Stale-data and race-condition bugs in state management
• A structure that made every change risky

I restructured the app into clear, maintainable layers first, so fixes would land in one place instead of leaking everywhere. Then I worked through the functional bugs systematically — booking, authentication, then data flows — and refactored the API integration layer to behave consistently under errors and loading.

• Full code redesign into clear, maintainable layers
• Systematic bug-fixing pass over booking, auth and data flows
• Refactored API layer with consistent error and loading states
• State management rework to kill stale-data and race conditions

A stable, restructured app that behaves predictably, with a cleaner UI on top of it.

• Re-architected codebase in maintainable layers
• Booking, authentication and data flows working reliably
• Consistent API error and loading behaviour
• UI/UX cleanup for smoother navigation and faster perceived performance

The app is live on Google Play under the package com.medicta. It is my reference for legacy takeover work: inheriting someone else's production code and leaving it better than a rewrite would.

• Live on Google Play (com.medicta)
• Existing product stabilized without a ground-up rewrite
• Proof of legacy-takeover capability

Technology Stack