Development — Mobile Apps
Your customers reach for their phones first
The problem: a business that exists only on the web and social media rents its audience. An app puts your service on the customer's home screen — bookings, orders, loyalty, and support one tap away — but only if it is fast, stable, and maintained. A badly built app is worse than none: it collects one-star reviews in public.
What we deliver
- Cross-platform apps from a single codebase (React Native / Expo): one build serves Android and iPhone — no paying twice for two native apps.
- Android-first development, tested on real mid-range Android phones — the devices your customers actually carry.
- App UI/UX designed inside the build: screens, navigation, and full Arabic (RTL) and English layouts.
- Business features scoped in writing before we start: content, forms, accounts, notifications, and integrations with the systems you already use, where feasible.
- Play Store release support: signed builds, store listing assets, and submission through your own developer account; iOS builds prepared through Expo for your Apple account.
- Handover in your name: source code, builds, and store accounts are yours, with a walkthrough — plus post-launch maintenance under our maintenance offer.
Who it's for
Businesses whose customers come back repeatedly — clinics and salons with bookings, retailers with repeat orders, training providers with enrolled students, and service businesses whose clients need a direct channel that doesn't drown in a crowded social inbox.
Scope & limitations
| Included | Design and build of the agreed screens and features in one cross-platform codebase, an Android release build with Play Store submission support, an iOS build via Expo, two structured revision rounds, and a handover walkthrough. |
|---|---|
| Not included | Native iOS-only development, games, and features that depend on paid third-party services (payment gateways, maps, messaging APIs) unless they run on your own accounts and subscriptions. |
| Timeline | Set in the written scope once features are fixed. Store review times are outside our control, and waiting on your materials, accounts, or approvals pauses the clock — in writing. We never promise an unconditional date. |
| Your inputs | Your content and brand assets, a Google Play developer account in your name (Google charges a one-time registration fee), an Apple Developer account if you want an iOS release, and one person who can approve rounds and test builds. |
Our workflow
Brief & scope
Questionnaire and call, then a written scope with screens, features, exclusions, timeline, and price.
Design direction
You approve the app's look, navigation, and screen flow before full build-out.
Build & device testing
Staged build with test versions you install on your own phone, and two defined revision rounds.
Release & handover
Store submission from your accounts, a walkthrough session, and full source-code handover.
The stack runs our own products
This is not a sideline service: the same React Native / Expo stack runs our own products. We designed and built an accessibility app that helps blind and visually impaired users with on-device AI, and we operate a community platform whose mobile app we develop in-house. We quote no store ratings or download numbers for them — they are our own products, built and device-tested the same way we would build yours: on real phones, in Arabic and English.
Questions, answered plainly
Do I need separate apps for Android and iPhone?
No. We build one cross-platform codebase with React Native and Expo that produces both. Development is Android-first; iOS builds are prepared through Expo and released through your own Apple Developer account.
Who owns the app and the source code?
You do — completely. The store accounts, the source code, and the builds are in your name from day one, and nothing is withheld or locked, including in a payment disagreement.
Can you publish the app to the Play Store for me?
Yes — we prepare the signed build, the listing assets, and the submission, all inside your own Google Play developer account (Google charges a one-time registration fee, paid by you to Google). We never publish client apps under our own account.
Will the app work fully in Arabic?
Yes. Arabic RTL and English layouts are both part of the build, and both are tested on real devices before release — not added as an afterthought.
What happens after launch?
Post-launch maintenance is available under our maintenance offer: platform and Expo updates, store policy changes, and small fixes, scoped in writing. New features are quoted as separate scopes before any work begins.
Have a project in mind?
Tell us what you are trying to build or fix. We reply with honest next steps — including if we are not the right fit.