Mobile apps
An app your customers and field teams use every day, linked to your system
For companies that need an app where their customers place and track orders, or an app where their technicians and sales reps record their work from the field.
01
Problems we solve
Our sales reps write orders on paper and send photos of them over WhatsApp.
Our technicians work at sites with weak connectivity, so their data is delayed or lost.
Our customers call to ask about the status of their orders, because they cannot see it.
We have a business system, but its data does not reach the people who work outside the office.
02
What the service includes
- F.01
Apps for customers
Placing and tracking orders, notifications, and transaction history, with a clear Arabic interface on iOS and Android.
- F.02
Apps for field teams
The day’s tasks, visits, photos, signatures, and cash collection records from the work site.
- F.03
Working offline
The app saves data on the device when the connection drops and syncs it with the system when the connection returns.
- F.04
Connecting to your system
The app reads from and writes to your business system through an API, so the data is not re-entered at the office.
- F.05
Notifications
Notifications when an order’s status changes or a new task is assigned; your team sets their text and when they are sent.
- F.06
Publishing to the app stores
We prepare the app for publishing on the App Store and Google Play and follow up on its review until it is available for download.
03
How it runs
We identify the users and their tasks
We shadow the real users, whether customers or technicians, and identify the tasks they carry out on their phones.
We design the screens
We design the screen flow in your users’ language, with right-to-left Arabic when needed, and test it with real users before development starts.
We develop in stages
We deliver test releases that are installed on your team’s devices, so your team can review them in real working conditions.
We publish and follow up
We publish the app to the stores and address bugs and user feedback in the next releases.
04
What it looks like in practice
Illustrative example
A maintenance company’s technicians receive their tasks by phone and record what they have done on paper sheets that are handed in at the end of the day. We build an app in which technicians receive their tasks, record the parts used and the cash collected, and take photos at the work site, even without a connection. The data reaches the system when the connection returns, so management sees the status of every task without waiting for the paperwork.
05
What we need from you to start
- A description of the users and their daily tasks
- Access to your current system, or a description of its data
- Developer accounts on the App Store and Google Play in your company’s name
06
Support and development after launch
Our work does not end when we hand over the system: we keep track of its day-to-day operation and develop it as your business grows.
- A post-launch support period to fix bugs and monitor stability, as set out in the contract.
- Keeping track of performance, backups, and security updates.
- Regular review sessions to rank improvements and the next modules by your priorities.
- Training for new users when the team grows or branches are added.
07
Common questions
Technologies we work with
- Flutter
- Kotlin
- Swift
- SQLite
Do we need separate apps for iOS and Android?
Not necessarily. Both apps can be built from a single codebase, and we choose native development for each platform when the app’s features require it.
Does the app work without internet access?
We design the features used in the field to work offline when your work requires it, and the data syncs automatically when the connection returns.
Does the app connect to our current system?
Yes, if the system allows it through an API or an accessible database. If it doesn’t, we build an intermediate layer to connect the two.
Who publishes the app to the stores?
We handle preparing and publishing the app and following up on its review, under developer accounts in your company’s name, so the app stays registered in your name.
08
Related work and articles
One app for Android and iOS: when Flutter is the right choice
You need an app that runs on Android and iOS, and you do not want to build the same app twice and maintain it twice. We explain what one codebase for both platforms means for cost and maintenance, when Flutter suits your case, and when a native app is the better fit.
Systems that keep working when the internet drops: why it matters in our markets
When your system stops because the connection drops, sales stop with it, and transactions pile up on paper. We explain what it means for a system to work offline, and how sync, conflicts, and document numbering are set up before development.
09
Related services
All services- S.08
Backend services and microservices
APIs that connect your systems to each other, and backend services that keep up as your business grows, with an architecture sized to your needs.
- Map of the systems and the data flows between them
- Documented APIs
- Connection and integration services
- S.03
Custom ERP systems
A custom ERP system built around your procedures and business rules, implemented module by module according to your priorities.
- Module map and numbered business rules
- Custom ERP system delivered module by module
- Permissions and roles matrix
- S.04
SaaS platforms
We build your platform to serve multiple customers by subscription, each with a separate account and isolated data.
- Multi-tenant SaaS platform
- Subscription and billing system
- Platform admin panel
Let’s start with how you work
Describe your processes and the problem you want to solve, and we will define a clear first step with you.