Keep the browser as the main workspace for the calendar, front desk, settings, reporting, and longer sessions.
One platform, the right surface for each role
Business in the browser, on mobile, and where needed on Desktop
Most teams manage the main work in the browser, use mobile for quick checks and QR scanning, and keep Desktop only for roles with a real local need.
Why this matters
Browser first. Mobile for speed. Desktop where local work still matters.
Teams do not need every app everywhere. What matters is that reception, specialists, and managers know which device fits their work and when Desktop really belongs.
Use the mobile app for notifications, quick schedule checks, quick client checks, short actions, and QR scanning away from the desk.
Bring in Desktop only where local devices, fixed workstations, or more specialized workflows really need it.
How this should work
Keep the main work in the browser and add other apps only where they help
The strongest setup does not spread the team across unnecessary installs. It keeps the full workflow in the browser, gives mobile the quick jobs it handles best, and limits Desktop to the roles that have a real local requirement.
- Use the browser for the live day when someone needs the calendar, front desk, lists, settings, reports, or any longer workflow.
- Add the mobile app when someone needs notifications, a quick schedule check, a quick client lookup, or QR scanning with the phone camera.
- Use Desktop only when a specific role depends on a fixed workstation, local devices, or a more specialized internal flow.
- Keep installation links and setup guidance in the Help Center and Downloads instead of turning downloads into the main product story.
What this layer includes
Where each surface fits
The point is not to list operating systems. The point is to make it obvious which surface is best for which job.
Browser for the full operating view
This is where most teams keep the calendar, front desk work, lists, settings, reporting, and the longer parts of the workday.
Mobile for quick actions on the move
Mobile is most useful for notifications, fast schedule checks, quick client lookups, short actions, and QR scanning.
Desktop for local or specialized work
Desktop stays useful where a fixed workstation, local devices, or a more specialized internal process still matter.
Help Center and Downloads for setup
When someone needs current installation links or setup guidance, the Help Center remains the right place to get them.
What improves
A clearer rollout and fewer wrong setup choices
The team can decide faster who should stay in the browser, who benefits from mobile, and where Desktop really belongs.
A clearer role for the browser
Core work stays in the most universal surface instead of being fragmented across unnecessary installs.
More useful mobile adoption
Mobile is introduced where it actually saves time instead of being treated as a replacement for every longer task.
A cleaner setup for the team
From the start it becomes clearer who works in the browser, who needs mobile, and where Desktop really makes sense.
FAQ
What teams usually ask about access
Does every business need Desktop?
No. The core model is browser-first. Desktop only makes sense when a specific local or more specialized workflow truly requires it.
Does the mobile app replace the browser?
No. It is most useful for quick checks, notifications, and QR work, while longer work, lists, and reporting usually stay in the browser.
Where do the current installation links come from?
Desktop download links live in the Help Center and its Downloads section. Mobile apps are available through Google Play, the App Store, and AppGallery.
When does mobile create the most value?
When someone is away from the desk and needs to review the schedule, check a client, react to a notification, or scan a QR code with the phone camera.