What we do
- Screen design and a clickable prototype: before any code is written, you see the flow of the app on your own phone.
- One codebase for iPhone and Android: both platforms are built from the same React Native code, so features arrive on both at the same time.
- Accounts and notifications: sign-in with email or Google, starting as a guest, push notifications.
- Server and database: user data, real-time features (live results, matchmaking), scheduled tasks and access rules.
- Store release: App Store and Google Play account setup, store page text, screenshots, privacy texts and the review process. In apps where users can create an account, the in-app account deletion path that the stores require is part of the plan from the start.
- After launch: bug fixes, support for new operating system versions and new features. With a maintenance agreement, crash reports in the store dashboards and user reviews are also monitored regularly.
Who it is for
- Businesses that want to offer their customers their own app (ordering, appointments, loyalty, catalogs). Customers install the app on their phone once; notifications such as campaigns or appointment reminders reach them directly.
- Companies that want an app for their field team: tasks such as keeping records, adding photos and filling in forms are done on the phone instead of on paper. If it has to work without internet, see field and inventory apps.
- Founders who want to test an idea with a small first version. The first version is limited to the few screens that show the core value of the idea; once you see how users respond, we decide together what to add next.
- Anyone who wants a mobile game built; details are on the game development page.
App or website? Not every project needs a mobile app. If people will visit you only now and then, for example to look up information or fill in a form, a website that works well on phones is often enough and does not involve the store process. An app makes sense when users will open it often, receive notifications, use phone features such as the camera or location, or need it to work without internet. We talk through which one suits you in our first conversation; for the web side, see websites and web apps.
How we work
- Intro and scope: together we write down who the app is for and which screens the first version will have. The first version is kept small on purpose: the screens that do the app's main job come first, and features that can wait go on a separate list.
- Prototype: the screens are prepared as a clickable draft; we do not move on to code until you approve the flow. Screen order, text and buttons are settled at this stage; a change made here is much easier than one made after the code is written.
- Development: you install the test build on your own phone (TestFlight on iPhone, a Google Play test track on Android) and follow progress in the working app. With each new test build we write a short note on what changed, and we address your feedback in the following builds.
- Release and maintenance: the store page text, screenshots and privacy details are prepared, and the app is submitted for Apple's and Google's review. We make any fixes the review asks for; updates after launch go out the same way.
What sets the price
- The number of screens and features; what goes into the first version.
- Integrations such as user accounts, payments, notifications and maps.
- Server needs: only storing data, or real-time features as well.
- Whether the design is already done.
- What you expect in maintenance and updates after launch.
Store account fees (Apple's and Google's own fees) are separate from the development fee, and the accounts are opened in your name. The quote is free; we send the scope, timeline and price in writing within 2 business days.
Example project
Trivium Arena
A real-time trivia game where 1–4 players answer the same question at the same time. iPhone and Android come from one codebase; question order, timing and scoring are calculated on the server. Starting as a guest, sign-in with email or Google, and real-time matchmaking are also part of this project.
FAQ
How long does it take to build an app?
It depends on the number of screens, server needs and integrations. After we talk, we define the scope of the first version together and give you a written timeline in the quote.
Is it written separately for iPhone and Android?
No. Both platforms are built from the same React Native code, which reduces both the timeline and the maintenance load. If something is specific to one platform, that part is written separately.
Whose name is the app published under?
Yours. The App Store and Google Play developer accounts belong to you; we help with the setup and with preparing the store page.
Do I get the source code?
Who owns the source code and the rights is stated clearly in the quote. Usually it is transferred to you once the work is delivered and payment is complete.
Can you improve an existing app?
We review the code first, then tell you plainly, with reasons, whether taking it over and improving it or rewriting it makes more sense.
Do you provide updates after launch?
Yes. We fix bugs found after delivery; for regular updates, server monitoring and new features, a separate maintenance agreement can be made.
Tell us about your project
Write a few sentences about what you want to build, who will use it, and whether you have a date in mind.