A bottom tab bar for the four things that matter
Home, My Day, Orders and Checks sit within thumb reach. The full module list is behind the menu, where it belongs on a small screen.
iOS · Android · Browser
The workspace, in a hi-vis pocket
Maintenance is recorded at the equipment or it is recorded from memory. RampWorks ships the same workspace as a responsive web app and as native iOS and Android builds, from one codebase.
Same records, same rules, smaller screen
The mobile builds are Capacitor wrappers around the identical Quasar client the browser runs. There is no reduced mobile feature set to discover the hard way, and no second database to fall out of step.
- Every module your role grants is available on the phone
- Role, station and provider scope apply identically
- Excel and PDF exports work from the device
- One release ships web, iOS and Android together
Designed for the apron
What changes on a device
Touch targets sized for gloves
Controls, rows and form fields are enlarged on mobile rather than shrunk, and input font sizes are set so iOS does not zoom the page when a field is focused.
Lists become cards
Where a desktop shows a dense table, the phone shows a card per record with the work-order number, asset, station, status and due date — readable at a glance in daylight.
Signature capture on the glass
Completion consent and technician signatures are captured directly on the device at the equipment, not back at a desk on a printed form.
Getting it on your phone
Ask your administrator which build you are on
Organisations run RampWorks either in the browser or as a distributed native build. Both are the same application; only the delivery differs.
Browser: add it to the home screen
Open your workspace address in Safari or Chrome and use Add to Home Screen. It launches full-screen and behaves like an installed app, with nothing to update.
Native: install through your organisation's channel
iOS and Android builds are distributed by your organisation, through internal testing or managed distribution. You will be sent an invitation rather than finding it by searching a store.
Sign in once
The session persists between launches, so the sign-in is a first-run step rather than a daily one. Sign out from the account menu when handing a shared device on.
Which should we use?
| Browser | Native build | |
|---|---|---|
| Rollout effort | Send a link | Managed distribution per device |
| Updates | Automatic on next load | Distributed as a new build |
| Home-screen launch | Add to Home Screen | Installed app icon |
| Feature set | Complete | Complete |
| Best for | Getting started, occasional users, desktops | Daily ramp use on organisation-managed devices |
Most operations start in the browser and move daily ramp users onto the native build once the workspace is settled.
Rolling RampWorks out to a ramp team?
We can walk through device distribution, shared-device handling and the account setup that goes with it.