Mobile adaptation — My Day Home View

This screen now treats My Day as the technician’s real home, using the supplied reference as the main design anchor: a map-first top half, a docked daily summary sheet, numbered stops, and a focused bottom navigation. The list is driven by upcoming work events. The work ticket still remains the technician’s execution home base, but My Day becomes the entry point into that work.

What this screen simplifies

• The technician lands in a day view of upcoming work events, not in a generic list or dashboard.
• Each stop is a work event for a work order, so schedule context is clear before execution starts.
• The route and the appointment list are visible together, so there is no context switch between map and schedule.
• The next actionable work event can expand in place, and the technician can create their work ticket from that event.
• Voice commands operate on the scheduled work-event sequence instead of forcing the user to search manually.

Voice command behaviors

• “Show me my next appointment” resolves the next scheduled work event, zooms the map to that stop, and expands a compact detail card.
• “Navigate to my next appointment” resolves the same next work event, then opens a handoff sheet for Apple Maps or Google Maps.
• “Create my work ticket” should create or open the technician's own ticket from the selected work event.
• Both commands should work without the technician needing to name the customer, stop number, or address.

Voice examples

Jigx component mapping

Open questions to validate

• Should the expanded card default to the next scheduled appointment or the nearest upcoming appointment when route conditions change?
• Should Navigate to my next appointment open the user’s default maps app immediately, or should we always show the Apple Maps / Google Maps chooser first?
• Do we want the technician to be able to start the appointment directly from My Day, or should the action always pass through the work-ticket detail screen first?