Photo: Gilles Lambert / Unsplash
The app was finished. Almost.
An app built with vibe coding looked finished. What was missing was the part you can't see.
How it came about.
The app had been built with vibe coding, and everyone assumed it was finished.
But the backend was missing – and with it everything that comes with it: data exchange, the setup behind the scenes and the ability to work seamlessly across several devices.
On top of that, hosting and the entire path into the app stores were missing.
What we found.
What we did.
The interface stayed as it was. We built the part behind it.
- Built the backend: The app now stores its data centrally instead of only on the device.
- Set up synchronization: App and backend exchange data – so you find the same state on every device and can switch seamlessly between devices.
- Provided hosting: The backend runs on a server that the app can reach from anywhere.
- Set up publishing: The path into the app stores is in place: builds, store listings and submission for review.
The prototype became an app you can install and use on several devices.
Same application. Clear state.
What others can learn from it.
An app isn't finished when the interface is done. It's finished when everyone who is supposed to use it can install it and find their data on every device.
Backend, hosting and release aren't details. They are the part that turns a prototype into a product.
All case studies →Building it isn't running it.
We review first, before we take on responsibility.
Request an Operations Check ↗