Move a feature and retire its old API carefully

A lounge-benefit feature was spread across Android modules, while a separate backend endpoint needed to be retired. These were two tasks in the same membership migration programme, with distinct implementation and release responsibilities.

I documented module dependencies, reviewed the feature structure and proposed extracting the lounge feature into the existing Membership module. I contributed part of the code change in a mixed Kotlin, Java and Jetpack Compose codebase.

The main app team completed the work collaboratively. I handled dependency analysis, documentation and part of the extraction, then handed over before moving into the technical-enablement role.

For the separate backend task, I checked the recorded old-version user state, removed or disabled the endpoint and related logic, and updated OpenAPI, Insomnia cases and unit tests. I also performed staging verification.

The Product Owner decided timing and approved retirement; the Mobile Tech Lead and I confirmed technical safety. The platform team performed the production release of the endpoint retirement through an inactive environment, validation, traffic switching and a temporary rollback window.

The Android extraction was completed collaboratively and handed over; its production release is not confirmed in the record. My backend contract, test and staging changes supported the endpoint retirement, which the platform team released to production. Both tasks preceded the later mobile-booking project.