Services

Mobile app development

iOS and Android apps for businesses in Lebanon, with the same work for GCC and remote clients. I design the product, build it, and ship it to both stores.

Market
Lebanon first, GCC and remote
Quote
Fixed, after the scope is agreed
Email
hello@eliechaaban.com

Where it fits

This is for a business that needs its own phone app. Customers booking a service, people finding a place on a map, or staff doing the job away from a desk.

A public brochure, a news page, or a form can stay a website. A logged-in tool that staff use at a computer is often a web app. If you are between the two, the distinction is written up in website or web app.

The first version should be the smallest product that does the real job. How to draw that line is in scoping the first version.

What you get

The pieces depend on the product. A typical mobile engagement can include:

  • An iOS and Android app. Recent apps are in React Native. When a fully native build is the better call, that choice is the one described in React Native versus native.
  • A backend and an admin when the app needs accounts, availability, content or reporting. Pro Clean+ uses a Next.js backend and admin. Local Meals uses .NET Core. NeonTask uses a .NET Core API.
  • Store release. I handle publishing end to end, from store listings to review and release, including from Lebanon. The practical steps are in publishing on the App Store and Google Play.
  • Arabic, English, or both, with proper right-to-left layouts, when the product needs them.
  • A server, when the app has one. On Pro Clean+ and NeonTask that is Docker on Linux, with a CI/CD pipeline that builds and deploys each change. NeonTask gives each client company its own deployment.

Not every app needs every line. Local Meals, for example, is the app, the vendor content and the store release, not a field-service backend.

How a project runs

  1. 01

    Email

    You write to hello@eliechaaban.com. We then talk through the project and the goals.

  2. 02

    Proposal

    A fixed quote, with the scope and timeline agreed in the proposal.

  3. 03

    Build

    Design and development, with regular previews so you see progress.

  4. 04

    Launch

    We go live: App Store and Google Play publishing, and hosting setup when the app has a server.

Ownership

You do. Full ownership of the code passes to you after the final payment. On a new project, the repository and the relevant Apple, Google, domain and hosting accounts are set up in your name.

You should be able to hand the repository to another developer later. That means the code, access to the accounts, and notes on how to build, deploy and run it.

After launch

Support and maintenance are agreed per project, based on what the app and the business need. There is no single package, and there is no standing price on this page.

For a shipped app, the work that usually belongs in maintenance is testing against new iOS and Android releases, updating dependencies, resubmitting when the stores require it, watching crash reports, and fixing bugs that show up in real use. New features, redesigns and new integrations are scoped and priced on their own. The longer account is app maintenance after launch.

Selected work

Three public projects, in the same words as the case studies.

What to send

Email hello@eliechaaban.com. A short note is enough to start. A quote needs the scope, not a polished specification.

  • The problem, in a few sentences, and who uses the app.
  • What each person has to be able to do.
  • How you handle it today.
  • What must be in the first version, and what can wait.
  • iOS, Android or both, and whether you need Arabic, English or both.
  • Integrations, a deadline if you have one, and anything you already know is out of scope.

There is no standard price. The fixed quote follows that scope. What tends to move the number is covered in what drives the cost of a mobile app, and a fuller brief template is in how to write a brief.

hello@eliechaaban.com

Questions

Who is this for?

A business that needs its own iOS or Android app, for customers or for staff. If a website would do the job, say so in the email and I will tell you.

Do you publish to the App Store and Google Play?

Yes. I handle publishing end to end, from store listings to review and release.

Can the app be in Arabic and English?

Yes. Apps can be in Arabic, English or both, with proper right-to-left layouts.

Who owns the code?

You do. Full ownership of the code passes to you after the final payment. On a new project, the repository and the relevant Apple, Google, domain and hosting accounts are set up in your name.

What happens after launch?

Support and maintenance are agreed per project, based on what the app and the business need. New features are scoped separately.

What should I email for a quote?

The problem, who uses the app, the main things they do, which platforms and languages you need, and what can wait. There is no standard price. The quote follows that scope.

How do I pay?

By bank transfer, Whish or OMT.

Let's work
together