Zohar App v2 — Vehicle-Centric Redesign Help

Action Panels

Actions are classified by complexity, and each gets the right amount of screen real estate.

Inline Actions

One tap, no navigation. Used for simple decisions.

Examples: Approve or reject an addition request. Change a status.

The action happens directly on the moked card within the vehicle view. A brief confirmation appears, then the card updates.

Slide-In Panels

A half-screen panel slides up (phone) or in from the side (web). The vehicle view stays partially visible behind it, maintaining context. The panel has a clear close button. Dismissing it returns to the vehicle view.

Request Addition (בקשת תוספת)

Garage discovers additional damage during repair and requests approval from the office.

Steps:

  1. Select moked — Pick which moked (damage area) needs additional work

  2. Take photos — Camera/gallery capture documenting the additional damage (optional, can skip)

  3. Voice notes & text — Record audio explanation and/or type notes. Can also edit parts/jobs/hours directly

  4. Review & submit — Summary of all changes. Submit sends to office for approval

What's sent: monday_id, photos, notes, parts/jobs/hours changes → POST /zohar/inspection/v2/request-additions

After submission: Tinsmith stays on the vehicle view. Office receives the pending approval (visible in "Needs My Attention" queue). Photos upload in the background.

Repair Photos (צילום תיקון)

Quick photo capture to document ongoing repair work.

Steps:

  1. Take photos — Camera opens immediately. Grid view with add/delete. Minimum 1 photo required

  2. Submit — Photos queued for background upload, associated with the vehicle automatically

What's sent: Photos tracked in SQLite, uploaded asynchronously to Monday.com repair files column.

Pre-Invoice (קדם חשבונית)

The appraiser's field approval step. The appraiser visits the garage, reviews the completed work against three sources: the app data (parts/jobs/hours), the printed proforma file, and the original appraisal they gave. They verify counts, adjust if needed, and approve.

Who: Appraiser (in the field, at the garage)

Steps:

  1. Review details — Shows all parts (with quantity deltas), jobs, and appraiser hours for the vehicle. Each item is editable — the appraiser can adjust counts based on what they see on-site

  2. Optional photos — Capture confirmation photos of the completed work

  3. Approve & submit — Appraiser confirms the work matches expectations. Updates sent to backend + Google Sheets sync (best-effort)

What the appraiser checks:

  • Parts: Do the actual parts match what was approved? Are counts correct?

  • Jobs: Was each job actually performed? Any changes needed?

  • Hours: Appraiser hours reconciliation

What's sent: Parts/jobs/hours deltas, photos → POST /zohar/inspection/v2/pre-invoice

Proforma Creation (יצירת פרופורמה)

Generates a proforma (price quote) document for the vehicle's repair work. Sends to Nesher invoicing system.

Steps:

  1. Editable table — Shows existing jobs, hours, and parts from Monday.com subitems. Each row has quantity and unit price fields. Can add new rows from the catalog (SKU lookup)

  2. Nesher card number — Required field linking to Nesher's accounting system

  3. Client selection — Choose billing client

  4. Submit — Creates new subitems on Monday.com if rows were added, updates tools column to "פרופורמה חדש לבדיקה" which triggers the server webhook → WebSocket → Nesher PC generates the PDF

What's sent: Nesher card number, client, new subitems (name, category, quantity, price, SKU) → Monday.com column updates + API calls

Vehicle Relocation (שינוע רכב)

Moves a vehicle between locations: to another garage area, to an external job provider, or back to the customer.

Steps:

  1. Select destination — Three options:

    • Garage (שלי דוד / הזוהר) → Select roof or ground level

    • External job (עבודות חוץ) → Select external provider

    • Client return (החזרה ללקוח) → Full delivery flow

  2. Driving mode — Animated trip dashboard with timer. User taps "הגענו!" (we arrived) on arrival

  3. Arrival handling (varies by destination):

    • Garage arrival: Simple confirmation → updates "איפה הרכב" column

    • External job arrival: Dialog with options (car stays / waiting) → updates external job subitem

    • Client return: 6-step photo sequence (exterior + interior) → signature capture → receiver details → updates all mokeds to "הסתיים חזר ללקוח"

Key features:

  • Session persistence — active driving sessions survive app restart

  • Pre-exit inspection auto-created if vehicle status is "מוכן ליציאה"

  • Client return includes syncfusion_flutter_signaturepad for customer signature

Full-Screen Flows

Complex multi-step workflows that need their own space. These open as a full screen but include a clear "← Back to Vehicle" breadcrumb.

Examples:

  • Pre-Exit Check — Multi-section QA checklist (cleanliness, systems), exit photos

  • Car Delivery — Verify mokeds, receiver details, photos, signature capture

  • Initial Appraisal — Vehicle profile, jobs selection, parts selection, hours, photos, review

The vehicle context is pre-populated — the user never re-selects the vehicle.

Standalone Flows

Unchanged from today. Used when the vehicle doesn't exist in the system yet.

Example: Car pickup from customer. Accessible via the existing home screen card and via a "+ New Pickup" shortcut on the dashboard.

16 March 2026