← Back to Documentation

VIA Visual Diagrams

31 Interactive Mermaid Diagrams β€” System Architecture, Workflows, APIs, Database Schemas

Note: This page displays interactive diagrams. For high-resolution PNG exports, visit the Exported Diagrams Gallery.

πŸ“± Mobile App Wireframes (6 Diagrams)

7.1 Driver App β€” Login & Home Screen

graph TB subgraph "Screen 1: Login" LOGO[VIA Logo
GREEN #059669] EMAIL[Email Input
chavez684@gmail.com] PASS[Password Input
β€’β€’β€’β€’β€’β€’β€’β€’] LOGIN_BTN[Login Button
GREEN background] FORGOT[Forgot Password?] end subgraph "Screen 2: Home Dashboard" HEADER[Header:
Driver: Juan PΓ©rez
Status: Active] VEHICLE[Current Vehicle Card
Chasis - ABC-123
Type: 40HC Container] TRIP[Active Trip Card
Container: ZIMU3040114
Destination: Guadalajara
ETA: 2:30 PM
Status: In Transit] NAV_BTN[Navigate Button
Start Navigation] CONVOY[Convoy Info
E-20260228-ABC123-001
10 trucks, Position #3] BOTTOM_NAV[Bottom Navigation
Home | Trips | Inspections | Profile] end LOGIN_BTN --> HEADER style LOGO fill:#059669,color:#fff style LOGIN_BTN fill:#059669,color:#fff style NAV_BTN fill:#059669,color:#fff style TRIP fill:#F0FDF4 style CONVOY fill:#ECFDF5

7.2 Driver App β€” Vehicle Type Selection

graph TB subgraph "Vehicle Type Selector Screen" TITLE[Select Your Vehicle Type] CHASIS[πŸš› Chasis
Container Transport
NOMs: 012, 015, 087] TOLVA[🚚 Tolva
Mineral/Bulk Dump
NOMs: 012, 087] JAULA[πŸ“¦ Jaula Granelera
Grain Transport
NOMs: 015, 087] PLAT[πŸ—οΈ Plataforma
General Cargo
NOMs: 012, 015, 087] PIPA[β›½ Pipa
Natural Gas Hazmat
NOMs: 033, 087] LOWBOY[βš™οΈ Low Boy
Heavy Special
NOMs: 012, Special Permit] CAJA[πŸ“¦ Caja Seca LCL
Multi-Client Cargo
NOMs: 015, 087] LIGERA[πŸš™ Camioneta Ligera
Light Cargo
NOMs: 087] CONFIRM[Confirm Selection Button] end TITLE --> CHASIS TITLE --> TOLVA TITLE --> JAULA TITLE --> PLAT TITLE --> PIPA TITLE --> LOWBOY TITLE --> CAJA TITLE --> LIGERA CHASIS -.selected.-> CONFIRM TOLVA -.-> CONFIRM JAULA -.-> CONFIRM PLAT -.-> CONFIRM PIPA -.-> CONFIRM LOWBOY -.-> CONFIRM CAJA -.-> CONFIRM LIGERA -.-> CONFIRM style CHASIS fill:#059669,color:#fff style CONFIRM fill:#059669,color:#fff

πŸ”Œ API Documentation Diagrams (5 Categories)

8.1 Authentication & User Management (8 Endpoints)

graph LR subgraph "Authentication & User Management APIs" AUTH1[POST /api/auth/login
Email + Password β†’ JWT] AUTH2[POST /api/auth/refresh
Refresh JWT 7-day expiry] AUTH3[POST /api/auth/logout
Invalidate JWT] AUTH4[GET /api/auth/verify
Verify JWT nginx auth] USER1[GET /api/users/profile
Get current user] USER2[PUT /api/users/profile
Update profile] USER3[POST /api/users/register
Register new user admin-only] USER4[GET /api/users
List all users admin-only] end AUTH1 --> AUTH2 AUTH2 --> AUTH3 AUTH3 --> AUTH4 AUTH4 --> USER1 USER1 --> USER2 USER2 --> USER3 USER3 --> USER4 style AUTH1 fill:#0D9488,color:#fff style USER3 fill:#f59e0b,color:#fff style USER4 fill:#f59e0b,color:#fff

πŸ—„οΈ Database ER Diagrams (3 Views)

10.1 Vehicle & Patio Type Classification Schema

erDiagram vehicle_types ||--o{ trucks : "defines type" patio_types ||--o{ patios : "defines type" companies ||--o{ trucks : "owns" companies ||--o{ drivers : "employs" companies ||--o{ patios : "manages" trucks ||--o{ trips : "assigned to" drivers ||--o{ trips : "drives" vehicle_types { int id PK string code UK string name text[] applicable_noms jsonb inspection_checklist boolean convoy_eligible } patio_types { int id PK string code UK string name text[] features boolean requires_sat_integration boolean requires_ptd_integration } trucks { int id PK int company_id FK int vehicle_type_id FK string plate UK int capacity_kg string status } patios { int id PK int company_id FK int patio_type_id FK string name decimal lat decimal lng int capacity int current_occupancy } companies { int id PK string name string rfc UK string status } drivers { int id PK int company_id FK string name string license_number UK string skill_level decimal hourly_cost_mxn } trips { int id PK int company_id FK int truck_id FK int driver_id FK string container_number int origin_patio_id FK string destination string convoy_id string status }