Do you build native apps (Swift/Kotlin) or React Native?+
Both. We build native in Swift and Kotlin where there is a concrete need for it, for example special hardware integrations or massive scale. For the vast majority of projects, React Native with Expo is still the right choice: the same user experience as native, at a lower cost and faster to market. We choose based on the project, not a fixed template.
Do you help with App Store publishing?+
Yes. We set up developer accounts, manage signing, certificates, submission, and communication with Apple and Google, so the route into the stores is smooth. The app and the accounts stay with you, so you are the formal owner and responsible publisher. We handle the technical side and guide you through the rest.
Do you work on a fixed price?+
Yes, as a rule. We price the deliverable and the value it creates, not the hours we spend. When the scope is clear, we are happy to give a fixed price directly, for larger projects after a short scoping phase. For more open or exploratory projects, we split the work into defined stages with a fixed price per stage, so you always know what the next step costs.
How long does it take from concept to a live app?+
The timeline depends on scope. A typical project runs through scoping and design, then development, then testing and publishing. We deliver in sprints so you see progress throughout and can adjust priorities as you go.
Do you handle maintenance and further development after launch?+
Yes. A standard monthly agreement covers monitoring, OS updates (iOS/Android), security patches, and minor improvements. Larger changes are estimated separately. We agree the operations terms before signing, usually a 12-month term with three months' notice.
Can you take over an app built by someone else?+
Yes. We start with a brief codebase review (cost and duration depend on size), identify technical debt and risks, and put together a handover plan. We have done this several times when the original supplier closed down or disappeared.