Repository navigation
docs enterprise ux app
This file designs the information architecture, the shared screen states, the flows and the visual rules of enterprise mode in the Android app. It is the home of what every app screen shares (00-conventions §4). Individual screens are specified in section 11 of each module file and indexed in §7. The web surfaces are in 13-ux-web.
Evidence. The app today is the personal product only. Its shell is four tabs, Explorar | Comunidade | Mapa | Perfil (app/src/main/kotlin/com/anpfuel/app/navigation/AbastevoBottomBar.kt, TabNavigation.kt, AnpNavGraph.kt), IMPLEMENTED. The visual identity is described in docs/android/design-system.md and docs/android/ui-containers.md and lives in app/src/main/kotlin/com/anpfuel/app/ui/theme/ and ui/designsystem/, IMPLEMENTED; rendered light, dark and 200 % font checks are recorded there as VISUAL_VALIDATION_PENDING. Pieces this design reuses exist: the header (ui/header/AbastevoHeader.kt), the state components (ui/components/LoadingState.kt, EmptyState.kt, ErrorState.kt, Skeleton.kt, SyncStatusBanner.kt, SourceTimeBadge.kt), the map, route sheet and turn-by-turn guidance (ui/map/MapScreen.kt, NativeRouteSheet.kt, GuidanceControls.kt, GuidanceService.kt, MapDownloadsScreen.kt), camera capture (capture/CaptureScreen.kt), the personal ledger screens (ui/ledger/LedgerEntriesScreen.kt, ui/sync/LedgerSyncScreen.kt) and the semantics helpers (ui/accessibility/AccessibilitySemantics.kt). No enterprise mode, context switcher, organization header or organization queue exists; everything below is PROPOSED, in a package com.anpfuel.app.ui.enterprise (proposed, 09-architecture §2).
- The four tabs stay. Enterprise mode is a separate experience entered from the app. It is not a fifth tab and it does not change Explorar, Comunidade, Mapa or Perfil.
- The organization is always named. Every enterprise screen shows which organization is active, and only the user changes it (BR-AUTH-012).
- One visual identity. Enterprise mode uses the existing tokens, fonts, components and container defaults. It adds no colour. The green accent keeps its meaning and is never the fill of a primary button nor the colour of a price or an amount.
- The role shapes the screen; the server decides. Home blocks and actions come from the member's cached permissions (07-permissions §8). Hiding an action is a convenience, never the control (BR-AUTH-002).
- Plain language. Labels use the interface words of 03-glossary. No identifier, error code or protocol word appears on a screen; a reason is a sentence that says what happened and what to do.
- The field has no signal. A field action is saved on the device first and always shows where it is (BR-OFFL-010). An action that needs the server says so before the user tries it (BR-OFFL-017).
- Few steps for frequent actions. Context fills what it can (trip in progress, assigned asset, last product). Targets are in §4.18.
- Hands and eyes belong to the road. While a trip is moving, the screen offers only large, glanceable actions; detailed entry happens while stopped (05-journeys JRN-06).
- Three states, three labels. What is happening, where the record is and whether the company approved it are shown separately (08-state-model §1). No state is told by colour alone.
| Entry | Behaviour |
|---|---|
| Perfil tab | A neutral entry card "Modo empresa" (existing entry-card pattern, outlined button) lists the organizations of the account. With no membership it offers "Tenho um convite" and "Ativar acesso corporativo" (§4.1). |
| Invitation link or code | Opens the activation flow (§4.1). |
| App start | The app reopens in the context that was active on this device (UC-AUTH-04). It never picks an organization from a record or a notification by itself. |
| Organization notification | The notification names the organization. Opening it shows the item inside that organization; when another context was active, the change is announced (§4.14). |
| Managed account | After the local unlock (SCR-PRIV-05) the app opens directly in enterprise mode. The account has no personal content (EDR-031); the four tabs remain reachable from the switcher as public, read-only data. |
Enterprise mode is a full-screen area with its own navigation. The bottom bar is not shown inside it, because its tabs are personal and public destinations. System back on the enterprise home leaves the app; it never changes context. The only way out to the four tabs is the context switcher (SCR-AUTH-04).
- Organization header (§5.2): the label "Modo empresa" and the organization's name. On the home it is the full header; on inner screens it is one fixed line under the screen title. Tapping it opens the context switcher.
-
Tracking indicator (§5.4), whenever a tracking session of this device is not
NOT_STARTEDorENDED. - Connection and storage banners: the offline banner with the last successful send, and the storage warning (SCR-OFFL-05), as persistent banners, never blocking dialogs.
The home is one scrolling screen made of blocks. A block appears only when the member holds its permission in the active organization. A member with several roles sees the union (BR-AUTH-003).
| Block | Driver (DRIVER) |
Operations staff (OPERATIONS_STAFF) |
Supervisor on the phone (SUPERVISOR) |
Permission |
|---|---|---|---|---|
| Current activity card with the main action | Trip in progress, or next mission, or "Iniciar viagem" | Not shown | Own trip, as a driver | trip.trip.start |
| Quick actions (large tiles) | Abastecimento, Despesa, Ocorrência | Abastecimento, Despesa, Checklist, Ocorrência; internal tank movement when enabled | Same as driver |
fuel.fueling.record, exp.expense.record, check.checklist.execute, check.incident.report, stock.movement.record
|
| My missions | Missions ASSIGNED or ACCEPTED
|
Not shown | Own missions | trip.trip.start |
| Team today (read-only) | Not shown | Not shown | Trips IN_PROGRESS and PAUSED in scope with the time of the last send; count of records waiting for a decision |
trip.trip.read beyond own records |
| Returned to me | Records RETURNED
|
Same | Same | author |
| Pending sends | Count by state, opens SCR-OFFL-01 | Same | Same | any member |
| History | Own records | Same | Own and, read-only, the scope | read permissions |
| My account in this company | "Meu acesso" (SCR-AUTH-05), "O que a empresa coleta" (SCR-PRIV-01), "Sair" | Same | Same | any member |
Approving, returning and rejecting are online-only (10-offline-sync §10.3) and are done in the company panel. The supervisor's phone shows the count and says where the decision is made; it offers no decision button. A member whose roles have no field permission (for example AUDITOR) sees the account block and one sentence saying that the work of that role is in the panel.
| Thing | Place | Screen |
|---|---|---|
| Pending sync | Round header button with a count; "Pending sends" block on the home | SCR-OFFL-01, SCR-OFFL-02 |
| Storage or long-unsent warning | Persistent banner under the header | SCR-OFFL-05 |
| Notifications | Round header button with an unread count, per organization | Notification centre, imports-notifications-integrations |
| My access | "My account in this company" block | SCR-AUTH-05 |
| What the company collects, my tracking sessions | Same block; also the tracking indicator | SCR-PRIV-01, gps-navigation |
| Other organizations and personal mode | Organization header | SCR-AUTH-04 |
| A denied action | In place of the screen that was asked | SCR-AUTH-06 |
flowchart TD
subgraph Personal["Personal mode: four tabs, unchanged"]
EX[Explorar] --- CO[Comunidade] --- MA[Mapa] --- PE[Perfil]
end
PE -- "Modo empresa card" --> SW["Context switcher (SCR-AUTH-04)"]
INV[Invitation link or activation code] --> ACT[Activation] --> NOTICE["What the company collects (SCR-PRIV-01)"]
SW & NOTICE --> HOME
subgraph Enterprise["Enterprise mode: organization header on every screen"]
HOME[Enterprise home by role] --> VEH[Vehicle selection] --> CUR[Current activity and trip screen]
HOME --> CUR
CUR --> CHK[Checklist] & NAV[Route and navigation] & LOG[Logbook] & FIN[Finish and submit]
HOME & CUR --> FUEL[Fueling with receipt] & EXPN[Expense] & INC[Incident]
HOME --> PEND["Pending sync (SCR-OFFL-01, SCR-OFFL-02)"] & NOTIF[Notifications]
HOME --> HIST[History] --> RET[Correct a returned record]
HOME --> ACC["My access (SCR-AUTH-05)"] & OUT["Log out (SCR-OFFL-04)"]
end
HOME -- organization header --> SW
SW -- "Modo pessoal" --> PE
Every app screen inherits these defaults. A module screen states only what differs.
| State | When | What the screen shows | Action offered | TalkBack |
|---|---|---|---|---|
| Loading | Nothing is cached yet | Skeletons with the final layout (SkeletonCard, 12dp); the organization header is already real. Cached content is shown at once with its age instead of a skeleton. |
None | "Carregando" once, as a polite live region; focus moves to the screen heading when content arrives. |
| Empty | The list or record set has no items | One sentence saying what will appear here, and exactly one next action when the member may take it (EmptyState). |
The single next action, or none | Sentence, then the action. |
| Error | A read or a local write failed | What failed in plain words and that saved data is safe (ErrorState). No code or identifier is displayed; "Copiar detalhes para o suporte" copies a reference without showing it. |
"Tentar de novo" | Announced as an alert; focus on the retry button. |
| Unavailable | No connection for an online-only action; or the organization, membership or plan does not allow it now | The reason in one sentence and what still works. Offline: "Sem internet. Isto precisa de conexão." with the last successful send. Suspended or not included: says so, with no price and no purchase link (EDR-024). | Go back; retry when online | Reason read with the disabled control: "indisponível, " and the reason. |
| Forbidden | The member lacks the permission | The no-permission pattern (SCR-AUTH-06): the action that was denied and who can grant it. Never any record data (BR-AUTH-013). | "Voltar" | Heading "Sem permissão", then the explanation. |
Two more defaults apply everywhere. Cached reference data shows when it was confirmed ("Atualizado em …"), and is marked as not confirmed after 24 hours without contact (BR-OFFL-016, 07-permissions §8). A state name the app does not know is shown as unknown with a request to update the app, never mapped to a known one (08-state-model §4).
Sync labels (08-state-model §2). The text is fixed; the icon shape differs per state; colour only reinforces.
| State | Label | Icon shape | Tone | TalkBack text |
|---|---|---|---|---|
SAVED_ON_DEVICE |
Salvo no aparelho | Phone | Neutral | "Salvo no aparelho. Ainda não enviado." |
SENDING |
Salvo no aparelho, with a progress hint | Phone with progress | Neutral | "Salvo no aparelho. Enviando." Not repeated while it lasts. |
SENT |
Enviado | Arrow up | Neutral | "Enviado. Aguardando confirmação." |
ACCEPTED |
Aceito pela empresa | Check | Neutral ink | "Aceito pela empresa." |
NEEDS_REVIEW |
Precisa de revisão | Triangle with exclamation | Notice (amber) | "Precisa de revisão", then the reason. |
REJECTED |
Não aceito | Circle with a cross | Error | "Não aceito", then the reason. |
A change of sync state on a visible record is announced once through a polite live region. "Aceito pela empresa" never appears as "aprovado": the record detail shows the review state on its own line (BR-REV-001). In lists a row shows one chip, the most urgent of the record: Não aceito, Precisa de revisão, returned, Salvo no aparelho, then the rest. The detail screen shows the operational, sync and review states as three labelled lines.
Each flow names the module that specifies its screens. Diagrams show the main path and the exceptions that change what the user sees.
Screens: identity, SCR-PRIV-01, SCR-PRIV-05. Online only. Journeys JRN-01 and JRN-02. Steps. 1) Invitation: the employee opens the link, or types the code under "Tenho um convite", and signs in with their own account if needed. 2) The app shows the organization's name and what joining means: the company sees what is recorded in enterprise mode; personal data stays personal. 3) Corporate access: the employee chooses "Ativar acesso corporativo", types the activation code and sets the local unlock. 4) Both paths show what the company collects (SCR-PRIV-01), with nothing pre-ticked, and then open the enterprise home. 5) An expired, revoked, used or locked invitation or code says that it no longer works and that the company issues a new one.
flowchart LR
I[Invitation link or code] --> S{Signed in?}
S -- no --> L[Sign in with own account] --> O
S -- yes --> O[Organization name and what joining means]
O -- accept --> N[What the company collects]
C[Corporate access: type activation code] --> U[Set local unlock] --> N
N -- acknowledge --> H[Enterprise home]
O -. expired or revoked .-> X[Ask the company for a new one]
C -. locked or expired .-> X
Screen: SCR-AUTH-04 (UC-AUTH-04, UC-OFFL-05). Journey JRN-03. Steps. 1) The user taps the organization header, or the "Modo empresa" card in Perfil. 2) A bottom sheet lists personal mode and each organization, with its state and its count of pending sends. 3) Choosing one opens that context's home and announces "Você está em" followed by the name. 4) A suspended membership is listed disabled with the reason. Offline, the list is the last known one, marked as not confirmed. 5) With a trip in progress, the sheet says that the trip and its tracking continue; the tracking indicator follows the user (§5.4).
flowchart LR
P[Organization header or Perfil card] --> W[Context switcher]
W -- organization --> H[Enterprise home of that organization]
W -- personal mode --> T[Four tabs]
W -. membership suspended .-> D[Row disabled with reason]
W -. offline .-> C[Last known list, marked not confirmed]
Screens: identity (home shell), §2.3. Works offline from cached data (UC-OFFL-08). Steps. 1) The home is drawn at once from cached permissions and reference data. 2) In the background the app refreshes missions, assets and policies and updates "Atualizado em …". 3) The current activity card and the quick actions come first; lists follow. 4) A block the member cannot use is absent, not disabled.
flowchart TD
O[Open enterprise mode] --> H[Home drawn from cached permissions]
O --> R[Refresh reference data in the background]
H --> A[Current activity card and main action] & Q[Quick actions] & L[Returned to me, pending sends, history]
R -. no connection .-> S[Lists keep their confirmed-at time]
Screens: trips. Offline. The current activity is a trip IN_PROGRESS or PAUSED, or else the next mission ASSIGNED or ACCEPTED.
Steps. 1) The card shows the asset, the running time and the tracking state; tapping it opens the trip screen. 2) An assigned mission opens its detail; the driver accepts, or declines with a reason, and may start the trip from it. 3) With nothing current, the card is the "Iniciar viagem" action. 4) The trip screen offers: add event, pause or resume, route, and finish.
flowchart LR
C{What is current?} -- trip in progress --> T[Trip screen]
C -- mission assigned --> M[Mission detail] -- accept --> V[Start trip]
M -- decline with reason --> H[Home]
C -- nothing --> V
T --> E[Add event, pause, route, finish]
Screens: fleet. Offline from the cached asset list.
Steps. 1) When the member has exactly one assigned asset, it is preselected and only shown for confirmation. 2) Otherwise the list shows assigned assets first, then the others the member may use, with search by plate or fleet number. 3) An asset that is RESERVED, IN_USE, IN_MAINTENANCE, BLOCKED or UNAVAILABLE is listed disabled with the reason. 4) The list shows its confirmed-at time; a choice made on old data is checked by the company when it arrives (BR-OFFL-016).
flowchart LR
S[Start trip, or a record outside a trip] --> O{Exactly one assigned asset?}
O -- yes --> P[Preselected, shown for confirmation]
O -- no --> L[List: assigned first, search]
L --> U{Available?}
U -- yes --> P
U -- no --> R[Disabled with reason]
P --> N[Next step of the calling flow]
Screens: maintenance. Offline.
Steps. 1) When the asset's template asks for it, the checklist opens before the trip starts or finishes. 2) Each item is one row with two large targets, OK and problem; a problem asks for a photo and a short note. 3) A failed critical item ends in BLOCKING: the app explains the company's policy and offers another asset or an incident report. 4) Otherwise the run ends as COMPLETED_OK or COMPLETED_WITH_ISSUES and the calling flow continues.
flowchart LR
T[Start or finish a trip] --> R{Checklist required?}
R -- no --> N[Continue]
R -- yes --> I[Items: OK or problem, photo and note on a problem]
I --> C{Critical item failed?}
C -- no --> N
C -- yes --> B[Blocking: explain, choose another asset or report an incident]
Screens: gps-navigation. Offline with a downloaded map region; no live traffic is offered. Steps. 1) From the trip screen, "Rota" shows the planned stops, or lets the driver pick a destination. 2) If the map region is not on the device, the app offers the download, which needs a connection. 3) The preview shows the planned distance, labelled as planned. 4) Guidance runs in the driving layout (§5.5) with the organization line and the tracking indicator visible. 5) Arriving at a stop offers a one-tap stop event; ending guidance returns to the trip screen and the trip continues.
flowchart LR
T[Trip screen] --> R[Route: planned stops or a chosen destination]
R --> M{Map region on the device?}
M -- no --> D[Download the region, needs connection] --> P
M -- yes --> P[Preview with planned distance]
P --> G[Turn-by-turn guidance, driving layout]
G -- arrive at a stop --> S[One-tap stop event] --> G
G -- guidance finished --> T
Screens: trips. Offline. The screen says that the logbook is an operational record and not a time clock (LV-05); its interface name is open (OQ-12). Steps. 1) The trip screen shows the timeline in order of occurrence, each event with its time and its sync label. 2) "Adicionar evento" opens a grid of kinds: stop, fueling, toll, parking, incident, handover, note. 3) Each kind asks for the fewest fields; a photo is optional unless the kind needs one. 4) Correcting an event creates a new version and keeps the old one.
flowchart LR
T[Trip screen: timeline] --> A[Add event] --> K[Choose kind] --> F[Few fields, optional photo] --> S[Saved on device]
S --> T
T --> E[Open an event] --> C[Correct: new version, old one kept]
Screens: fuelings, documents. Offline, except with an agreement voucher code, which is online-only. Journey JRN-01. Steps. 1) "Abastecimento" on the home or on the trip screen opens the camera on the receipt. "Sem comprovante agora" skips the photo. 2) The photo is checked for legibility on the device; the driver keeps it or retakes it. 3) The form has the asset and product already filled, and asks for quantity, total paid and the meter reading. Unit price, fill level and place are optional. 4) Missing quantity or total blocks saving (BR-MONEY-006). An arithmetic difference or a volume above the tank is a warning, not a block (BR-MONEY-005). 5) "Registrar" saves on the device and marks the fueling ready to send; the photo is sent after the record (BR-OFFL-015).
flowchart LR
A[Fueling action] --> C[Camera: receipt]
C -- keep photo --> F[Form: quantity, total paid, meter reading]
C -- no receipt now --> F
F --> V{Quantity and total present?}
V -- no --> F
V -- yes, warnings shown --> S[Saved on device, ready to send]
S --> Y[Sent, then accepted by the company, photo follows]
Screens: expenses-finance, documents. Offline. Steps. 1) "Despesa" opens the grid of categories cached from the organization. 2) The receipt photo comes next, when the category's policy asks for one. 3) The form asks for the amount and who paid; "paid by me" marks the expense for reimbursement. 4) A trip in progress is linked automatically; saving marks the expense ready to send.
flowchart LR
A[Expense action] --> K[Category] --> C[Receipt photo, when the policy asks] --> F[Amount and who paid]
F --> S[Saved on device, ready to send]
F -. paid by the employee .-> R[Marked for reimbursement]
Screens: maintenance. Offline. Steps. 1) "Ocorrência" asks for the kind: breakdown, accident, fine notice, theft or damage. 2) Photos and a short note follow; the note field asks not to enter health or other sensitive details about people (BR-PRIV-007). 3) The asset and the trip in progress are already filled. 4) After saving, the app offers a maintenance request when the asset needs repair.
flowchart LR
A[Incident action] --> K[Kind] --> P[Photos and short note] --> S[Saved on device]
S --> M{Asset needs repair?}
M -- yes --> Q[Maintenance request]
M -- no --> H[Back to where the user was]
Screens: SCR-OFFL-01, SCR-OFFL-02, SCR-OFFL-05 (UC-OFFL-01 to UC-OFFL-03). Steps. 1) The header button or the home block opens the list, grouped by state, with kind, time and reason. 2) "Enviar agora" is enabled only with a connection; otherwise the list says when the last send succeeded. 3) A record opens its history: saved, sent, accepted, review, outcome, and the progress of its photo. 4) A record that was not accepted shows the reason; the user creates a new one from it, or dismisses it. Nothing leaves the list by itself (BR-OFFL-013).
flowchart LR
B[Header button or home block] --> L[Pending list by state]
L -- send now, online --> D[Delivery in order]
L --> I[One record: history]
I -- photo failed --> R[Retry or capture again]
I -- not accepted --> N[Read reason, create again from it or dismiss]
I -- needs review --> W[Reason shown, the company decides]
Screens: trips, fuelings, expenses-finance. Offline with the last known review results. Steps. 1) "Histórico" lists the member's own trips, fuelings and expenses, newest first, with one chip per row (§3). 2) Filters are kind and period; the list says when review results were last confirmed. 3) A record opens its detail: three state lines, timeline, documents. 4) A returned record leads to §4.16.
flowchart LR
H[Home] --> L[My records: trips, fuelings, expenses]
L --> F[Filter by kind and period]
L --> D[Record detail: three states, timeline, documents]
D -- returned --> C[Correct and resubmit]
Screens: imports-notifications-integrations. In-app first (EDR-032); the list works offline with what was last received. Steps. 1) The header button shows the unread count of the active organization and opens its notification centre. 2) Items are returned records, review outcomes, assigned missions and access changes; each opens its destination. 3) A system notification always names the organization. 4) Opened from another context, it switches to that organization and announces the change before showing the item.
flowchart LR
N[Header button with unread count] --> C[Notification centre of this organization]
C --> I[Open item] --> D[Destination screen]
S[System notification names the organization] --> X{Same organization active?}
X -- yes --> D
X -- no --> W[Switch context, announced] --> D
Screens: trips, fleet (reading). Offline. Journeys JRN-01 and JRN-06.
Steps. 1) "Encerrar viagem" on the trip screen asks for the final meter reading. 2) The return checklist runs when required (§4.6). 3) The conference lists the trip's fuelings, expenses and documents and flags a missing receipt; the driver fixes it or continues. 4) "Encerrar e enviar" ends tracking and marks the trip COMPLETED, "Salvo no aparelho" and ready to send. 5) When the server accepts it, the review state becomes SUBMITTED (BR-REV-002).
flowchart LR
T[Trip screen] --> E[Finish trip] --> R[Final meter reading]
R --> K[Return checklist, if required]
K --> C[Conference: missing receipts flagged]
C --> S[Finish and send]
S --> O[Tracking stops, trip completed, saved on device]
O --> Y[Server accepts: submitted for review]
Screens: expenses-finance (my submissions), plus the record's module. Offline (BR-REV-005).
Steps. 1) A notification, or "Returned to me" on the home, opens the record with the reviewer's reason at the top. 2) The author edits the fields or adds the missing receipt. 3) "Reenviar" saves a new version on the device; the review state stays RETURNED until the server accepts it. 4) If the record changed meanwhile, it shows "Precisa de revisão" and both versions are kept.
flowchart LR
N[Notification or returned-to-me block] --> D[Record with the reviewer's reason on top]
D --> E[Edit fields or add receipt]
E --> R[Resubmit: new version saved on device]
R --> A{Server answer}
A -- accepted --> S[Submitted again]
A -- record changed meanwhile --> V[Needs review, both versions kept]
Screens: SCR-OFFL-04 (UC-OFFL-06, BR-PRIV-017). Steps. 1) "Sair" is in the account block of the home. 2) With a trip in progress, the app first asks the driver to pause or finish it, so that tracking never runs without a session. 3) With pending sends, a dialog shows their count and size and offers "Enviar agora" (online), "Manter neste aparelho" and "Cancelar". 4) The dialog says that uninstalling the app or resetting the phone loses what was not sent (BR-OFFL-013, BR-OFFL-014). 5) Logging out removes the session and locks the organization's local data; the same account sends what was kept at its next login.
flowchart LR
O[Log out] --> T{Trip in progress?}
T -- yes --> Z[Pause or finish first]
T -- no --> P{Pending sends?}
P -- no --> X[Session removed, local data locked]
P -- yes --> D[Dialog: count and size]
D -- send now --> X
D -- keep on this device --> X
D -- cancel --> B[Stay signed in]
A tap is one touch on a control. Typing a value and the keyboard's "next" key are counted as typed values, not taps. One-time system permission dialogs are not counted.
| Flow | Starting point and conditions | Taps | Typed values | Target |
|---|---|---|---|---|
| Record a fueling | Enterprise home or trip screen; asset known from the trip or the single assignment; product remembered | 4: fueling action → shutter → keep photo → "Registrar" | 3: quantity, total paid, meter reading | At most 4 taps and 3 values. Choosing an asset or changing the product adds 1 tap each. |
| Start a trip | Enterprise home; one assigned asset; no checklist required | 2: "Iniciar viagem" → "Iniciar" | 1: meter reading | At most 2 taps and 1 value. Asset selection adds 1 tap; a checklist adds 1 tap per item. |
The start button states in one line that tracking starts with the trip and stops when it pauses or ends (LV-03), so the notice costs no extra tap. These counts are design targets; counts measured on a device are owed evidence (§8).
| Need | Existing piece |
|---|---|
| Colours, type, shapes, spacing |
AnpFuelTheme; EnergiaLightTokens, EnergiaDarkTokens, AbastevoAccent; Manrope and Source Sans 3; 8, 12, 16 and 24dp radii; AbastevoSpacing with the 16dp screenGutter
|
| Main and secondary actions |
Button (ink fill), OutlinedButton, TextButton from ui/designsystem; one filled button per screen section |
| Cards and grouped content |
AnpContainerDefaults outline and shape; no second outline, no outlined layouts |
| Inner screen title |
AnpTopAppBar, flat on the screen colour |
| Loading, empty, error |
SkeletonCard, LoadingState, EmptyState, ErrorState
|
| Offline and stale banners |
SyncStatusBanner; amber (tertiary) for notice |
| Source and time on a value |
SourceTimeBadge pattern for "Atualizado em …" |
| Large action tiles, account rows |
ActionCardButton, ProfileActionRow
|
| Filters and kinds |
FilterChip (selected: solid ink), AssistChip
|
| Dialogs and sheets | 24dp shape; the context switcher and the logout dialog use it |
| Map, route preview, guidance | The existing map engine, route sheet and guidance controls |
| Receipt camera | The existing capture flow, with a document-oriented frame |
| Component (proposed) | Why existing pieces are not enough | Built from |
|---|---|---|
| Organization header | Nothing in the app shows an active context | The flat header chrome and its gray pill field: uppercase label "Modo empresa", business icon in ink, organization name in Manrope, chevron; round gray buttons for notifications and pending sends |
| Context switcher sheet | New concept | Bottom sheet with selectable option rows |
| Status chip | Three kinds of state need one consistent, non-interactive label | Pill with icon and text on surfaceContainerHigh; amber and error roles for the two urgent states |
| Tracking indicator | Location recording must be visible on every screen (BR-PRIV-006) | One-line strip under the header |
| Driving layout | Guidance and trip actions must be usable at a glance | Scaffold with two to four full-width actions |
| Trip return bar | A trip in progress must stay visible outside enterprise mode | One-line bar above the bottom bar of the four tabs |
The organization name wraps to two lines on the home and is cut to one line elsewhere; its full text is always in the content description.
- A chip is text with an icon. It is never a button and never the only place where a reason is given.
- Sync chips use the labels of §3. Review chips use the wording below. Operational states use the module's wording.
- Neutral chips are ink on gray. Amber marks what waits for someone; the error role marks what was refused. Green is not used for "accepted" or "approved", because the accent already means selection, links and community.
- Review-state wording is not yet fixed in the glossary. Proposed, to be recorded there:
DRAFT"Rascunho" (offline after submitting: "Pronto para enviar"),SUBMITTED"Aguardando aprovação",IN_REVIEW"Em análise",APPROVED"Aprovado",RETURNED"Devolvido para correção",REJECTED"Rejeitado",CANCELLED"Cancelado",VOIDED"Anulado". "Enviado" is reserved for the sync state.
| Tracking session | Strip | Tap |
|---|---|---|
RECORDING |
Location icon in the accent (its existing meaning), "Rastreamento ativo" and the running time | Opens what is collected and the session history |
SUSPENDED |
"Rastreamento pausado" | Same |
INTERRUPTED |
Amber notice: "Rastreamento interrompido" with the action "Retomar" | Resumes after the user confirms; the gap stays recorded |
NOT_STARTED, ENDED
|
Not shown | — |
With approximate location only, the strip adds that GPS distance will not be calculated. The system notification of the foreground service is always present while recording and names the organization. Outside enterprise mode the trip return bar repeats the indicator.
- Used by guidance and by the trip screen while the trip is
IN_PROGRESSand the phone is moving. - At most four actions, each full width and at least 64dp tall (hypothesis, to be confirmed in the field test): stop, fueling, incident, pause. Text uses the title role; no body-size text is needed to act.
- No text entry, no lists longer than the screen, no photo capture while moving. Those actions open after the driver confirms that the vehicle is stopped.
- The organization line and the tracking indicator stay visible.
-
Dark mode. White on true black, cards on
#141414. Every new text pair meets 4.5:1 and every new control fill, outline and indicator meets 3:1 in both themes; the pairs are added toBrandPaletteContrastTest. -
Font scale. All sizes are
sp. Screens work up to 200 %: chips and tiles grow in height, labels wrap, nothing is cut by a fixed height. -
TalkBack. Reading order is header, tracking indicator, heading, content, actions. The organization header reads "Modo empresa" and the name. Chips read their full sentence (§3). Headings use
headingSemantics; state changes useliveRegionSemantics. -
Targets. Every control and tappable row is at least 48dp tall (
controlMinHeight); driving actions are larger (§5.5). - Amounts and quantities. Ink, Manrope, with the unit beside the number; never the accent.
Labels use the pt-BR terms of 03-glossary. The ones that appear most in enterprise mode: Empresa, Modo empresa, Modo pessoal, Acesso corporativo, Convite, Código de ativação, Aparelho, Atividade, Viagem, Parada, Trecho, Diário de bordo, Evento, Troca de condutor, Encerramento, Checklist, Ocorrência, Avaria, Veículo, Máquina, Leitura, Abastecimento, Tanque cheio / parcial, Comprovante, Despesa, Reembolso, Rota planejada, Navegação, Situação de envio, Situação de revisão.
Protocol concepts never appear on a screen: queue, payload, tenant, revision numbers, record identifiers and error codes. Action labels in this file ("Iniciar viagem", "Registrar", "Enviar agora", "Tentar de novo") are proposed copy built from the glossary terms.
The rules are in 10-offline-sync; what works offline is the matrix in its §10.3. The interface applies it with four patterns.
- Works offline. The action is always enabled. Saving answers at once with "Salvo no aparelho". The offline banner says that records stay on the phone and shows the last successful send.
- Needs a connection. The control stays visible, disabled, with the reason beside it. It is never queued as if it had happened (BR-OFFL-017).
- Shows its age. Lists from the organization show when they were confirmed; old data is a notice, not an error.
- Announces limits early. The storage warning (SCR-OFFL-05) and the end of the device's offline validity (BR-PRIV-018) are shown days before they bite, with what to do.
| Online-only in the app | What the user sees offline |
|---|---|
| Sign in, accept an invitation, activate corporate access | "Sem internet. Para entrar na empresa é preciso conexão." |
| Fueling with an agreement voucher code | The code field is disabled: the code is checked at the station and needs a connection. The ordinary fueling stays available. |
| Budget hold or pre-authorization | Disabled with the reason; the expense itself can still be recorded. |
| "Enviar agora", photo upload | Disabled; the list says that sending resumes by itself when the connection returns. |
| Refreshing missions, assets and review results | The last known data with its confirmed-at time. |
| Downloading a map region | Disabled; guidance works only where the region is already on the device. |
| Confirming the list of organizations in the switcher | The last known list, marked as not confirmed. |
A revoked device or an ended membership is learned only on contact. The app then says what happened, what was delivered and what the company must be asked about, following UC-OFFL-07 and BR-OFFL-014; it never promises that unsent data of a lost phone can be recovered.
The table between the markers lists every screen whose surface is APP, generated from section 11 of the module files (00-conventions §7).
| Screen | Objective | Specified in |
|---|---|---|
| SCR-AUTH-04 | Choose personal mode or an organization | 07-permissions.md |
| SCR-AUTH-05 | Understand own access | 07-permissions.md |
| SCR-AUTH-06 | Explain a denial | 07-permissions.md |
| SCR-CHECK-01 | Fill a departure or return checklist | modules/maintenance.md |
| SCR-CHECK-02 | Show the outcome and what it means for the trip | modules/maintenance.md |
| SCR-CHECK-03 | Report a damage or an incident | modules/maintenance.md |
| SCR-CLAIM-10 | Show what the badge means on the public station profile | modules/station-claims.md |
| SCR-DOC-01 | Capture or import synthetic evidence | modules/documents.md |
| SCR-EXP-01 | Record a scoped expense | modules/expenses-finance.md |
| SCR-FLEET-08 | See the assets I may use | modules/fleet.md |
| SCR-FLEET-09 | Choose the asset for a trip, fueling or checklist | modules/fleet.md |
| SCR-FLEET-10 | Check an asset before using it | modules/fleet.md |
| SCR-FUEL-01 | Record a fueling in under a minute, with no signal | modules/fuelings.md |
| SCR-FUEL-02 | Follow my fuelings | modules/fuelings.md |
| SCR-FUEL-03 | Correct a returned fueling | modules/fuelings.md |
| SCR-GPS-01 | Start a trip knowing whether it will be tracked | modules/gps-navigation.md |
| SCR-GPS-02 | Always know the tracking state | modules/gps-navigation.md |
| SCR-GPS-03 | Resume after an interruption | modules/gps-navigation.md |
| SCR-GPS-04 | See my tracking | modules/gps-navigation.md |
| SCR-GPS-07 | Compare the four distances of a trip | modules/gps-navigation.md |
| SCR-IDN-09 | Enter a company with a code | modules/identity.md |
| SCR-IDN-10 | Decide on an invitation | modules/identity.md |
| SCR-IDN-11 | Activate corporate access | modules/identity.md |
| SCR-IDN-12 | Enterprise home | modules/identity.md |
| SCR-IDN-13 | See my access, devices and data in this company | modules/identity.md |
| SCR-IDN-14 | Know that access was suspended or ended | modules/identity.md |
| SCR-IDN-15 | Understand what deleting the account does to company records | modules/identity.md |
| SCR-MAINT-06 | Ask for maintenance | modules/maintenance.md |
| SCR-MAINT-07 | See an asset's restrictions before using it | modules/maintenance.md |
| SCR-METER-01 | Type a reading correctly | modules/fleet.md |
| SCR-NOTIF-01 | Read own notices | modules/imports-notifications-integrations.md |
| SCR-OFFL-01 | See everything not yet accepted by the company | 10-offline-sync.md |
| SCR-OFFL-02 | Understand one record's sync history | 10-offline-sync.md |
| SCR-OFFL-04 | Decide what happens to pending data before logout or context removal | 10-offline-sync.md |
| SCR-OFFL-05 | Warn about storage or long-unsent data | 10-offline-sync.md |
| SCR-ORG-12 | Tell members the organization is suspended, archived or closing | modules/organizations.md |
| SCR-PRIV-01 | Tell the employee what the company collects | 11-privacy-security.md |
| SCR-PRIV-05 | Unlock corporate access | 11-privacy-security.md |
| SCR-PUB-01 | Understand active product context | modules/subscriptions.md |
| SCR-ROUTE-02 | Preview the route before leaving | modules/gps-navigation.md |
| SCR-ROUTE-03 | Be guided while driving | modules/gps-navigation.md |
| SCR-ROUTE-04 | Complete entries at a stop | modules/gps-navigation.md |
| SCR-ROUTE-05 | Choose where to fuel on the route | modules/gps-navigation.md |
| SCR-ROUTE-06 | Open navigation from a trip in phase 1 | modules/gps-navigation.md |
| SCR-STOCK-02 | Record an authorized dispense | modules/fuel-stock.md |
| SCR-TRIP-01 | Execute an eligible trip | modules/trips.md |
- Every enterprise screen shows the organization header with the active organization's name, in both themes and at 200 % font scale.
- The four tabs render and behave exactly as before for an account with no membership, and no enterprise element appears in them except the entry card in Perfil and, during a trip, the trip return bar.
- System back on the enterprise home never changes the active context; only the context switcher does.
- A member sees on the home only the blocks whose permission they hold; a test per role of §2.3 asserts the blocks present and absent.
- Each of the five shared states of §3 renders on every app screen with the default content unless the module states a difference.
- Each sync state shows its fixed label and a distinct icon shape; a test removes colour and the six states remain distinguishable.
- Recording a fueling and starting a trip meet the tap targets of §4.18 in an instrumented run on an emulator.
- With no connection, every online-only action of §6 is visible, disabled and explained, and no field action of the offline matrix is disabled.
- No screen displays a record identifier or an error code; a test scans the string resources of the enterprise package for the codes of 09-architecture §6 and 10-offline-sync §10.2.
- While a tracking session is
RECORDING, the tracking indicator is visible on every enterprise screen and the trip return bar on the four tabs. - TalkBack reads the organization, the tracking state and each chip as full sentences, in the order of §5.6.
- All new colour pairs pass the contrast test in light and dark.
Owed evidence, never assumed:
- Comprehension with real drivers. At least five drivers and two operations employees of pilot organizations (default sample) perform the flows of §4.9, §4.15, §4.12 and §4.16 without help and explain in their own words what "Salvo no aparelho", "Aceito pela empresa", "Precisa de revisão" and "Não aceito" mean. Until this is done and recorded, the wording is a proposal.
- Field legibility. The driving layout and the status chips are read in daylight, in a vehicle mount and with one hand; the 64dp hypothesis is confirmed or changed.
- Rendered checks. Light, dark and 200 % font on an emulator and on at least one small screen; the existing design-system checks are themselves still pending.
- TalkBack pass of the two most frequent flows by a person, not only by semantics tests.
These items are recorded with the release gates in 15-validation and block a pilot with real data, not local construction.
- Home
- Roadmap
- docs-README
- docs-android-build
- docs-android-design-system
- docs-android-forum
- docs-android-games
- docs-android-map-engine
- docs-android-navigation
- docs-android-ocr-image
- docs-android-ocr-live-framing
- docs-android-premium-area
- docs-android-premium-integration
- docs-android-release
- docs-android-ui-containers
- docs-architecture-android-stack
- docs-architecture-android
- docs-architecture-backend
- docs-architecture-data-sources
- docs-architecture-overview
- docs-architecture-sources-ev-research
- docs-architecture-sources-national-limits
- docs-architecture-sources-national-stations
- docs-architecture-sources-register
- docs-assets-app-tutorial-CAPTURE_CONTRACT
- docs-assets-app-tutorial-FABLE_LANDING_POLISH_PROMPT
- docs-assets-app-tutorial-README
- docs-assets-attribution
- docs-assets-brand-README
- docs-assets-flags-ATTRIBUTION
- docs-assets-fuel-icons-README
- docs-assets-games-fuel-v1-README
- docs-assets-home-icons-README
- docs-assets-landing-fleet-android-20261012-BRIEF
- docs-assets-landing-hero-20261011-BRIEF
- docs-assets-landing-illustrated-20261012-BRIEF
- docs-assets-landing-illustrated-20261012-README
- docs-assets-landing-minimal-20261012-BRIEF
- docs-assets-landing-open-data-20261026-BRIEF
- docs-assets-landing-redesign-20261011-PREPARATION_EVIDENCE
- docs-assets-landing-redesign-20261011-README
- docs-assets-landing-redesign-20261011-REFERENCE_BRIEF
- docs-assets-landing-sync-20261012-BRIEF
- docs-assets-map-icons-README
- docs-backend-anp-ingestion
- docs-backend-api
- docs-backend-community-pricing
- docs-backend-data-model
- docs-backend-domain-model
- docs-backend-driver-private-data
- docs-backend-forum-architecture
- docs-backend-forum-bulletins
- docs-backend-forum-sources
- docs-backend-payments-provider-admission
- docs-backend-payments-provider-register
- docs-backend-photos-capture
- docs-backend-photos-subset-submission
- docs-backend-premium-api
- docs-backend-premium-cloud-protocol
- docs-backend-testing
- docs-backend-toolchain
- docs-brand-app-icons
- docs-brand-identity
- docs-decisions-001-kotlin-compose-stack
- docs-decisions-002-price-import-immutability
- docs-decisions-003-nominatim-reverse-geocode
- docs-decisions-005-modular-monolith-and-postgresql
- docs-decisions-006-official-catalog-and-exact-contracts
- docs-decisions-007-anonymous-proof-of-possession
- docs-decisions-008-privacy-and-retention
- docs-decisions-009-community-consensus-and-projections
- docs-decisions-010-private-object-evidence
- docs-decisions-012-licensing-and-hosted-business
- docs-decisions-015-kotlin-multiplatform-shared-domain
- docs-decisions-016-android-commercial-community-ios-deferred
- docs-decisions-017-station-profile-and-verified-representation
- docs-decisions-021-community-first-contribution
- docs-decisions-022-comaps-derived-native-map-engine
- docs-decisions-023-admin-suite-granted-tiers-contributors
- docs-decisions-025-private-abastevo-empresas-organization-boundary
- docs-decisions-026-multilingual-public-site
- docs-decisions-README
- docs-enterprise-README
- docs-enterprise-architecture
- docs-enterprise-backlog-INDEX
- docs-enterprise-backlog-ep00-governance
- docs-enterprise-backlog-ep01-platform
- docs-enterprise-backlog-ep02-organizations
- docs-enterprise-backlog-ep03-identity-access
- docs-enterprise-backlog-ep04-sync
- docs-enterprise-backlog-ep05-fleet-meters
- docs-enterprise-backlog-ep06-trips
- docs-enterprise-backlog-ep07-gps-navigation
- docs-enterprise-backlog-ep08-fuelings
- docs-enterprise-backlog-ep09-documents
- docs-enterprise-backlog-ep10-expenses-finance
- docs-enterprise-backlog-ep11-maintenance
- docs-enterprise-backlog-ep12-fuel-stock
- docs-enterprise-backlog-ep13-intelligence
- docs-enterprise-backlog-ep14-station-claims
- docs-enterprise-backlog-ep15-station-commerce
- docs-enterprise-backlog-ep16-subscriptions
- docs-enterprise-backlog-ep17-data
- docs-enterprise-backlog-ep18-imports-notifications-integrations
- docs-enterprise-backlog-ep19-back-office
- docs-enterprise-backlog-ep20-release
- docs-enterprise-business-rules
- docs-enterprise-contract
- docs-enterprise-conventions
- docs-enterprise-data-offering
- docs-enterprise-decisions
- docs-enterprise-domain-model
- docs-enterprise-glossary
- docs-enterprise-journeys
- docs-enterprise-modules-back-office
- docs-enterprise-modules-data
- docs-enterprise-modules-documents
- docs-enterprise-modules-expenses-finance
- docs-enterprise-modules-fleet
- docs-enterprise-modules-fuel-stock
- docs-enterprise-modules-fuelings
- docs-enterprise-modules-gps-navigation
- docs-enterprise-modules-identity
- docs-enterprise-modules-imports-notifications-integrations
- docs-enterprise-modules-intelligence
- docs-enterprise-modules-maintenance
- docs-enterprise-modules-organizations
- docs-enterprise-modules-station-claims
- docs-enterprise-modules-station-commerce
- docs-enterprise-modules-subscriptions
- docs-enterprise-modules-trips
- docs-enterprise-offline-sync
- docs-enterprise-permissions
- docs-enterprise-portal-routes
- docs-enterprise-privacy-security
- docs-enterprise-product-vision
- docs-enterprise-source-admission
- docs-enterprise-state-model
- docs-enterprise-testing
- docs-enterprise-ux-app
- docs-enterprise-ux-web
- docs-operations-README
- docs-operations-backup
- docs-operations-deploy-agent
- docs-operations-dou-editions
- docs-operations-edge-cache
- docs-operations-enterprise-activation
- docs-operations-map-static-overlay
- docs-operations-moderation-feedback
- docs-operations-moderation-profiles
- docs-operations-monitoring
- docs-operations-operator-access
- docs-operations-payments
- docs-operations-premium-billing
- docs-operations-recovery
- docs-operations-registry-daily-sync
- docs-operations-registry-runs
- docs-product-README
- docs-product-admin-tiers
- docs-product-community-community-first
- docs-product-community-experience
- docs-product-community-metrics
- docs-product-community-moderation
- docs-product-community-safety
- docs-product-community-terms-pt-br
- docs-product-driver-suite-README
- docs-product-driver-suite-android-state
- docs-product-driver-suite-cloud-sync
- docs-product-driver-suite-cost-profiles-and-maintenance
- docs-product-driver-suite-driver-model-and-earnings
- docs-product-driver-suite-foundation-decisions
- docs-product-driver-suite-gps-lifecycle
- docs-product-driver-suite-mobile-hub
- docs-product-driver-suite-odometer-review
- docs-product-driver-suite-outbox-wire
- docs-product-driver-suite-quick-refuel
- docs-product-driver-suite-reports
- docs-product-driver-suite-shifts-and-distance
- docs-product-driver-suite-signed-commands
- docs-product-ev-README
- docs-product-ev-charging-stop-planner
- docs-product-ev-energy-model
- docs-product-ev-financial-method
- docs-product-ev-journey-ui
- docs-product-ev-preparation
- docs-product-ev-typed-data
- docs-product-exploration
- docs-product-forum-contract
- docs-product-forum-policies
- docs-product-glossary
- docs-product-landing-content
- docs-product-landing-guides
- docs-product-landing-organic-growth-i18n-plan
- docs-product-licensing
- docs-product-map-discovery
- docs-product-map-favorites-and-trips
- docs-product-map-reports-routing-guidance
- docs-product-notification-content
- docs-product-official-prices
- docs-product-open-source-business
- docs-product-overview
- docs-product-payments-README
- docs-product-payments-offer-policy
- docs-product-premium-README
- docs-product-premium-financial-method
- docs-product-premium-source-policy
- docs-product-stations-catalog
- docs-product-stations-fuel-feedback
- docs-product-stations-fuel-quality
- docs-product-stations-identity-and-ev-catalog
- docs-product-stations-profile-contract
- docs-product-stations-profile-representation
- docs-product-stations-registry-sources
- docs-product-vehicle-registration
- docs-product-vehicles-and-occurrences
- docs-security-android-terms-acceptance
- docs-security-free-account-access
- docs-security-identity-profile
- docs-security-media-location-policy
- docs-security-privacy-notice
- docs-security-privacy-policy
- docs-security-retention
- docs-security-risks
- docs-security-security-privacy
- docs-store-README
- docs-store-play-readiness
- docs-store-play-store-listing
- docs-store-ugc-safety
Source: AlexandreZanata/Abastevo @ e4a67580fc368a59bc1c0f1e0466fc011313f330