Marketplace
sampleExample — three-sided delivery platform
Replace with a real app: the operational problem, what you shipped, and what changed for the business. Add store badges and two screenshots.
—Installs
—Orders / month
—Crash-free rate
Mobile applications · iOS & Android
An app your customers keep,
An app your customers keep,
and an engineer you can reach.
iOS and Android from one codebase, or fully native when the product earns it. Modern backend, admin dashboard, Moroccan payment gateways, store submission handled, Arabic right-to-left done properly. From 48 000 MAD — and we publish that number instead of asking for your budget first.
You own the code and the store accounts
AR / FR / EN including RTL
Moroccan contract and jurisdiction
Scope
The apps we're asked for most
Nearly every one of these is really two products: the app your customer sees, and the dashboard your team runs it from. We build both — the second one is where projects quietly fail when it's an afterthought.
◧
Marketplace & delivery
Catalogue, cart, live order tracking, driver app, dispatch dashboard, commission logic and payouts.
⊕
Booking & services
Clinics, salons, transport, tourism, rentals. Availability, deposits, reminders, cancellation rules and no-show handling.
▦
Loyalty & retail
Cards, points, tiers, push campaigns, in-store scanning, and the analytics that tell you whether any of it worked.
⎕
Field & operations apps
Technicians, inspectors, drivers and agents. Offline-first with sync, photo capture, GPS stamping and signatures.
⊜
Fintech & wallets
KYC flows, transaction ledgers, statements, strong authentication and the audit trail a regulator will ask for.
⊞
Internal enterprise apps
Approvals, stock counts, site reports, HR requests. Private distribution, no public store listing needed.
The first real decision
Cross-platform or native? Here's how we actually choose
Studios tend to recommend whichever one they're staffed for. We do both, so the recommendation can follow your product instead of our hiring. This is the table we work through with you in the Blueprint.
| React Native / Expo | Flutter | Fully native (Swift + Kotlin) | |
|---|---|---|---|
| Relative build cost | One codebase — lowest | One codebase — lowest | Roughly 1.7–2× |
| Time to both stores | Fastest | Fast | Two parallel tracks |
| Feels native to the user | Yes, with care | Yes, own render engine | Perfect by definition |
| Heavy graphics / AR / video editing | Possible with native modules | Good | The right answer |
| Deep OS integration (widgets, CarPlay, Watch) | Partial | Partial | Full |
| Hiring a maintainer in Morocco later | Easiest — shares JS/TS talent pool | Growing pool | Smallest, most expensive |
| Shares code with your website | Yes — same language and logic | No | No |
| We recommend it when | Most business apps, marketplaces, booking, loyalty, field tools | Design-led apps with heavy custom animation | Games, AR, media processing, or a hardware-bound product |
↳
Our default is React Native with Expo — not because it's trendy, but because it shares a language and often real code with your web backend, and because you'll be able to hire someone in Casablanca to maintain it in three years. If your product needs native, we'll say so in the Blueprint and quote it honestly, including the higher cost.
Who you hire matters
The cheapest quote is a bet on nothing going wrong
Apps take months, not days. Over that stretch the thing that decides the outcome isn't the hourly rate — it's whether you can get someone accountable on the phone when the store rejects your build two days before a campaign launches.
| Recode | Offshore agency | Freelance marketplace | No-code app builder | |
|---|---|---|---|---|
| Day rate | Mid | Low | Lowest | Subscription |
| Timezone overlap | Same day, same hours | 4–8 hour lag | Whenever they reply | Help centre |
| Language on calls | Arabic, French, English | English, variable | Variable | Documentation only |
| If it goes wrong | Moroccan contract, Moroccan courts | Foreign jurisdiction | Platform mediation at best | Terms of service |
| Who owns the code | You, with full Git history | Check the contract carefully | Often unclear | The platform |
| Where your user data sits | Morocco, CNDP-declarable | Wherever they chose | Unknown | Foreign servers |
| Store accounts | Yours, in your company name | Sometimes theirs | Often theirs | Theirs |
| Continuity if they vanish | Documented, handover-ready | Depends | You start again | App stops working |
This is a comparison of categories, not of specific companies. There are excellent offshore teams and competent freelancers — the point is that the structural risks above are real and you should price them in rather than discover them.
Always included
Things other quotes charge extra for
The gap between a 48 000 MAD app and a 20 000 MAD app is usually not features. It's everything on this list, which the cheaper quote leaves out and bills you for later.
Admin dashboard
A web back office to manage users, content, orders and settings. An app without one is unusable by a real team.
Store submission
App Store and Google Play listings, screenshots, privacy declarations, review responses — under your own developer accounts.
Push notifications
Infrastructure plus a dashboard to segment and send, because the whole point of an app is that you can reach people again.
Arabic & RTL
Right-to-left layout, Arabic typography and number formatting built in from the start, not bolted on and broken.
Crash & analytics
Crash reporting and product analytics configured, so you know what breaks and where people drop off.
Offline handling
Moroccan mobile coverage is not uniform. Apps that assume a perfect connection get uninstalled.
Security review
Secure storage, certificate pinning where warranted, no secrets in the bundle, authenticated API by default.
Handover pack
Repository, build pipeline, signing keys, environment docs. Everything needed for someone else to continue.
Timeline
What three to five months actually looks like
Dates come from the Blueprint, not from this page. But this is the honest shape of a two-platform app with a backend, and the two places schedules usually slip are marked.
00
Free consultation
We pressure-test the idea, the business model and the smallest version worth shipping. You don't need a specification to book this.
01
Blueprint
Screen inventory, user flows, data model, platform decision, integration list and a fixed build quote. Yours to keep even if you stop here.
02
UI / UX design
Every screen designed and assembled into a clickable prototype you can hand to a real customer before anything is built.
03
Build — app, backend, dashboard
Two-week sprints with an installable test build each time. Start bank and gateway paperwork now — it is the single most common cause of delay.
04
Testing on real devices
Physical Android and iOS handsets across screen sizes and OS versions, on mobile data as well as wifi. Not just a simulator.
05
Store review & launch
Submission, review responses, phased rollout. Apple review is outside anyone's control — we plan for a rejection round rather than pretending it won't happen.
06
Run
Monitoring, OS-version updates, store policy changes, and iteration based on what users actually do. Optional, and cancellable.
App pricing
Three entry points, published
Every tier includes both platforms, the backend, the admin dashboard and store submission. Design-only engagements start at 12 000 MAD if you already have a development team.
MVP
Prove the idea with real users before spending more
from
48 000MAD
- iOS + Android, one codebase
- Up to ~12 screens
- Backend and API included
- Basic admin dashboard
- Accounts and authentication
- Push notifications
- Store submission, both stores
- Payments quoted separately
most chosen
Business app
A product you'll run commercially and grow
from
115 000MAD
- Everything in MVP
- Full custom UI / UX design
- CMI, Payzone, Stripe or PayPal
- Full admin with roles and reporting
- Arabic, French, English with RTL
- Offline mode and sync
- Crash reporting and analytics
- 3 months support included
Platform
Multi-sided, regulated, or operationally critical
from
240 000MAD
- Everything in Business app
- Multiple apps (customer, driver, partner)
- Native modules where required
- ERP / CRM / third-party integrations
- Real-time tracking and messaging
- Load testing and staging environment
- Security review and audit trail
- Dedicated team, 6 months support
Selected work
App case studies
Layout is final; the two entries are illustrative placeholders — replace with real apps, screenshots and store links before launch.
Field operations
sampleExample — offline-first inspection app
Replace with a real app. Internal tools make excellent case studies because the ROI is measurable in hours saved.
—Field users
—Hours saved / week
—Paper eliminated
App questions
What clients ask before they commit
Yes, and that's the normal case. Writing a requirements document is a skill, and expecting a founder or a director to produce one before anybody will talk to them is a way of pushing the hardest part of the work onto the person least equipped to do it. Bring the problem, the constraint and the deadline. The Blueprint is where it becomes a specification — and you own that document whether or not we build it.
Nobody can promise that, and a studio that does is either inexperienced or lying. What we can do is build to the guidelines, handle the privacy declarations and data-use disclosures properly, avoid the patterns that trigger rejection, and plan a review round into the schedule. If a rejection comes, we handle the response and resubmission as part of the project rather than as a change request. Apps that take payment for digital goods must use Apple's in-app purchase and its commission — we'll flag that early because it changes business models.
You do. The Apple Developer and Google Play accounts are registered in your company's name with your billing details, and we're added as collaborators. Signing keys and certificates are handed over in the launch pack. This matters more than it sounds: when the accounts belong to the agency, you cannot publish an update without them, which is how businesses end up hostage to a studio they've outgrown.
Budget realistically for 15–25% of the build cost per year. That isn't a maintenance tax — Apple and Google change requirements, OS versions ship annually and deprecate APIs, libraries get security patches, and an app left untouched for two years will eventually stop being installable. Plans start from 1 200 MAD/month for monitoring and updates. You can also take the repository and handle it in-house; we'll document it for exactly that.
Usually yes, and the question is what the system exposes. A documented REST API is straightforward. SOAP, a direct database connection, or a nightly CSV over FTP are all workable and we've no snobbery about it. If there's genuinely no way in, we'll say so during the Blueprint rather than discovering it in month three — this is exactly the kind of risk the Blueprint exists to surface before you've committed a build budget.
You need somewhere a stranger can verify you exist, and both stores require a privacy policy at a public URL. Beyond that it depends: if discovery happens through search, the web matters more than the app; if it happens through your existing customer base, the app can lead. Because we build both and often share code and backend between them, doing the two together costs meaningfully less than two separate projects — we'll put both options in the Blueprint with real numbers.
We handle the technical side of discoverability — store listing optimisation, keyword and screenshot work, deep links, attribution tracking so you can tell which channel actually delivered a user. We are not a media buying agency and won't pretend to be. If you need paid acquisition we'll tell you what to instrument before you spend, which is the part agencies usually skip.
Next step
One call. Then a document you own,
One call. Then a document you own,
whether you build with us or not.
Bring the idea in whatever state it's in. You'll leave the call knowing roughly what it costs, roughly how long it takes, and what the smallest worthwhile first version looks like.