The seven-minute glare-and-glove test for a jobsite app

Prepare one real task

Choose a common workflow that can be completed without exposing customer information. Good examples include starting a blank daily log, adding a practice photo, marking a sample punch item, or completing a training checklist.

Use a test project and noncustomer images. Do not run the test against a live job record unless the person testing already has permission to access it.

Minute 1: establish the starting point

Open the task from the screen where a crew member would normally begin. Note the device, operating system, app version, brightness setting, connection state, and whether gloves are being worn.

Do not change settings midway through the first attempt. The goal is to capture the normal starting condition before trying improvements.

Minutes 2–3: run the task in ordinary light

Complete the selected task once. Count the moments when the tester must stop, reread, zoom, backtrack, or ask what a control means.

Record the result in plain language:

• Could the tester identify the next action without coaching?
• Were the important controls easy to tap on the first try?
• Did the screen make saved, pending, and failed states clear?
• Could the tester recover after choosing the wrong control?
• Did the app preserve the work if the tester moved away from the screen?

Minutes 4–5: repeat in glare and with normal work gear

Move to a safe outdoor position with the screen facing the light conditions the crew commonly sees. Repeat the same task while wearing the gloves or other gear normally used for that work.

Do not create an unsafe test location or ask someone to operate the device while driving, climbing, or handling equipment.

Note which labels disappear in glare, which controls become difficult to distinguish, and which tap targets require repeated attempts. A failed tap is more useful evidence than a general comment that the screen “feels small.”

Minute 6: interrupt the workflow

Pause before saving, move to another screen, then return. If the app supports offline work, repeat only the documented offline procedure using a training record.

Check whether the app explains what was saved locally, what still needs to synchronize, and what the user should do next. Do not assume that a visible item reached the server unless the app provides evidence of synchronization.

Minute 7: record one fix and one follow-up

Write down the single problem that caused the most delay or uncertainty. Describe the screen, action, expected result, actual result, device, conditions, and whether the problem could be repeated.

Choose one next step:

• adjust the form or workflow configuration;
• create a short crew instruction;
• test an accessibility or display setting;
• compare an approved accessory after fit and compatibility are verified; or
• send the software vendor a reproducible issue report.

Keep the original observation separate from the proposed fix. A suggestion is not proof that a product or configuration will solve the problem.

Field test record

Save these eight items with the test:

1. device and operating system;
2. app and version;
3. workflow tested;
4. light, weather, glove, and connection conditions;
5. completed, blocked, or uncertain result;
6. repeated taps, backtracking, or lost work observed;
7. screenshots or recordings that contain no customer information; and
8. owner and next review date.

Equipment note

Field UI/UX may later compare touchscreen-compatible work gloves or anti-glare screen films when a specific product has current manufacturer evidence, verified device compatibility, and a permitted merchant link. No product currently meets those release gates in the observed catalog, so this article carries no product link or purchase recommendation.

The useful result today is the test record: it shows what the crew experienced and gives the next design or configuration change a clear starting point.