A body-shape virtual-fitting app combining Unity and Flutter. The original team had left; we recovered the AWS outage, automated 3D-model uploads, and lifted app performance — picking up where the previous build stopped.
After the original team left, the app sat dark and nobody knew how to turn it back on.
An AWS server outage had taken the service down. To add new 3D garment models a developer had to run INSERTs directly on the database. The Unity build was heavy, the app crashed often, and every new user made the operating load worse.
No maintenance manual. No code comments. If we didn't pick it up, the service was finished.
Start with recovery, change the structure so operations can grow content without code, and document everything so the next team can take over cleanly.
We traced the AWS outage to root cause, rebuilt the infrastructure, and re-laid the database recovery, backup and monitoring rails. New 3D garment models no longer need a developer — operators upload through the admin and the pipeline auto-optimizes and registers them.
We redesigned the Unity–Flutter communication layer to cut load time and memory use, then refactored, documented, wrote the maintenance manual and set up CI/CD — leaving the project in a state the next team can inherit.
Reworked the Flutter-hosting-Unity-view bridge to reduce load time and memory pressure.
Post-recovery monitoring, backup and automated deploys put in order.
Admin panel and 3D-model registration automation on Spring Boot.
Kept the existing data shape while rebuilding backup, recovery and monitoring.