Walk into any gym at eight in the evening and look at the front-desk screen: the management system is open in a browser tab among fifteen others, next to an email, an electricity bill and a YouTube video. The next shift closes it by accident, and the hunt begins — first for the link in the history, then for the password. None of that is a software fault, but it is five minutes lost every day and a queue at the door in the busiest hour.
The fix is in the browser itself: the gym system can be installed on a device as an app, with an icon on the home screen, opening in its own window with no address bar and no tabs. No app store, no developer account, no week-long review, no fee. The technology is called a progressive web app (PWA), and it is what runs both the ArabGym dashboard and the member portal — and this article is about using it on the gym’s own devices rather than on members’ phones.
What installing actually changes
A point of precision first: the installed app is the same app that was in the tab, not a second product with extra features. What changes is the frame around it — a smaller change on paper than it sounds, and a larger one in a busy trading day:
- An icon on the home screen instead of a link in the history — and a new employee finds it without being told how.
- A standalone window with no tabs and no address bar, so the system is not closed by accident or typed over.
- Shortcuts inside the icon itself: a long press on the dashboard icon opens check-in, add member, or reports directly — and those three are 90% of what a front desk does.
- A faster open on return visits, because the static interface files stay cached on the device.
- A branded screen when the network drops instead of the browser’s error page — which gets its own section below, because what it does and what it does not do both matter.
And because the app is a web page underneath, everything that worked in the browser works after installing: the QR reader uses the device camera (grant the permission once on that device), invoices print, and the same login carries the same staff permissions.
Which device gets what
The common mistake is installing everything on every device. Each device should open on the screen its user actually needs, logged in as that person rather than as the owner:
| Device | Who uses it | What goes on it | The rule |
|---|---|---|---|
| Front-desk tablet | Shift staff | The dashboard, with the check-in shortcut to hand | An account per employee rather than one shared login, and a short screen lock |
| Owner or manager phone | Owner, manager | The dashboard, opening on reports | The only personal device that should be seeing revenue figures |
| Coach’s phone | Coaches | The dashboard with coach permissions | Sees their classes and members, not the money — the permission decides, not the device |
| Member’s phone | Members | The member portal: check-in code and class booking | A separate app from the dashboard, installed the same way from the portal link |
| Back-office computer | The accountant | The browser is usually enough | The work here is monthly rather than daily; installing adds nothing to it |
How to install it on each system
The whole thing takes under a minute, and only the first step differs by device. Log in first, then:
- Android and Chrome: an “Install app” banner usually appears; otherwise use the install button in the site bar, or the browser menu → “Install app” / “Add to Home screen”.
- iPhone and iPad (Safari): the Share button → “Add to Home Screen” → “Add”. Safari never shows an automatic install banner, and this manual route is the only one.
- Windows and Mac (Chrome or Edge): the install icon at the end of the address bar, or menu → “Install”. The app then appears in the programs list like any other application.
- From inside the site: an “Install app” button sits in the navigation bar on the public pages, and inside the dashboard an install banner appears on a return visit. Either one opens the native install prompt where the browser supports one, and shows your device’s specific steps where it does not.
What really happens when the internet drops
Here the wording has to be exact, because “works offline” is sold often and means different things. The installed app opens without internet and shows a clear, branded outage screen instead of the browser’s error page. What it does not do — deliberately — is keep your members’ data on the device: no names, no memberships, no figures sitting in the tablet’s storage.
That is a deliberate trade-off rather than a gap. A front-desk tablet is a shared device held by five staff, sometimes lent out and sometimes lost. Any copy of member records stored on it becomes a copy that leaves the gym in somebody’s bag. The system keeps only interface files on the device — fonts, images, program files — and asks the server for member data every time.
So you need a three-step outage plan written on a sheet behind the counter, because the outage will arrive in the peak hour rather than in a quiet afternoon:
- Turn on a phone hotspot immediately — most outages are in the gym’s line rather than the mobile network, and this step alone ends most incidents.
- If it persists: a paper list of name and time at the door, and do not hold members at the counter. Enter it into the system once service returns, dated the same day.
- Payments: defer the recording, not the collection — write a manual receipt with a sequential number and enter it into the system later the same day, so the tax invoicing sequence does not break.
Rules for a device five people hold
Installing changes nothing about security, for better or worse: the same session, the same permissions. What it does change is how easy the system is to reach — and easy reach on a shared device needs three rules:
- An account per employee. A shared login means the action log says “deleted” without saying who — the moment a log stops being worth keeping.
- A short screen lock on the device itself — a minute or two. The installed app opens with one tap, which is what you want for your employee and not what you want for a curious member passing the counter.
- A log-out at the end of the shift on shared devices, and access withdrawn the same day for anyone who leaves — not at the end of the month.
How updates arrive without a store
This is the biggest practical gain from installing through the browser, and nobody notices it until they compare. There is no build waiting on a store review, and no employee running a three-month-old version because they never updated. A fix published today reaches the front-desk tablet on its next open: the app fetches the new version in the background and it takes effect on restart — and in the member portal the member is told a new version is ready and reloads by choice, not by a sudden jump that interrupts what they were doing.
The other side of that coin is worth stating: there are things a web app does not do today, chiefly push notifications to a lock screen. Which is why the system’s alerts — expiry reminders, renewal notices, payment receipts — go out over WhatsApp and email, the channel your members in this region read far more than any app notification anyway.
A practical close: set aside ten minutes on a quiet morning. Install the dashboard on the front-desk tablet and on your own phone, set the screen lock, print the three-step outage plan and stick it behind the counter, and send members the portal link with the install steps in a single message. Those ten minutes end the three most repetitive operational problems a front desk has.