// 02 — Services
Mobile app development.
iOS and Android applications, native or cross-platform, built to survive the second year — not just the launch demo.
We build mobile applications end to end: the product decisions, the interface, the backend behind it, and the submission to both stores. Flutter and React Native for most products, native Swift or Kotlin when the product is genuinely device-heavy.
The parts that decide whether a mobile app works are rarely the screens. They are what happens with no signal, how the app behaves when a shift crosses midnight, whether a field worker's check-in survives a dead battery, and how you ship an update without breaking the people still on the old version. We design for those first.
Rakeez, our own HR platform, puts attendance, payroll, leave and documents in an employee's pocket on both iOS and Android, in Arabic, with location-stamped check-ins from the field. Quick App coordinates customers, vendors and riders across five delivery categories in two languages.
Common questions.
- Native or cross-platform — which should we choose?
- Cross-platform is the reasonable default for most business applications: one codebase, one bug fixed once, both platforms shipping together. Native earns its extra cost when the product is genuinely device-heavy — sustained background location, real-time camera processing, Bluetooth peripherals — or when you have separate iOS and Android teams to maintain it.
- Do you handle App Store and Google Play submission?
- Yes. Store review is part of getting an app live, rejections included, and we scope it in from the start rather than treating it as someone else’s problem at the end. What is and isn’t included in a given engagement is written into that engagement’s scope.
- Can the app work in Arabic?
- Yes, and it is decided at the start rather than retrofitted. Right-to-left layout, bidirectional text, Arabic typography and date and number formats are architectural decisions — cheap in week one, close to an interface rebuild afterwards.
- What happens after launch?
- Every project ends with your team able to maintain it — documented, typed, and handed over properly. If you want us to stay involved after launch, that is worth agreeing before launch rather than discovering afterwards; talk to us about it while the scope is being written.
