Mobile adaptation — Service Location Context
This mobile version keeps the service location easy to read in the field while making the editable areas explicit. In v1, General and Address are reference tabs that stay synced from Acumatica, while Customers and Contacts are the tabs where technicians can add or update related records with the minimum information needed.
Design principles (apply to every screen from here on)
- Keep edit boundaries explicit. General and Address are visible for context; Customers and Contacts are the editable tabs in v1.
- Capture the minimum when creating related records. New customers and contacts can be created with basic enough information to keep the job moving.
- Tabs keep context focused. Four short panels (General / Address / Customers / Contacts) let the technician move through the record quickly without mixing reference information and edit actions together.
- Location stays visible even when it is not editable here. The Address tab still anchors the technician to the site and supports downstream routing and work execution context.
- Voice capture everywhere. Every header has a 🎤 that dictates into the active field(s) on the current tab.
- Primary action always docked. Save (+ Save & add another) sits above the home bar so the tech never hunts for it.
- Defaults do the work. Active = on, Location ID auto-generated on save, Country pre-filled from the tenant's home country.
Tab contents
- General — Read-only service-location context such as name, service area, work calendar, and signature settings.
- Address — Read-only site location reference, including map context and the stored address values.
- Customers — Editable list of billing customers linked to this location. The user can link an existing customer or create a basic new one.
- Contacts — Editable site contacts such as property manager, tenant, or building super. The user can add a basic new contact inline.
Voice capture
Jigx ships voice capture on every screen. On this service-location flow, voice should focus on the editable relationship tabs first, helping the technician add a customer or contact quickly with minimal typing.
Examples we should test against:
🎤"Add customer Alfa Ava as the billing customer."
→ switches to Customers, opens the customer picker pre-filtered to "Alfa Ava", and links the selected customer.
🎤"Create a new billing customer called Alfa Ava with phone 206 145 4503."
→ switches to Customers, opens the create-customer flow, and prefills the basic customer details needed to save.
🎤"Site contact Adam Wilson, mobile 206 145 4503, email adam at crossadamcal dot net."
→ switches to Contacts and creates a new contact with the parsed name, phone, and email.
🎤"Show me the site address."
→ switches to the Address tab and highlights the saved site location for quick technician reference.
Jigx component mapping
jig.default +
component.form
Root screen and form state for the Service Location record.
component.segmented-control
Four tabs - General, Address, Customers, Contacts - positioned below the header to keep each panel short.
component.section
Grouped cards within each tab (e.g. Identity vs. Preferences on the General tab).
component.text-field
Name · Address Line 1 · Address Line 2 · City · Postal Code.
component.dropdown
Service Area · Work Calendar · State · Country. Inline; no sub-navigation.
component.checkbox
Boolean fields such as Active and Require Customer Signature.
component.location
Map hero on the Address tab; drops a pin, autofills the address fields, stores lat/long.
component.list
Customers and Contacts lists with inline add/navigation actions.
component.custom-component
Optional only where the empty states or docked action bar need richer layout treatment, built from custom components such as component.card, component.view, component.text, component.icon, and component.button.
Voice input integration
The header mic is treated as a platform capability / integration layer that routes the transcript to the active tab's fields.
Open questions to validate
- Does Acumatica require a customer to be linked before the Service Location is usable in a Work Order, or can we truly save with just a name?
- Should Service Area be suggested by GPS when the tech is creating a location on-site?
- For multi-customer billing — do we need a primary/split-% capture on mobile or is that back-office only?