Mobile apps

One codebase for iOS and Android, offline mode, push notifications. For services that customers need on their phone, not only in the browser.

PWA · CAPACITOR

Two native apps means two teams, two release cycles and every bug fixed twice. For most services that is unnecessary: the screens are the same, the data is the same, only the store the app is installed from differs.

I build the app on one codebase. The web version runs as a PWA and installs to the home screen, and for the App Store and Google Play the same version is packaged with Capacitor. Push, camera, geolocation and offline mode connect through native plugins. The backend is shared with the web service, so a new feature reaches every platform in one release. I show a prototype with the main screens on your phone in a week.

You get an app in both stores and a web version on your own domain — one code, one release cycle. This is how Mnogodel works: installs as a PWA, opens offline, updates without waiting for store review.

What is included
  • An app for iOS and Android from one codebase
  • Web version as a PWA: home screen and offline mode
  • Push notifications, camera, geolocation
  • Publishing to the App Store and Google Play
  • A shared backend with the web version
  • Analytics and crash reporting
How we work
01
A 30-minute callWe go through the scenarios and what the app needs from the phone: push, camera, offline. I name the timeline and the budget.
02
A prototype in a weekThe main screens on your phone. We check navigation and gestures before the main development.
03
Weekly releasesThe PWA on the domain first, then the store builds. Every week a new version reaches the testers.
04
Publishing and supportI take the app through store review. Then monitoring, updates, a reply within the business day.
Consultation

Thirty minutes to decide whether we work together