A software development company in Detroit needed delivery capacity for two custom cloud-based mobile apps, both targeting iOS and Android. One of the two came with the problem that forces the refactor vs rewrite decision: an existing Flutter app, a mental health platform with video sessions and billing management, was unstable and not production-ready. Rebuilding it from zero would have meant discarding working surfaces and restarting the clock. Refactoring meant taking over another team's codebase and making it shippable as-is.

The client chose the takeover. That made this an app rescue with a hard constraint: the platform had to reach production and keep evolving while the code underneath it was being repaired.

Shipverra ran both builds from the client's documentation: one app in Flutter, the other in React Native. For one project Shipverra owned development only; for the other it owned both the UI/UX design and the development. A single project's team ran to five mid-level developers, a senior developer, an architect, and a UX designer working as needed, coordinated by a technical product manager, the structure of a dedicated development team. It is the same embedded model that runs the industrial IoT analytics engagement at Greyhound Engineering. The team worked AI-augmented throughout, and that is the fact the rest of this case rests on: it is what let a team this size carry two apps and a rescue at the same time.

Stabilize first, then refactor what you touch

The rescue followed the sequence that separates a refactor from a rewrite. Stabilization came first and took a couple of months: the Flutter app went from unstable and not production-ready to shippable. AI-assisted code comprehension shortened the hardest part of any takeover, understanding another team's decisions before changing them. From there the refactor ran progressively in production. As features evolved and surfaces were touched, the code under those surfaces was repaired in the same pass, so the platform never stopped shipping to get better. The stack ran mainly on GCP and Firebase.

The second app, built in React Native, ran in parallel with the same coordination model. One team delivering one app in each framework, at the same time, for the same client, with AI-assisted QA holding coverage across both while the refactor changed code underneath.

The app that was once unstable became a stable, solid product the client says they are happy to showcase, live in production. The client's Clutch review scores 5.0 across every category and names quality and honesty as the two takeaways of the engagement: deadlines met, promises kept, and an airtight process producing quality code. The client's shout-out goes to the technical product manager coordinating the work.

The engagement began in October 2023 and continues. What makes this mobile app development case study unusual is who did the judging: the client is itself a software development company, a buyer that reads code, and it is the one vouching for the honesty and the quality. The same takeover discipline carried the Notary.io software project rescue on the web side. Per the confidentiality terms of the engagement, the client is identified only as a software development company.