Our services

Each phase has clearly defined deliverables: an analysis document and user story map, a design prototype and design system, a tested prototype, native apps in the app stores connected to the backend, and monitoring and ticketing after launch. Anything outside that (third-party licences, hosting, marketing campaigns) we name in the proposal so nothing surprises you.

Yes, and we recommend it. In the discovery phase we discard ideas that would cost you too much and set a roadmap. With App as a Service we go further: the first version is live within a month and you keep building only what is really needed.

Most often an unclear brief and mid-project changes. That is why we start with discovery, where we agree on scope, and then develop in controlled iterations where you see and approve every change. Testing and risk mitigation are part of the process from the start, not bolted on at the end.

Approval is in the hands of Apple and Google, but we know their requirements and processes. If everything goes well, an app is usually approved within a few days. For larger or less typical projects, and for projects with a fixed public launch date, we always recommend a buffer of a few weeks for possible fixes or additional specifications. We plan releases to avoid the typical reasons for rejection, and we automate release publishing as far as possible.

Five phases: 1. Strategy Analysis, i.e. discovery (the initial analysis): we understand the problem and build a roadmap. 2. Product Design: up to a clickable prototype. 3. Prototyping and testing: we validate with real users. 4. Development: native apps and web including QA. 5. Launch and support. You can go through all of it, or join where you already are.

Because a wrong decision is cheap in analysis and expensive in development. In discovery we assemble a small team (product lead, UX-UI designer, senior developer), map roles, user stories and architecture, and evaluate alternatives. It often turns out that part of the brief is not worth building, which saves you money.

Yes, we develop in controlled agile iterations. You see results continuously, not just at the end, and every scope change is handled together. As our project lead puts it: when a partnership runs agile, we can focus on the product instead of administration.

We expect it, which is why we work iteratively. We discuss the change from the perspective of user value, business and tech, tell you the impact on time and cost, and you decide together with us. No silent overruns.

Both, natively. We have separate teams for iOS (Swift, SwiftUI) and Android (Kotlin, Jetpack Compose), and we build most apps for both platforms in parallel (Kotlin Multiplatform or React Native). If it makes sense to start with one platform, we will tell you so in the analysis.

Yes. Development includes implementing the API and integrations to the backend and third-party services. We address integrations already at the architecture stage during prototyping, so they do not surprise us later.

Backend, frontend, mobile apps and integrations are all done in-house. After launch we provide system monitoring and ticketing.

Yes, we have QA engineers in the team and we test continuously. Testing and risk mitigation run from the start of development, not just before release. The point is to protect you from unexpected costs in live operation.

Yes, and before development starts. We run qualitative usability tests with a small group of users and an independent facilitator to avoid owner bias. You get the recordings and in-depth interviews.

Yes, we have done it. ISIC came to us with an obsolete app from a previous supplier. We completely redesigned the interface and wrote new code so the project could be maintained and scaled. What makes sense to rebuild and what to keep, we assess based on the state of the code.

Yes, that is our fifth phase. We automate releases, make the data ready for analysis, set up monitoring, and support is ready for continuous development. User data helps you make roadmap decisions. Our designers can work with the launch campaign team.

Yes. We prepare visuals for the app stores and campaigns, and our designers work with your marketing team. We understand ASO, which we did for Slevomat for example. The campaigns themselves are run by your team or agency.