How I help / Build it

Mobile apps. Made for thumbs, not manuals.

I design and build mobile apps with a clear purpose: a tool for people in the field, a service your customers use on the move, or a companion to software you already run.

Design and development · Newbury, UK · Remote worldwide

AI-generated portrait of Richard as a developer in clear glasses and a grey hoodie, frowning in concentration at his laptop, a red enamel mug beside it, on a sky-blue backdrop
RichardMobile apps

Mobile apps, at a glance.

What it is

An app for a clear job on a phone or tablet: field work, customer self-service or a mobile view of your existing systems.

Job first

Most good apps do one thing very well. We agree that one thing before we talk about features, platforms or app stores.

Works on the move

Patchy signal, small screens and one free hand. The app is designed and tested for the conditions people actually use it in.

Ready for release

Permissions, data handling, store listings, updates and support are planned before launch, not discovered afterwards.

When an app is the right answer.

Not every idea needs an app. Sometimes a well-built mobile website does the job for less, with no app store in the way. If that is the case, I will tell you.

An app earns its place when people use it often, need it away from a desk, or rely on something the phone itself does best.

Work happens in the field

Visits, inspections, deliveries or stock checks. Capture the information where the work happens, not typed up later.

Customers expect self-service

Bookings, tracking, account details or support, in their pocket and without a phone call.

Your software needs a companion

A focused mobile view of an existing system, for the few tasks people need on the go.

How I build an app.

Name the one job

Agree who uses the app, where and how often, and the task it must make easy.

Design for small screens

Sketch the flow and test it as a clickable prototype on a real phone before building anything.

Build and test on devices

Develop in small releases and test on real phones, including slow connections and awkward inputs.

Release and look after it

Plan permissions, data handling, updates and support, so launch is the start of the app’s life, not the end of the project.

What I bring to it.

I build software myself as external / fractional CTO at Kona Libre, covering development, testing, version control and release coordination. I also do UI and UX design, including freelance work on 99designs.

Earlier in my career I was a field engineer at T-Mobile, so I know what it is like to need the right information away from a desk.

A sensible first step.

Focused discovery is a good start for a new app: one defined job, a solution plan and a clickable demo on a real phone when that helps.

Once the scope and acceptance criteria are clear, the build is quoted to scope using the defined implementation day rate as the planning basis. Updates after launch can sit in a planned improvements allowance.

Focused discovery, builds and improvements

A useful next step

What should the app help people do?

Describe who would use it, where and for what. The first 30-minute conversation is free.

You’ll speak directly with me about the problem, the fit and a sensible next step.

Email Richard

Opens your email app with a few prompts.
hello@richardzoltantoth.com

Online meetings worldwide.
No VAT added — I’m not VAT registered.
View the full engagement terms.