Frequently asked
questions

We lock the scope in writing and give a fixed price. Anything outside that scope is quoted as a separate line item, so no surprise invoice appears mid-project. For longer engagements a monthly dedicated team is also possible.

You do. On delivery the entire source code, the deployment documentation and the accounts are transferred to you. We prefer to keep the repository somewhere you can reach from day one.

Yes. Six months of bug-fix cover after delivery is standard; after that we sign a monthly maintenance agreement with a committed written response time. A release schedule and a changelog are part of the maintenance scope.

We will. First we produce a technical audit report: what can be fixed, what needs rewriting, and the cost of both paths in figures. After the report, the decision to continue is yours.

Yes. App Store and Google Play submission, permission texts, the privacy declaration, signing and the rating questionnaires are on us. Store review times are outside our control, so we show them as a separate line in the schedule.

Yes. We build 3D mobile apps with Unity and C#; in 2026 we produced and published five of them ourselves, from concept to Google Play release. Interaction design, 3D production, store publishing and maintenance across simulation, adventure and sport genres all run from one team.

Flutter on mobile, Unity for 3D apps, React + Vite for web and admin panels, Node.js and MongoDB on the server. For map-heavy work, MapLibre GL and the Valhalla routing engine on our own servers. We choose technology for the job, not out of habit.

Consent texts are stored with a version stamp, retention periods are defined and expired data is deleted automatically. The privacy notice, the privacy policy and cookie management are part of the delivery scope.

Yes. We can run correspondence, documentation and the quoting process in English, and multilingual content infrastructure is already standard in the products we build. Our own platform ships with six interface languages.