Mobile Apps

A native app is written twice: once for iOS and once for Android, with two teams, two codebases and double the maintenance. We build in Flutter: one codebase that produces two real apps on both stores. For most business apps — a catalogue, services, booking, contact — the performance difference is imperceptible to the user, while the difference in cost and time is large.

A website is better when the goal is to be found by people who don't know you: search, advertising, a first visit. An app is better when you have returning customers you want to reach directly — an icon on their screen, notifications, and an account that remembers their preferences. If there is no repeat purchase or repeat use, a website first is the sounder call.

Usually between a day and two weeks at Apple, and often faster at Google. A build can also be rejected and the cycle repeated. That is why we always separate build time from review time: the first is our commitment, the second is not in our hands. We prepare the submission, file it, follow the review and answer its notes through to approval.

Your business's, not ours. This is not a preference but a condition: Apple requires each business to have its own account (Guideline 4.2.6), and publishing from an agency account is rejected. The practical consequence matters more: the app, its ratings and its data stay yours, and you can change development provider without losing any of it.

The offer includes a month of support and one round of revisions. After that, apps need ongoing attention — not because something broke, but because Apple and Google ship new operating systems every year and their requirements change, and an app that is never updated is eventually removed from the store. We propose that as a separate maintenance subscription.