Rebuilding an app when the source code is gone
No source code, no store bundle — only an installed app, a screen recording, some notes and a forty-minute meeting. We rebuilt it from scratch and applied every change the client had asked for, reaching a testable build in days rather than months.
“We have lost the code”
It is a more common problem than people admit, and a frightening one. A working prototype existed and was installed on phones. The source code and the store bundle were gone. The only surviving copy of the software was the installable file itself.
On top of that, the client had held a long meeting listing everything they wanted changed, and nobody had written it up properly. Their view of how the prototype looked was blunt: too dark, too neon, too much glow — the wrong feel entirely for the audience it was meant to serve.
Starting again with a conventional agency would have meant weeks of discovery before a single line of code.
What we had to work with
- The surviving installable app file
- A screen recording of the prototype being used
- A statement of work and a page of written notes
- A forty-minute audio recording of the client meeting
How we did it
- Read everything first. The meeting recording was transcribed and every single request in it was listed. The screen recording was watched screen by screen. The app file itself was unpacked to recover the screen text, the data structure and the connection details for the existing database — so the rebuilt app could keep using the data that was already there.
- Wrote a specification. Every item from the meeting became a row in a status table marked built, partly built or not started, kept current throughout, so the client could watch progress against their own words rather than against our summary of them.
- Rebuilt, then improved. The prototype's screens were recreated first, and only then were the meeting's changes applied on top.
- Asked rather than guessed. Decisions that belonged to the client — pricing tiers, build order, hosting — were put to them as short multiple-choice questions instead of being assumed.
- Audited against the original material. Part-way through, the recording and notes were re-read from the beginning and compared against what existed. That found about a dozen missed items, which were then built. Catching your own omissions is cheaper than having the client catch them.
What came out of it
A full application with sign-up and sign-in, an AI-assisted identification feature using guided photos, a substantial built-in reference library, daily logging across a dozen measures, and a pattern engine that learns what normal looks like over a fortnight and speaks up only when several signals change together for several days — in calm wording rather than alarming wording.
Alongside it: reminders with a calendar and automatic follow-ups, record-keeping with photographs of paperwork and a shareable summary, a location-based community section with alerts and private groups, Bluetooth tag tracking with a map and the day's trail, an AI helper with fixed safety rules that never diagnoses and never gives doses, three subscription tiers with a free trial, and light and dark modes with large-text support and screen-reader labels throughout.
The client's team got a web admin page to correct reference data, review reported posts, suspend abusive users, publish guides and change settings without releasing a new version — plus database security rules so each account can only ever reach its own data.
The dark neon look was replaced with a warm, flat palette, rounder shapes and friendlier typefaces.
By the numbers
- About two days from the first file to the current build
- 11 test builds delivered
- 25 screens, roughly 12,000 lines of app code plus 900 for the server and admin
- About 2,000 lines of automated tests — 38 logic, 76 screen and flow, 17 server and 16 database-security tests, all passing
The service behind this
App rescue. Lost your source code, or lost your developer? If the app is still installed somewhere, there is usually a route back.
Prototype to product. A rough prototype and a list of meeting feedback turned into a structured, tested application.
Honest reporting. Every build comes with a plain list of what is finished, what is partly done and what has not been tested. The status table above is the same one the client watched throughout.
Related: mobile app development, systems integration, more of our recent work.
Start with a conversation
The first meeting is free, and part of its job is working out whether software is the right answer at all. If it is, you will see a working prototype before any long-term money is discussed.
Book a slot or call 020 4652 7504