APPS & MARKETPLACES
The apps that sit on top of your ERP.
Your ERP is the system of record. It’s rarely the right interface for a customer, a driver or a technician in the field. We build the apps that are, and keep them in sync with the platform underneath.
WHAT WE BUILD
Interfaces for the people outside the office.
Every app talks to your ERP through a documented API layer we build and maintain.
Customer portals
Order history, invoices, statements, support tickets and payment — on your domain, in your brand, in Arabic and English.
- Self-service invoices & statements
- Online payment
- Bilingual by default
Field and driver apps
Offline-capable mobile apps for technicians, delivery drivers and inspectors that sync back to the ERP when signal returns.
- Offline-first sync
- Photo & signature capture
- Route and task assignment
Marketplace publishing
We handle App Store and Play Store submission, review responses, release notes and the ongoing compliance updates each platform demands.
- iOS and Android release
- Store listing in AR & EN
- Ongoing policy compliance
API layer
A documented, versioned API between your ERP and everything that talks to it — including systems we didn’t build.
- Versioned REST endpoints
- Auth and rate limiting
- OpenAPI documentation
Maintained, not abandoned
Apps break when the OS updates and when the ERP upgrades. Ours are on the same support contract as the platform.
- OS version tracking
- Crash reporting
- Covered by the same SLA
SPECIFICS
The things people ask on the second call.
- Mobile stack
- React Native — one codebase, both stores
- Web stack
- Next.js, server-rendered, bilingual
- Backend
- Your Frappe or Odoo instance, via a versioned API
- Store accounts
- Yours — we publish under your developer account
- Code ownership
- Yours. Delivered to your repository.
- Typical timeline
- 8–14 weeks for a first release
PROCESS
From idea to a listing.
Store review adds a week or two at the end that nobody ever plans for. We plan for it.
- 01
Define
Who uses it, what they do in it, and what the ERP has to expose for that to work.
- 02
Design
Screens and flows in your brand, reviewed before a line of app code is written.
- 03
Build
App and API in parallel, with builds you can install on a real device each sprint.
- 04
Publish
Store submission, review handling, release notes, and the first update cycle.
QUESTIONS
Before you ask us.
Yes, in your company’s name — Apple and Google both require the publisher to be the business. We’ll walk you through creating it and publish under it.
It happens, usually over metadata or a permission description. Handling review responses is part of the engagement, not an extra invoice.
For field and driver apps, yes — we build offline-first with a sync queue. For portals it’s rarely worth the complexity, and we’ll tell you when it isn’t.
Yes, provided the ERP can expose a usable API. If it can’t, building that layer becomes part of the scope.
Who needs access to your ERP but shouldn’t be logging into it?
That’s usually where the first app comes from.