Progressive Web App (PWA) Delivery Method

The Progressive Web App (PWA) delivery method lets learners install eduMe on their phone's home screen directly from the Knowledge Hub - no app store required - and receive push notifications about their training. It gives frontline workers an app-like experience and a proactive, push-based delivery channel that doesn't rely on SMS, email, or a workforce management integration.

What's covered in this article?

Why use PWA delivery?
How it works
Enabling PWA notifications
Installing the app (learner experience)
Push notifications
Staying logged in
Platform differences: iOS vs Android
Limitations & troubleshooting

Why use PWA delivery?

📲 App-like experience, no app store – Learners add eduMe to their home screen straight from the browser, giving one-tap access to their Knowledge Hub.

🔔 Push-based delivery – Training assignments and reminders are pushed to the learner's device, rather than relying on learners to remember to check a portal (pull-based access).

✅ Consent-friendly – Learners opt in to notifications themselves on their own device, which suits organisations where SMS is treated as a personal channel requiring explicit consent.

🤝 Complementary channel – PWA push notifications are sent alongside any other delivery methods enabled for the learner (e.g. SMS, Email, WhatsApp).

How it works

The Enable PWA notifications setting is turned on for the customer (found under the Notifications section in the admin dashboard).
A learner opens their Knowledge Hub in a mobile browser and sees an Install app callout.
The learner installs the eduMe PWA to their home screen using the callout's Install button.
On opening the installed app, the learner is invited to enable push notifications.
Once enabled, content notifications are delivered as native push notifications on the learner's device. Tapping a notification opens the relevant content directly in the app.

Enabling PWA notifications

Web push notifications are enabled at customer level using the Enable PWA notifications setting under the Notifications section.

Installing the app (learner experience)

Learners should always install using the Install app button in the callout shown in the Knowledge Hub, then follow the on-screen instructions — rather than using the browser's own "Add to Home Screen" option from elsewhere in the app.

This matters because the PWA's start page is inherited from the page it was installed from. The Install button forces a page reload so the installed app reliably opens on the Knowledge Hub, not a login page or another screen the learner happened to be on.

💡 If a customer has multiple Knowledge Hubs, the installed app opens the Knowledge Hub it was installed from.

Android (Chrome) — step by step

Based on the Android install demo video, the learner journey looks like this:

Log in – The learner opens their Knowledge Hub link in Chrome and signs in with their email address or phone number, then taps Continue.
Install callout – On the learning dashboard, a callout appears at the top: "Install this app for the best experience – Get notified about new content, and easily find important information", with Maybe later and Install app options.
Tap Install app – The page reloads (this ensures the app opens on the dashboard after install) and a "How to install" panel appears with four steps:
- Step 1 – Tap the menu button in your browser
- Step 2 – Choose "Add to home screen"
- Step 3 – Save the shortcut
- Step 4 – Find all your content in the eduMe app
The panel also links to full instructions on the Help Center ("Don't see these options? → See full instructions").
Complete the install in Chrome – The learner taps Chrome's menu (⋮) → Add to home screen → Install, then confirms in Chrome's Install app dialog and adds the icon to the home screen.
Open the app – The eduMe icon now appears on the home screen. Opening it shows an eduMe splash screen and lands the learner on My learning dashboard, still logged in — the Android PWA shares the browser session, so no re-login is needed.

iOS (Safari)

There is no automatic install prompt; learners follow the instructions in the install callout, which guide them through adding eduMe to the home screen via the Share menu → Add to Home Screen.
Login is carried over from the browser to the app automatically using a short-lived, single-use transfer code generated when the learner taps Install (see Platform differences below).

Push notifications

Enabling

When the learner first opens the installed app, a callout invites them to enable push notifications: "Make sure you don't miss out on new content", with No thanks and Enable notifications options.
Tapping Enable notifications triggers the operating system's permission popup (e.g. "eduMe wants to send you notifications" on Android), where the learner chooses Allow or Block (Don't allow on iOS).

If the learner declines

The system popup can only be shown once. If a learner taps Don't allow, notifications can only be enabled afterwards via the device's App Settings (iOS or Android) — there is no way to re-trigger the prompt from within the eduMe app.
Alternatively, uninstalling and reinstalling the app will show the enable-notifications prompt again.

Delivery behaviour

Push notifications are sent to every learner who has installed the PWA and allowed notifications, in addition to any other enabled channels (SMS, Email, WhatsApp).
Tapping a notification opens the relevant content as a direct link within the app.
The notification icon currently defaults to the eduMe logo and cannot be customised.

Staying logged in

The PWA uses a refresh token system so learners stay logged in without repeated logins:

As long as a learner opens the app at least once every 30 days, their session is refreshed and they can stay logged in indefinitely.
If a learner doesn't use the app for more than 30 days, their session expires and they'll need to log in again. Learners without their own username/password (e.g. seamless learners) would need to uninstall and reinstall the app from the Knowledge Hub to restore access.

Platform differences: iOS vs Android

Android

The PWA shares the browser session, so no extra steps are needed to stay logged in after installing from Chrome.
⚠️ Because the session is shared: if the learner logs out in the browser, they are logged out of the app too. Learners with credentials can simply log back in; learners without credentials must uninstall and reinstall the app.

iOS

PWAs on iOS are sandboxed and don't share data with the browser. eduMe bridges this with a short-lived (single-use) transfer token created when the learner taps the Install button, which logs the app in automatically on first open.
⚠️ If an iOS learner is ever logged out of the app, the original transfer token can't be reused — they'll see a login page. Learners without credentials must uninstall and reinstall the app.

Limitations & troubleshooting

Learner declined notifications but callout persists / wants to re-enable → Enable notifications via the device's App Settings, or uninstall and reinstall the app.
App opens on a login page instead of the Knowledge Hub → The app was likely installed via the browser menu rather than the Install callout. Uninstall and reinstall using the Install app button in the callout.
Learner logged out and can't get back in (no credentials) → Uninstall and reinstall the app from the Knowledge Hub.
Notifications still "sent" to uninstalled devices → Devices are unregistered on logout, but eduMe cannot detect a learner uninstalling the app without logging out, or disabling notifications at OS level. Notifications may continue to be sent to devices that won't receive them; this does not affect other delivery channels.
Knowledge Hub opened inside another app (e.g. Slack webview) → In rare cases a webview can be mis-detected as a PWA, showing the notifications callout instead of the install callout. A fix has been applied for known cases (e.g. Slack on Android); report any new occurrences to Support.
Notification image → Not customisable; defaults to the eduMe logo.