Latest
iOS and Android: one codebase or two?
The decision is not driven by price or fashion but by how much the app has to talk to the phone itself. Where the line falls, what "almost identical" means, and when double the cost is justified.
Topic 02 / 064 articles
Apps & products
Whether you need an app or a mobile site, one codebase or two, what the first version should contain, and what happens after launch.
Articles on this topic
MVP scope: what to build first and what to postpone
A first version is not a small version of everything — it is one workflow, end to end. This guide gives a concrete postponement list, separates the work that cannot be postponed, and suggests agreeing in advance what observation would count as evidence.
What it takes to keep an app running after launch
An app is not a one-off project. Even if you change no features at all, the platforms require yearly updates, and without them the app can no longer be updated in the store. This guide lists the real cost categories across twelve months, with no invented figures.
Does your business need an app, or is a mobile website enough?
Choosing a mobile app is rarely a design decision. Three things decide it: whether the solution genuinely needs phone capabilities, what has to work without a connection, and who owns the store accounts. This guide takes one need and walks it through four platform routes so you can see what actually changes.
Related services
The services this topic is relevant to.
Web app development
Web app, SaaS and MVP development: a first usable version, user roles, billing, integrations and a clean handover to your own team.
Mobile app development
Mobile app development: platform choice, offline behaviour, store submission, supported devices and the update work that follows launch.