The problem we solve
Plenty of apps get built before anyone answers a simple question: why would someone open this a second time? The result is an app that repeats the website more awkwardly, or one that gets installed and removed the same day. A second problem only surfaces after launch. The app was handed over as a finished file — no store accounts in the company name, no signing keys, no release pipeline, no crash reporting — so every small change becomes a negotiation and every operating system update becomes an emergency. We address both: validate the need before building, and hand over a complete release process rather than a binary.
Expected outcomes
- One coherent experience across iOS and Android, with no gaps between the two.
- A clear reason for users to return, based on a need tested before the build.
- Shipping an update as a routine task for your team rather than a fresh project.
- Visibility into what people do inside the app and where they stop.
- Alerts when users hit crashes, before the complaints arrive.
- Store accounts, source code and signing keys in your company name from the start.
Who this is for
- Service businesses whose customers interact frequently and need faster access.
- Startups building a mobile-first product that need a first release the market can test.
- Companies with field teams who need a tool that works away from the office, sometimes offline.
- Organisations with an established web platform that need a mobile extension, not a duplicate.
Use cases
- A customer app for booking, ordering or tracking service status.
- A field-team app for logging visits, photos and reports from site.
- A loyalty and offers app with notifications driven by behaviour rather than broadcast.
- A first release of a mobile product, put in front of real users to test the idea.
- Rebuilding an existing app that has stopped being updated or keeps failing store review.
- Adding a mobile layer over an existing internal system through its APIs.
Deliverables
- A published app on both stores under your own developer accounts.
- Source code in a repository you own, with signing keys and certificates.
- A documented release pipeline any developer can use to ship a new version.
- Usage analytics and crash reporting configured and connected.
- Store listing assets in Arabic and English.
- A short operating guide for managing notifications and in-app content.
Project phases
Validation and scoping
Defining the user, the need and the core function, and agreeing what enters the first release and what waits.
Design and experience
User flows and screen design aligned to each platform convention, with both languages supported.
Development in short cycles
Features built in the agreed order, with a test build on your device at the end of each cycle.
Integration and device testing
Back end, notifications and payments where relevant, then testing on real devices and poor-network conditions.
Store review and release
Listing assets and declarations prepared, then submission, review tracking and resolution of any notes.
Post-launch
Crash reports and user behaviour monitored, with fixes handled during the follow-up window.
- Estimated timeline
- 10 to 18 weeks
- An estimate that depends on scope and how quickly reviews come back — not a contractual commitment in itself.
- Pricing
- After scoping
- Price depends on screen count and logic complexity, on whether the back end exists or is built alongside the app, and on whether native development is required instead of a shared codebase. We send a proposal after the scoping session.
Scope and working details
What is in and out of scope, how we work, and what we need from you.
What is included
- A working session defining the user, the need, and the function that deserves to be an app.
- Experience and interface design that respects each platform convention instead of forcing one look on both.
- Right-to-left Arabic and English support inside the app.
- Development for both stores from a single codebase where that is the right choice.
- Back-end connectivity through APIs, with secure authentication and session handling.
- Push notifications, and defined behaviour when the network is weak or absent.
- Crash reporting and in-app usage analytics from the first release.
- Store listing preparation: description, screenshots, categories and privacy declarations.
- Testing on real devices across a range of capability, plus test builds distributed to your team.
- Submission for review and management of reviewer feedback through to publication.
What is not included
- Developer account fees and their recurring store subscriptions.
- Paid install campaigns and ongoing app store optimisation as a retained service.
- Licences for paid third-party services or SDKs the app depends on.
- The store review decision itself — we prepare for the requirements and resolve every note raised, but approval rests with the store.
- Producing and managing in-app content after launch.
How we work
We open with one question: what makes someone open this app a second time? Anything that does not serve that answer leaves the first release and is logged for later. We design, then build in short cycles, and a build lands on your own device early rather than at handover. Testing happens on real devices across a spread of capability, not on the simulator alone, because how the app behaves on a mid-range phone is what most of your users will experience. Before submission we walk the store requirements line by line to reduce the risk of rejection and delay.
What we need from you
- Developer accounts on both stores in your company name, or authority to create them.
- Access to the back-end systems or APIs the app will rely on.
- Brand assets and core content in Arabic and English.
- A privacy policy and terms of use approved by your own legal counsel.
- A group from your team who will use the test builds and give feedback on time.
Methodology and technology
A single codebase in Flutter or React Native covering iOS and Android, which suits most business apps because it lowers maintenance cost and keeps the two experiences aligned. We move to native Swift or Kotlin when the app leans heavily on device capabilities or needs particular performance, and we explain the reasoning and the cost implication before starting. The app talks to the back end through documented APIs, with local storage so it stays usable on a weak connection and syncs when the connection returns. Test distribution runs through the official store tooling, with crash reporting and usage analytics enabled from the first build.
From our work
Lavin Fashion: a complete commerce system, built from scratch
Store, app, AI shopping assistant, automation and supplier links, for a company our owner is a partner in.
How this connects to the rest of our work
A service rarely works alone. These come before it or alongside it, and these are the solutions it forms part of.
Services that work with it
UI/UX and Product Design
Research, tested prototypes and a documented design system — in Arabic and English, ready for engineering.
Web Applications and SaaS Development
A web app or SaaS product built around your real process — permissions, integrations and code you own.
APIs and Systems Integration
Documented APIs and an integration layer that keeps your systems in step — and alerts you when it cannot.
Digital Products and MVP Development
Idea to working product: tight scope, production-grade build, and a next round decided by real usage.
Solutions close to it
Frequently asked questions
Do I actually need an app, or is a responsive site enough?
If usage is occasional and the experience needs no camera, location or offline capability, a responsive site is usually cheaper and faster to reach people with. An app earns its cost when usage is frequent, when timely notifications matter, or when device capabilities are central. We ask this in the first session, and if an app is not justified we will say so.
Should I launch on both stores or start with one?
With a shared codebase the difference in cost between one store and two is modest and sits mainly in testing and release, so we usually recommend both. If you are still testing the idea and your early audience is clearly on one platform, starting with a single store is a sound way to narrow the testing surface.
Can you promise the app will be approved by the stores?
No one can — that decision belongs to Apple and Google alone. What we do is review the submission requirements line by line beforehand: permissions, privacy declarations, payment methods and listing content. That is what genuinely reduces the risk of rejection. If a reviewer raises a note, we resolve it and resubmit within the project scope.
Who owns the app, the accounts and the signing keys?
You do. Developer accounts are created in your company name, the repository is yours, and signing keys and certificates are handed over and documented. This is exactly the point at which companies get trapped with a previous supplier, and we do not repeat it.
What happens when the operating systems update?
Mobile platforms change on a regular cadence, which can mean updating dependencies, adapting to new permission behaviour, or meeting a new minimum requirement for publishing. We recommend a maintenance arrangement covering compatibility and security updates. Without one the app keeps working for a while, then the gap widens until an update becomes a project of its own.
Why does the timeline vary so much between projects?
The two biggest factors are whether a back end already exists, and how many exceptions live in the business logic. An app reading from documented, working APIs moves far faster than one built alongside a whole new back end. On top of that sits store review time, which is outside our control and which we allow margin for in the schedule.