Have you started building your app? What does it need?

You get a project board and preview links, so you always know where your project is up to and can try out each change as it’s ready. When a decision needs explaining, I send you a short video walkthrough.

Will my app have a page that explains it?

Yes. Your app’s landing page, the page that explains it and gets people to sign up, is part of the build, written from what we learn about your users. If you want a fuller website for your product, we price that on the call.

What does the price depend on?

It depends on which features your app needs, such as sign-in, payments, bookings or a dashboard, whether it’s a web app, a mobile app or both, how many user journeys it covers and which integrations it needs. We agree all of that before I quote.

How long does the work take?

The agreed work on an existing app usually takes 2–4 weeks. A new build depends on what the app needs, and its dates are set in the plan before work starts.

When and where can we meet?

Calls are on UK evenings and weekends, and if you’re in London, I’m happy to meet in person.

How do I know the work is done properly?

Every feature is tested, and you get a link where you can see each test pass as the work progresses. Changes are checked on a separate test version first, so nothing breaks for your users.

Who owns the app?

You do. I set everything up in accounts you own from day one, and the code becomes yours when the final payment clears.

Do you check the app is secure?

I use established providers such as Supabase for sign-in and data, and I run the project’s own tests along with checks for committed credentials and vulnerable dependencies. That isn’t a penetration test, a formal certification or proof that your app meets legal standards. Where an app carries real risk, I’ll say so and recommend a specialist.