How long does it take to publish an app?

A discovery sprint takes two to four weeks and settles scope, architecture and estimate. From there, a first published version usually ships in eight to twenty weeks, depending on the number of screens and integrations.

Do you build native or cross-platform?

Both. Native when the app leans on hardware or performance — camera, maps, sensors, heavy field use. Flutter when a single codebase covers iOS and Android and the time saved is worth it. The choice is made during discovery, with the reasoning written down.

Who owns the store accounts?

The client company. We publish under your account, or create it in your name and hand over the credentials. The app and the code are yours.

Mobile app development for companies

We design, build and publish iOS and Android apps — for the team working in the field, for the customer buying from a phone, and for the product that has to reach the stores at store quality.

Talk about a project

When a company needs an app of its own

The conversation almost always starts the same way: people work away from the office — sales reps, technicians, drivers, inspectors — and their process lives in paper, chat apps and phone calls. The data only reaches a system when somebody types it again, hours later, with errors.

An app fixes that by taking the system to where the work happens: the order is recorded in front of the customer, the inspection is signed on site, the photo goes with it. When the signal drops, the app stores and syncs later — that is the part separating an app that works in the field from one that only works in a demo.

What we deliver

Native apps in Swift (iOS) and Kotlin (Android), or Flutter when one codebase serves both platforms
Offline operation with synchronisation, for field work
Integration with the ERP, the CRM and the APIs the company already runs
Publishing and managing the App Store and Google Play accounts
Crash and performance monitoring after launch
Continuous evolution: new versions, fixes and support with agreed response times

Apps we have published

Three of our apps are in the stores right now: Incognito, for privacy and security, with more than 5 million downloads on Google Play; THE GRID, for meditation, with live sessions running worldwide at the same moment; and Bertoldi Connect, for product and order management inside a flower company.

They are very different projects — global consumer and B2B operations — and that is what store publishing teaches: the review rules, the release cycles and the quality bar are the same for both.

Questions

How long does it take to publish an app?: A discovery sprint takes two to four weeks and settles scope, architecture and estimate. From there, a first published version usually ships in eight to twenty weeks, depending on the number of screens and integrations.
Do you build native or cross-platform?: Both. Native when the app leans on hardware or performance — camera, maps, sensors, heavy field use. Flutter when a single codebase covers iOS and Android and the time saved is worth it. The choice is made during discovery, with the reasoning written down.
Who owns the store accounts?: The client company. We publish under your account, or create it in your name and hand over the credentials. The app and the code are yours.

Let's talk

Tell us what needs building. You get a reply from an engineer, usually within one business day.

Talk about a project See every service