Car service mobile APP

Mobile app (Android + iOS) for car workshop — diagnostics, vehicle intake & electronic acceptance protocol, communication, parts & job tracking (MVP)

Budget
$300 fixed-price (MVP). Monthly hosting/API costs paid separately.

Project overview
We need an MVP cross-platform mobile app to streamline vehicle intake, manual diagnostics, mechanic ↔ office ↔ client communication, parts list sharing, time tracking and vehicle history. Core feature: electronic vehicle intake / acceptance protocol with multiple photos, checklist and dual signatures (mechanic + client) captured on the mechanic’s device and exported as a PDF with company header/logo. App should auto-translate UI/messages to the device language where possible.

Target users

• Workshop admin / office staff

• Mechanics

• Clients (vehicle owners)

Platforms

• Android and iOS (cross-platform: Flutter or React Native preferred)

MVP scope (deliverable for $300)

• Authentication & roles: admin, mechanic, client (email/password; OTP optional)

• Job & vehicle intake:

• Create job: VIN/registration, make/model, mileage, client info

• Intake screen with checklist (client will supply checklist/template)

• Capture multiple photos (exterior/interior/odometer) with timestamps and uploader metadata

• Capture signatures for mechanic and client on the mechanic’s device

• Generate & store PDF acceptance protocol (fields + photos + signatures + company header/logo/legal text) in job history; option to share/send PDF (email/share link)

• Offline capture and sync when online

• Diagnostics (MVP minimal): manual entry/import of fault codes and parameters

• AI decoding: cloud AI endpoint decodes fault codes into plain-language descriptions + inspection checklist (cached)

• Mechanic workflow & time tracking:

• Start/stop timer per job; basic labor cost calculation (default placeholder “xxxxx”; admin-configurable)

• Parts list & ordering:

• Create parts list; share via WhatsApp/system share or export CSV

• Messaging:

• In-app text messaging per job between workshop and client; auto-translation to device language (via translation API; cache translations)

• Media & documents:

• Photos and short videos (≤20s) upload; basic compression before upload

• Store invoices/docs (PDF/images)

• Vehicle history: consolidated timeline of jobs, media, PDFs, dates, mileage

• Admin: assign mechanics, configure labor rate

• Security: HTTPS, secure storage, basic role access control

Out of scope for $300 (can be phased later)

• Native OBD-II hardware integration (Bluetooth/Wi‑Fi)

• Payments/subscriptions / marketplace

• Complex offline conflict resolution or heavy AI hosting

• Extensive custom backend beyond recommended serverless setup

Recommended tech (developer to justify)

• Mobile: Flutter or React Native (cross-platform)

• Backend: Firebase (recommended for rapid MVP) or Supabase

• PDF generation: client-side library or serverless function

• AI/translation: OpenAI / Google Translate / Azure Translate (cache results)

• Media storage: Firebase Storage or S3-compatible storage with lifecycle rules

Deliverables

• Android + iOS app source code and build instructions

• Backend configuration notes (Firebase or chosen)

• Documentation: setup, how to configure AI/translation, how to use intake protocol template

• Example generated PDF from a sample intake

• Short demo screenshots/video of main flows

Timeline
Suggested 4–7 weeks. Milestones example:

1. Requirements confirmation, intake template & UX screens — 15%

2. Core: auth, job creation, intake UI, photo & signature capture, PDF generation & storage — 50%

3. Timer, manual fault entry, AI decoding integration, parts share, messaging, history — 25%

4. QA, docs, final builds — 10%

What to include in your proposal (required)

1. Confirm if you can deliver the MVP for $300 (yes / no). If no, state minimum price.

2. Preferred cross-platform framework (Flutter or React Native) and why.

3. Recommended backend (Firebase or Supabase) and why.

4. Estimated monthly hosting/API costs for light usage (Firebase/Supabase, storage, translation/AI).

5. Timeline and milestone breakdown fitting the budget.

6. What exactly will and will not be delivered for $300.

7. Portfolio / links to similar apps or relevant work.

8. Communication cadence, availability, and post-delivery support terms.

Assets I will provide to the selected developer

• Intake protocol template (form fields & checklist)

• Company details and logo for PDF

• Default labor rate placeholder (“xxxxx”)

Payment terms

• $300 fixed for the MVP (paid per agreed milestones). Monthly hosting/API costs billed separately (developer should list estimated monthly costs).

How to apply
Submit a short proposal answering points 1–8 above. Keep proposal concise and include any questions you need answered to start.