Deployment and devices
There is nothing to deploy
MedJot is a Progressive Web App at https://medjot.app.
- No app store listing, no MDM app package, no installer, no MSI, no IPA.
- No software installation on any device.
- Optionally, users add it to a home screen — a browser function, not an installation.
For most organisations, deployment consists of allow-listing the domain and telling clinicians the URL.
Browser requirements
- A current version of Safari, Chrome, Edge or Firefox.
- iOS / iPadOS 16.4 or later for the full installed-app experience.
- JavaScript enabled; local storage and IndexedDB available.
- WebSocket support for live account state (
wss://*.firebaseio.com).
The storage policy — the one that matters
Local storage must not be cleared automatically.
MedJot keeps in-progress reports in the browser's own storage. A policy that wipes website data on exit, on a schedule, or after inactivity will discard a clinician's unfinished report — potentially mid-shift, with no recovery, because no copy exists anywhere else.
Please check for and exempt medjot.app from:
- "Clear browsing data on exit" policies
- Scheduled or idle-triggered site data clearance
- Kiosk or shared-device profiles that reset between sessions
- Safari's "Remove website data" configuration profiles
Installing MedJot to the home screen also substantially reduces the risk of Safari's Intelligent Tracking Prevention evicting storage from a site left unused for an extended period.
MDM configuration
Typical items in a managed deployment:
| Setting | Recommendation |
|---|---|
| Allow-list | medjot.app and the endpoints in Network requirements |
| TLS inspection | Exempt medjot.app and *.medjot.app. See TLS inspection |
| Website data clearance | Exempt medjot.app |
| Add to Home Screen | Permit, if home-screen installation is otherwise restricted |
| Web notifications | Optional. Blocking is safe |
| Camera | Needed only for QR-based device transfer |
| Web clip | You may push a web clip to https://medjot.app/app if you prefer central distribution |
Shared and pooled devices
MedJot is usable on shared devices, with two things to understand:
- Clinical working data is cleared when a different user signs in, so one clinician's report is not left under another's session.
- Reports are stored locally and are not backed up. On a pooled device, a clinician who does not export before handing the device on has no route back to that report. Export-and-reset should be part of the local workflow.
Personal devices (BYOD)
MedJot works on personal devices, and the local-first architecture means clinical content stays on that device rather than in a supplier's cloud.
The corollary is that a lost or compromised personal device exposes any in-progress report on it, exactly as it would any locally-stored document. That is a device-management question for the organisation, and it is a further reason for the standing instruction that patient-identifiable information should not be entered into MedJot at all.
Offline behaviour on managed networks
MedJot's interface is cached, so it opens without a connection. On a network that blocks it, this produces a characteristic and confusing symptom: the app opens and appears healthy while every network request fails, and the app correctly reports itself offline on a device that looks connected.
If clinicians report "it says offline but my wifi is fine", start at Diagnosing a blocked deployment.
Rollout advice
- Do the network work first. Allow-list and the TLS exemption before anyone is given the URL — a first week of certificate warnings is very hard to recover from with clinical users.
- Test on a genuinely managed device, not an IT laptop outside the standard policy.
- Confirm the certificate issuer is Let's Encrypt on that device.
- Confirm storage survives a browser restart on that device.
- Then roll out, with the quick start and installing pages.
Support
hello@swyftscale.com. Tell us what you are seeing and, where there is a certificate warning, which authority issued the certificate your devices receive.