Common questions

Yes. The code, the designs and the project assets are yours, in every project.

Yes. You can start with one platform or build for iOS and Android together. We decide whether to use a shared codebase or separate native apps based on the project. A second platform can be added later.

Yes. We prepare the store listings, submit the app and manage the technical changes needed during review within the agreed project scope.

We first review your existing system, its API and the available access options. If integration is feasible, we agree on how the app will connect to it and include that work in the project scope.

We agree on the change with you before doing it. Nothing is added without your approval.

Swift and SwiftUI on iOS, Kotlin on Android. Flutter when one codebase makes more sense. Firebase or Supabase for the backend. We recommend one during scoping and explain why.

Every project includes 30 to 90 days of post-launch support for fixes to the delivered work. New features are scoped separately. If you need ongoing maintenance, we agree on a separate plan.

Yes. We review the current code first and tell you honestly whether to continue with it or rebuild.

We first review the records and the export options in your current software. We then agree on which data can be transferred, how it needs to be prepared and the migration scope to include in your proposal.

We design the screens around your team’s everyday tasks and terminology. Each user receives training for their role, and we support the team as they start using the system.

The browser-based system works on desktop, tablet and phone. Your team accesses the same records according to each person's permissions. A separate iOS or Android app can be scoped if you need one.

We can connect your business's payment provider account through its supported APIs. The provider processes payments; your system records the results and payment status. You can also record and track payments manually without a payment integration. We confirm the required connections in your proposal.

Yes. If online booking is included in your scope, customers can use your booking link to choose an available time. The appointment is saved to your calendar, and reminders follow the rules we agree on.

The timeline depends on the features, integrations and any data migration. We confirm the dates for the first test version and go-live in your proposal before work starts.

Yes. We review how the new feature would work with your existing system. Before development starts, we agree on its scope, cost and timeline separately.

Your data is stored in your own cloud account. We agree on hosting, backups and access arrangements based on your project needs and set out the related service costs in your proposal.

Yes. The source code developed for your project and your data belong to you. We set up project accounts in your name or use your existing accounts. If you choose to work with another team, we hand over the code, documentation and access they need.

Your proposal sets out the scope and duration of transition support. Ongoing maintenance, technical support and further development can be arranged separately based on your needs.