Skip to content

Mobile app development · Saudi Arabia

Let’s work out what your app needs. Then build it.

You might have an idea, a service customers already use, or an app that needs more work. I help you choose the scope and handle the development myself. You work directly with me throughout.

From a rough idea to an app you can try

Illustrative example, not client work
01

The idea

Book a visit?Book a visit?ServiceTimeConfirmstart hereevery feature??change the time?points & rewardsnot yet

We start with sketches and questions. Your idea does not need to arrive neatly packaged.

02

The first version

One complete booking

Book your visit

  1. 01Service
  2. 02Time
  3. 03Confirm
points & rewardsnot yet

Defer rewards. Keep the booking tests.

Choose one useful journey. Leave the extras for when they earn their place.

03

Try it

Studio visit

Book your visit

Choose a time that suits you

Sunday · demo only

Try working software and review the details together. Pick a time and test the booking.

Start with what the customer needs to do

For a booking app, that might be choosing a service, finding a time and managing the booking. We work through that journey before deciding which features belong in the first release.

We also look at how your team will run the service: manage bookings, answer customers and correct mistakes. Those tools need a place in the scope, too.

A first version with a clear purpose

An MVP should let real users try the main idea. We decide which journey must work, what we need to learn and what can wait. It still needs appropriate testing and care with user data.

Sometimes a website or an existing service is enough to test demand. If that looks like the better starting point, I’ll say so before we commit to a custom app.

From requirements to release

We agree on the intended users, platforms, screens, data and integrations. That includes decisions about Arabic and English, payments or subscriptions where needed, and the tools you will use to manage the app.

You try working software as I build. Before handover, we agree on the testing, deployment, access and documentation the project needs. App-store submission and any support after launch belong in that agreement; a store’s review timing is outside my control.

I also run my own apps

Mounjari, my medication-tracking app, has 150 paying users. I work on its releases, subscriptions and Arabic wording, including feminine address when a user selects female.

That is my own product, not a client result. It gives you something real to inspect before discussing how I would approach yours.

See Mounjari and the rest of my work

Questions before starting

How do we choose between iPhone, Android and the web?

We agree on the platforms your customers need and choose the approach around them. The estimate should name the platforms, integrations and release work it includes, rather than assume every version costs the same.

How much does app development cost?

The scope determines the estimate. Agreed development work is billed at SAR 250/hour for actual time; third-party costs are separate. Read the cost guide for what affects the hours and what to prepare.

How long will it take?

I can give you a useful schedule after we define the first version and check the dependencies. I won’t promise a launch date before understanding the work.

Can you improve an existing app?

Yes. We first review its code, current problems and the access available. That review helps us decide whether to improve what is there, replace a part or rebuild.

Tell me about your app.

Who will use it, what do they need to do, and what have you tried so far? A short explanation is enough to start.