Sketch three useful screens before building
Draw boxes on paper before choosing colors. You can find a missing step in five minutes without writing any code. Use a familiar task, such as completing a room checklist.
The list: what should I do next?
Show the jobs the person needs to find, with enough detail to tell them apart. “Tuesday, Unit 4” is more useful than two identical cards named “Cleaning.” Show whether each job is a draft or complete.
Think about the empty screen too. A clear “Create a job” action is better than an unexplained blank area. Do not populate it with pretend customer records that look real.
The entry: what do I need to record?
Use the words staff already use. Give checkboxes enough room to tap and put labels beside every field. Let someone correct an answer without starting over.
Decide how saving works. If the app saves automatically, show success or a visible failure. If it needs a Save button, make unsaved work obvious before someone leaves the screen.
The review: did I finish correctly?
Show the job identity, the result, and any missing required information. Keep “complete,” “saved here,” and “sent to someone” distinct. They describe different events.
For an estimate, review the rate, quantity, and total before export. For a checklist, let the person reopen a completed job if the process allows a correction. Record corrections where the business needs an audit trail.
Test the sequence with paper
Ask a staff member to point to what they would tap. Try a new entry, a mistake, and a return to an unfinished job. Stay quiet long enough to see where the drawing is unclear.
Three screens are a starting pattern, not a rule. A calculator may need only one. Remove screens that add no useful decision, and keep the route back to the list easy to find.
Your choice stays on this device. It is not sent to the site owner.