Home / Services / Web & Mobile Development
Development · Web · iOS · Android
Web & Mobile Development
The product itself, built and shipped
A web app, a mobile app, or both from one codebase. React and Next on the web, Flutter on mobile, .NET or Node behind them. Built to be handed over — your repo, your accounts, documented well enough that the next developer is not me.
One codebase
iOS and Android from the same Flutter build
AR + EN
right-to-left designed in, not bolted on
Your repo
code, accounts and docs handed over at the end
30+
products shipped under OurInc
Pricing
What a build costs.
Priced against a written feature list, not an hourly guess. Send the list and the number comes back fixed — and it stays fixed unless you change the list.
Web app
On requestone-off
- React or Next.js front end, responsive to phone
- API and database designed and built, or wired to yours
- Authentication, roles and an admin view
- Arabic and English with real RTL layout
- Deployed to your hosting, with the pipeline that redeploys it
- Repo, credentials and a handover doc
Priced per scope. A dashboard and a marketplace are not the same job, so the number follows a written feature list.
Request this ↗Mobile app
On requestone-off
- Flutter, so iOS and Android come from one codebase
- Designs built to the screen list agreed up front
- Offline behaviour, push notifications, deep links
- Store-ready build and signing — publishing sold separately
- Repo, keystore and certificates handed over
Publishing to the stores is its own service; this ends at a signed, installable build.
Request this ↗The full product
On requestone-off
- Everything in both, on one shared API
- One data model, one login, one admin
- Built once, so the mobile app and the site never disagree
- One team and one timeline instead of two
- 30 days of Care plan after launch
Cheaper and faster than the two separately, because the backend is built once.
Request this ↗Add-ons — buy with any package or on their own
Take over an existing build
On requestone-off
- Written audit of what is there and what it will cost to finish
- The critical bugs fixed first, in priority order
- Documented so it stops depending on whoever left
- Then continued on the same terms as a new build
Half of this work is inherited codebases. The audit is a fixed price and stands alone — you are not obliged to continue with me.
Request this ↗Care plan
On requestper month
- Fixes, small changes and dependency updates
- Uptime and error monitoring with a monthly note
- A named person when something breaks
- Priority over new enquiries
Most clients keep it. The alternative is finding someone new the week something breaks.
Request this ↗Compare
Side by side.
One decision really: web, mobile, or the same product on both.
| What you get | Web app | Mobile app | Full product | Take over |
|---|---|---|---|---|
| Runs in a browser | Included | Not included | Included | Depends |
| Runs on iOS and Android | Not included | Included | Included | Depends |
| One shared API and data model | Included | Included | Included | After the audit |
| Arabic and English with real RTL | Included | Included | Included | Included |
| Store-ready signed build | Not included | Included | Included | Not included |
| Written audit before any code | Not included | Not included | Not included | Included |
| 30 days of Care plan | Not included | Not included | Included | Not included |
| Repo, credentials and docs handed over | Included | Included | Included | Included |
| Fixed against a written scope | Included | Included | Included | Included |
The full product is cheaper than the two separately because the backend is built once — the same reason it is the one most people take.
Before we start
What your business needs in place.
Nothing here is code, and each one stops a build from starting.
A written feature list
Not a full specification — a list of what the thing does, screen by screen. This is what a fixed price is fixed against, and the reason scope arguments do not happen later.
One person who can decide
Builds stall on unanswered questions far more often than on hard problems. I need one name who can settle a design question inside a day.
Access to whatever it must talk to
Payment gateway, ERP, existing database, a partner's API — with credentials and, ideally, a test environment. An integration promised but not accessible is the most common cause of a missed date.
A real deadline, or none
A date tied to something — a campaign, a tender, a season — changes the build order. An invented deadline just adds pressure without changing decisions, so I would rather know which it is.
Hosting and domains, or permission to buy them
Cloud account, domain, app store accounts if it ships to a store. I can set them all up, but they must be in your name from the first day, not migrated later.
Terms
How the money and the risk are split.
No retainer to start a conversation, and no invoice for work that never got delivered.
Half to start, half on delivery
Balance falls due when the work is done and handed over. Not delivered, not charged.
Fixed price, not an estimate
The number holds unless you change the scope. If I misjudged it, that is mine.
The clock starts at handover
From the day I have everything on the list, not from the day you pay.
One round of revisions included
Then hourly, quoted before anything starts. No surprise invoices.
You own everything at the end
Code, accounts, assets and credentials. Nothing is held hostage.
Proof
Where this has already been done.
All of it live, all of it mine to point at.
OurGrowth
A multi-tenant AI marketing platform: 70 skills, an orchestrator, a live Shopify carrier app, shipping and payments — React, Next and Node.
our-growth.com ↗Shaaml
A services marketplace with booking, provider profiles and an Arabic and English interface — live and taking appointments.
shaaml.online ↗Bride
A wedding and beauty ecosystem — marketplace, mobile app and e-commerce on a .NET 8 backend. The most sprawling build in the portfolio.
our-bride.com ↗FrontCores
The shared frontend monorepo behind every OurInc product: auth, platform config and a common design system, packaged for reuse.
What you get
What lands in your hands.
Not a demo — a running URL, a signed build and the repo that produces both.
A working web app
On your domain, on your hosting, with the pipeline that redeploys it when you change something.
A signed mobile build
Installable on a real device, Arabic and English, ready for the stores whenever you are.
The repo and the keys
Code, credentials, environment notes and a walkthrough. Nothing depends on me still being here.
A deploy that anyone can run
One command, documented, so the next change does not need a specialist.
What you send
The handover, in one list.
Send it in one go and the clock starts.
- The feature list, screen by screen
- Any designs you have — Figma, images, or a competitor to point at
- Brand assets: logo, colours, fonts
- Access to systems the product has to talk to
- Existing repo and hosting, if you are handing something over
- The languages and markets it launches in
How it runs
Six steps, and you see each one.
-
01
Scope
We turn the feature list into a screen list and a written scope. The price is fixed against this document.
-
02
Foundations
Repo, environments, data model, authentication and the deployment pipeline — before any screen is built.
-
03
Build in slices
Working software every week, on a URL you can open. Not a demo at the end.
-
04
Your review
You use it on a real device and mark what is wrong. One round of revisions is included.
-
05
Hardening
Errors, edge cases, loading states, Arabic layout, and the things that only appear under real data.
-
06
Handover
Repo, credentials, environment docs and a walkthrough. The 30 days start here.
Scope
What this is not, and who it is not for.
These are quoted separately, so the price above stays a price.
- Ongoing content or data entry
- Paid marketing and user acquisition
- Publishing to the app stores — that is its own service
- Hosting and third-party fees
- Brand identity design from scratch
- Legal, tax or compliance advice
Right fit, wrong fit
Saves a call that would end in no.
A good fit
- You know what the product does, even if not how it looks
- You want one person accountable for web and mobile together
- Arabic and English both matter, and RTL has to be right
- You want to own the code and the accounts at the end
- You have an unfinished build somebody walked away from
Not a fit
- You want a price before there is a feature list
- You need a team of five starting Monday
- The scope is expected to change weekly
- You want the cheapest hourly rate on the market
After launch
After it ships.
Software does not stop needing attention the day it ships. Dependencies age out, an OS update breaks a screen, traffic finds the one slow query. Every build includes 30 days; the Care plan keeps a named person on it after that.
Questions
The ones people actually ask.
Can you give a price before the scope is written?
A range, yes; a price, no. The honest version is that a fixed price without a feature list is either padded to cover the unknown or gets renegotiated halfway. Writing the scope is a short paid step and it is yours to take elsewhere.
Why Flutter rather than native iOS and Android?
One codebase, one team, one set of bugs — for the kind of apps most businesses need, native buys very little and costs roughly double. If your app depends on something platform-specific, I will say so and quote native instead.
What happens if it takes longer than planned?
The price is fixed against the written scope, so overrun is mine unless the scope moved. If you add a screen, we price the screen.
Can you finish what someone else started?
Often. It starts with a fixed-price audit that tells you honestly whether finishing it is cheaper than restarting — sometimes the answer is that it is not, and that answer is worth having before more money goes in.
Who owns the code?
You do, from the first commit. It lives in your repo under your account, not mine.
Tell me what you have, and I will tell you what it takes.
The app, the market and the deadline is enough to get a straight answer on scope, price and timing — usually the same day.