How the work runs
Our first question is whether a backend is needed. A planner that stores data on the phone can stay private and simple; a planner shared between family members cannot. When a server is the right answer, we design the API around the app's real screens and keep the number of services small.
Services are written in Go, TypeScript or Python depending on the workload and your existing systems, with PostgreSQL for data. Each project comes with documentation for the API, deployment and backups, so running it does not depend on us.
What's included
- Decision on whether a backend is needed
- API design matched to app screens
- Sync, accounts and access control
- PostgreSQL schema and migrations
- Admin panel for content and users
- Deployment, logging and backup setup
What you receive
- API documentation generated from the code
- Staging environment for testing
- Deployment and backup instructions
- Access to the source code repository during the project
Languages behind it
Timelines and pricing are quoted per project after a discovery call.
Questions people ask
Where will the backend be hosted?
On infrastructure you choose. We recommend an EU region when the service stores personal data of EU users.
Can you connect our app to an existing API?
Yes. We review the API documentation first and flag anything that affects the app.