Skip to content
Stan Leon

Mobile app

An iPhone or Android app, designed with you and taken all the way to the stores.

Request a quote Questions →

Request

Tell me about your project

You are asking about: Mobile app. I reply by email, usually within two working days. Please do not include passwords or logins.

Platforms *
Indicative budget
Target date

The three or four things the app must do on day one.

What you want to achieve, where things stand, anything that matters to you.

Most first versions fail by being too big, not by being too small. My job in the first week is as much to cut as to build: find the smallest app that someone would genuinely use, and get it into their hands.

I publish and maintain my own apps on the App Store, so I know how it goes after release: the review, the first bug reports, the system update that breaks something. That experience goes into how I plan your project.

Who it is for

  • Founders who want a first version in the hands of real users, not a year-long project
  • Businesses that need an app for their customers or for their field team
  • Coaches, clubs and professionals whose work needs a tool in the pocket

What is included

  • Scoping workshop: the few features the first version needs, and the ones that can wait
  • Interface design that follows each platform's habits, then development
  • Data and accounts if needed: sign-in, sync across devices, backend and database
  • Push notifications, purchases or subscriptions, and integrations with existing services when the project requires them
  • Test builds on your own phone from the first weeks (TestFlight on iOS)
  • Submission to the App Store and Google Play, including screenshots, descriptions and privacy details

How it works

  1. 01

    Scope the first version

    One page that lists what the app does, for whom, and what it deliberately does not do yet.

  2. 02

    Design the key screens

    The main flows are drawn and clickable before the code grows, which is cheaper than changing finished work.

  3. 03

    Build in short cycles

    Every one or two weeks you get a build on your phone, try it and tell me what feels wrong.

  4. 04

    Release and follow

    Store submission, handling of the review, then a period of fixes based on real use.

Indicative timeline

A focused first version typically takes 2 to 4 months; store review adds a few days.

Examples from my own work

Questions

Native or cross-platform?

If your audience is mostly on iPhone, native iOS gives the best feel and the best access to the system, which is how I built Football Tactics and Narrafit. If you need iPhone and Android at once from a single code base, Flutter is usually the better route, as in Homebit.

Do you handle the App Store submission?

Yes: build, signing, listing text, screenshots, privacy details and the answers to App Review. The developer account itself must be in your name.

Can the app work offline?

Yes, and for many apps it should. The decision is made at the scoping step because it changes how data is stored and synced.

What happens after release?

New iOS versions and your users' feedback mean an app needs care. We can plan updates and fixes, either as separate missions or under a maintenance agreement.

Do you also build the backend?

When the app needs accounts or shared data, yes. I build and run backends on Cloudflare for my own products and can do the same for yours.