Progressive web apps by default
Installable from a browser, works on any handset, updates itself, no app-store review holding up a fix. For most business apps this is simply the better answer, and dramatically cheaper to maintain.
The mobile projects that fail are the ones with no job to do. Somebody decides the company needs an app, it gets built, it shows a menu of things that were fine on the website, and within a year nobody opens it.
The ones that work remove a phone call. Staff check in without ringing the office. A supervisor approves a leave request from a site. A driver closes off a delivery. A customer checks an order without emailing anyone. That is what we build — and it works because the app is connected to the system that holds the real data.
WHAT WE DO
What this covers
Native when it is genuinely needed
Deep hardware access, background location, offline-heavy field work. We will tell you when you need it — and when you do not.
Connected to your ERP
Not a separate database that syncs. The app reads and writes the same records as your ERPNext or Frappe system, so there is no reconciliation and no lag.
Staff apps
Attendance and check-in, leave, payslips, expense claims, advances, approvals, notifications. The workload this takes off an HR office is the usual reason to start.
Field and operations apps
Job cards, delivery confirmation, inspections with photographs, signature capture, barcode and QR scanning.
Customer apps and portals
Order status, invoices and statements, requests and support tickets — reducing the calls that interrupt your team all day.
QUESTIONS
Frequently asked questions
-
Progressive web app or native — which do we need?
Most business apps should be progressive web apps: one codebase, installable from a link, no store approvals, instant updates. Go native when you need deep hardware integration, sustained background location, or heavy offline operation. We will give you a straight recommendation rather than the more expensive one.
-
Does it work offline?
Partially, and it is worth being precise. A progressive web app can cache screens and data for viewing offline. Recording transactions offline and syncing later is a genuinely harder problem that needs designing in deliberately and testing hard — it is doable, it is not free, and we would rather scope it properly than promise it casually.
-
Can it connect to our existing system?
If your system has an API, generally yes. If it is ERPNext or Frappe, certainly — every module exposes REST endpoints, which is why those projects go quickly.
-
Do you publish to the App Store and Play Store?
For native builds, yes, and we handle the submission. Progressive web apps skip stores entirely — staff install from a link, which also means an urgent fix reaches them in minutes rather than after review.
-
How long does a staff app take?
A focused staff app on an existing ERPNext backend is usually four to eight weeks. A customer-facing app with its own design language and offline requirements takes longer, and we will say so at scoping rather than later.
-
Who owns the code?
You do. Source code is handed over and the repository is yours.
KEEP READING
Related
API development & integration
Connecting ERPNext to banks, gateways, portals and the software you already run.
Website development
Search-optimised business sites, optionally on the same platform as your ERP.
CareOps nursing platform
Booking, rostering, reliever cover, attendance and invoicing for nursing services.
ERPNext implementation in Qatar
What we do, how a project runs, and what it costs to move a Qatar business onto ERPNext.
GET STARTED
Start with the phone call you want to stop receiving
Tell us which routine request eats your team's day. That is usually the right first app, and it is usually smaller than you expect.