AT A GLANCE
Mobile plumbing software should let a field user understand the assigned job, review the approved scope and record the next supported action on a phone. Test saving, connection loss and notifications separately. A responsive website does not by itself prove offline support or an installable native app.
An edited note is not always a saved note
Saved to the record
The office can see the confirmed update and its time.
Pending or unavailable
The screen must explain what is safe to do next.
Confirm the result
Check for a missing update, duplicate or conflict.
Start with the field task
Ask the technician to find the correct job, service address, authorized contact and approved scope. Then ask them to record a permitted status change. The task should work without repeatedly zooming, guessing at icon meanings or switching to a desktop view.
Use the actual device types your team carries. A successful desktop demonstration does not establish Android or iPhone usability. Include text enlargement and a slower connection in the exercise.
Distinguish browser access, an installed web app and native apps
| Term | What it establishes | What still needs testing |
|---|---|---|
| Responsive website | The layout adapts to a smaller screen | Touch controls and real field tasks |
| Installed web app | A supported browser-based installation | Update, notification and offline behavior |
| Native app | An identified installable iOS or Android build | Permissions, versions and device acceptance |
| Offline workflow | Specific work supported without connectivity | Local save, sync and conflict handling |
Do not infer offline editing or background notification delivery from an app icon. Ask the vendor to identify the release and demonstrate the capability on a device.
Test connection loss and return
Begin a fictional note or status update, interrupt the connection and inspect the screen. It should make clear whether the change is saved, pending or unavailable. Reconnect and verify the final record from the office view. Check for a duplicate or a lost update.
The right fallback depends on the actual product. If offline work is not supported, the business needs an agreed process for that situation. Avoid relying on a screen that only appears to have saved.
Check notifications independently
Try the required notification scenarios with the browser open, the screen locked and permissions disabled. A visible alert while a page is open does not prove background or native push delivery. Record the device, build and result so the acceptance evidence is reproducible.
For teams in the United States, include the relevant time zone in proposed visit times. Check that addresses, ZIP code fields and amounts in USD remain readable on the phone.
Know the current Flor boundary
Flor Plumbing has a web workspace and public demo. Native-device notification delivery, installable mobile app availability and offline editing must be confirmed separately; this guide does not claim those capabilities are generally released. Test your required devices during onboarding before relying on them for live work.
Use the comparison worksheet to record evidence for each device. Include the office handoff so a field update has a clear next action.
Common questions
Does mobile-friendly mean offline-ready?
No. A page can fit a phone screen while still requiring a connection for every operation. Verify the exact offline tasks and their synchronization behavior.
How do I verify native notifications?
Use an identified installable build on the required device and test the relevant locked-screen and background scenarios. Record the build, permissions and result.
Bring your workflow to the demo
Explore the fictional request-to-approval journey, then discuss the capabilities your business needs.
Hi, I’m Flor