Biencall
iOS app for staying close to you people
Scroll to explore
Biencall is an iOS app for staying close to your people, sharing your availability and connecting when everyone is ready. We took the whole app off Supabase and onto AWS, and we keep building it in Swift.
Services
UI & UX Design
Software Development
Industry
Software
Date
In progress
The challenge
Biencall is an iOS app for staying close to the people who matter: you share your availability, and you connect when everyone is ready. The app was live and working, but it was built on Supabase, and it had outgrown that setup.
As the product grew, the team needed more than Supabase comfortably gave them: more control over the backend, better reliability, and real room to scale. The catch is that the app was already live, with real users, so the backend could not just be ripped out. It had to be moved without breaking the product.
Migrations like this are where things go wrong. Data has to move, auth has to keep working, and the app has to keep running through the whole switch.
The Solution
We migrated the entire app from Supabase onto AWS. The database, authentication, and APIs were moved onto AWS services and wired back together, so the app kept working on the other side.
We used the migration as a chance to fix the weak spots rather than just lift and shift. That meant more reliable real-time availability and calling, cleaner push notifications, and a backend architected to scale as the user base grows instead of straining under it.
On the app itself, we keep building in Swift. The iOS codebase is where we do most of our ongoing work, shipping features on top of the new, sturdier foundation.
The result
Biencall is an iOS app for staying close to the people who matter: you share your availability, and you connect when everyone is ready. The app was live and working, but it was built on Supabase, and it had outgrown that setup.
As the product grew, the team needed more than Supabase comfortably gave them: more control over the backend, better reliability, and real room to scale. The catch is that the app was already live, with real users, so the backend could not just be ripped out. It had to be moved without breaking the product.
Migrations like this are where things go wrong. Data has to move, auth has to keep working, and the app has to keep running through the whole switch.
.avif)
The takeaway
Outgrowing your first backend is a good problem to have. Migrate cleanly to AWS, use the move to fix the weak spots instead of carrying them over, and the app comes out more reliable and ready to scale.
