Installing PMA and using mobile, offline sync, camera, QR, and notifications
Install the PMA PWA (Progressive Web App), understand cached and queued work, recognize when data is live, synchronizing, or failed, resolve synchronization problems, control personal notifications, and understand camera, QR, Capture, and Android-wrapper readiness.
Before you begin
- Open PMA over HTTPS in a current browser on the device you intend to use.
- Sign in to the correct PMA organization before testing synchronization or notifications.
- Allow camera or notification access only when the related PMA workflow needs it.
- Use the current PMA version provided by the official app so browser and notification behavior matches the supported release.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
Review installation state, service-worker control, camera and QR capability, synchronization status, the mobile audit, and Android-wrapper readiness from one screen.
PMA reports the actual device state and links to Sync Centre. A queued item remains protected locally; a failed item requires review before retry or discard.
Choose which eligible browser alerts appear for you. These settings do not grant record access or change team responsibility.
Use the visible capability checks and fallback routes rather than assuming a device supports every browser feature.
Step-by-step workflow
Install PMA
Open Settings → Mobile, PWA & notifications. Use Install PMA when the browser exposes it. On iPhone or iPad, use Safari’s Share menu and choose Add to Home Screen. Open PMA from its current green PMA icon after installation.
Confirm the application shell
Verify the Control Centre reports an installed application or supported browser, service-worker support, and the expected camera and QR capability. A supported service worker does not mean every workflow can write offline.
Read the synchronization state before working
Live uses current cloud data. Cached shows the last protected device copy. Queued means a local change is waiting. Synchronizing means PMA is sending queued changes in order. Failed means Sync Centre needs review.
Configure personal alerts
Open Settings → Notifications. Enable browser notifications, grant browser permission, and select due-work, assignment, acknowledgement, critical-message, health, overdue, and security categories. Browser notifications work while PMA is running; notifications after the application is fully closed are not currently supported.
Test camera and QR safely
Open QR & Camera from the Control Centre. PMA must be running in a secure context and the browser must expose the camera API. When native barcode detection is unavailable, use the image or manual-code fallback.
Use Capture with explicit state
Before submitting, confirm whether the Capture item will send immediately or enter the protected offline queue. Keep attachments and evidence associated with the draft, then review any failure in Sync Centre instead of recreating the work blindly.
Review wrapper readiness
PMA's Progressive Web App provides the mobile foundation for a possible future Android wrapper. PMA does not currently ship an APK, signing key, Play Store listing, native push provider, background service, or device-administration capability.
Expected result
PMA is installed or clearly usable in the browser, the current green PMA identity appears across application assets, offline and synchronization states are understandable, personal notifications match your responsibilities, and camera, QR, and Capture workflows have visible fallbacks.
Safety boundaries
- Do not interpret an installed PWA as proof that every screen works offline.
- Do not discard failed queued work until its evidence and error are reviewed.
- Notification preferences never grant organization permissions or accept an assignment.
- Browser notifications may not arrive after the application is fully closed; closed-app native push is not currently supported.
- Camera and QR output must still be reviewed before an operational record is created.
- The Android assessment is not an APK release or store-readiness certification.
Troubleshooting
The Install button is missing
The browser may require installation through its menu, PMA may already be installed, or the device may not expose the install event. Use the platform instructions in the Control Centre.
PMA says work is queued
Open Sync Centre. Keep the device signed in to the same organization and reconnect. PMA will attempt eligible items in order and preserve exact failures for review.
Notifications are enabled but nothing appears
Confirm browser permission is Allowed, the master browser-notification switch is on, the category is enabled, the current user is eligible for the notification, and the application is open enough for browser delivery.
The camera cannot start
Use HTTPS, review browser camera permission, close another application using the camera, or use PMA’s image/manual fallback. Device and browser support vary.