Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/juanmatz/inspection-form-euroautos/llms.txt

Use this file to discover all available pages before exploring further.

Answers to the most common questions about the Euroautos Inspection Form. If you have a question that isn’t covered here, please open an issue on the project repository.
The Euroautos Inspection Form is tested and supported on the following browsers:
BrowserMinimum versionNotes
Google Chrome110+Recommended for desktop and Android
Microsoft Edge110+Chromium-based; full feature parity with Chrome
Mozilla Firefox115+Fully supported; IndexedDB behaviour may differ slightly
Apple Safari16.4+Required for iOS devices; some PWA features limited on earlier versions
Samsung Internet20+Supported on Samsung Android devices
Browsers based on older rendering engines (Internet Explorer, legacy Edge) are not supported and will display a compatibility warning. For the best experience — particularly for camera access and offline capability — use an up-to-date version of Chrome or Edge on desktop and Android, or Safari 16.4+ on iOS.
Yes. The Euroautos Inspection Form is fully responsive and designed to be used on mobile phones and tablets by technicians on the workshop floor. The layout adapts to smaller screens, and all checklist interactions, photo capture, and signature pad features work on touch devices.For the best mobile experience:
  • Install the app as a PWA (Progressive Web App). On Chrome for Android, tap the three-dot menu and select Add to Home screen. On Safari for iOS, tap the Share icon and select Add to Home Screen. This gives the app a dedicated launcher icon, full-screen mode, and more reliable offline access.
  • Use a tablet (10” or larger) if inspectors need to review multiple sections side by side or attach several photos per item.
  • Ensure HTTPS — camera access on mobile browsers requires the app to be served over a secure connection.
Nothing is lost. The app stores all data locally in the browser’s IndexedDB storage as the inspector works, so losing internet connectivity mid-inspection has no impact on the current session.Here is what happens when you go offline:
  1. Ongoing work continues uninterrupted. You can complete sections, add notes, take photos, and submit the inspection without any interruption.
  2. Changes are queued. Any saves that would normally sync to the backend are written to a local sync_queue instead.
  3. Sync resumes automatically. When the browser detects that connectivity has been restored, it processes the queue and sends all pending mutations to the backend in the background.
  4. No action required. Inspectors do not need to manually trigger a sync. A status indicator in the app header shows whether all data has been successfully synced.
The only scenario where data could be lost is if the browser’s local storage is cleared before syncing occurs. See Data Storage for details on preventing this.
Not in the current version. Inspections are owned by a single device and inspector. If two technicians attempt to edit the same inspection simultaneously from different devices, the last sync to reach the backend will overwrite earlier changes.The recommended workflow for multi-technician inspections is:
  • Assign individual sections to specific technicians within the app (the section assignment feature is available in the Settings screen).
  • Each technician completes their assigned sections on their own device.
  • The lead inspector reviews and merges the sections before submitting the final record.
Real-time collaborative editing with conflict resolution is planned for a future release.
Use the built-in export and import flow:
1

Export from the old device

On the old device, go to Settings (⚙ icon) → Almacenamiento → Exportar datos. The app will download a JSON file containing all local inspections and their attached photos.
2

Transfer the file

Move the exported .json file to the new device — via email, a USB drive, cloud storage, or any file transfer method.
3

Import on the new device

On the new device, open the app and go to Settings → Almacenamiento → Importar datos. Select the JSON file. The app will load all inspections into the local IndexedDB store.
4

Verify the import

Navigate to the inspection list to confirm all records appear correctly. Attached photos should also be visible within each inspection.
If backend sync is enabled and both devices share the same VITE_API_URL, inspections will also be accessible on the new device once they have synced to the server — no manual export needed.
Yes, with a configuration change. Inspection sections are defined in the src/config/sections.ts file. Each section entry specifies a type key, a display label, an icon, and an array of ChecklistItem templates.To add a new section:
  1. Add a new entry to the sections array in src/config/sections.ts with a unique type key.
  2. Define the checklist items for the section, marking any mandatory items with mandatory: true.
  3. Optionally, add a translated label for the section in the language files under src/i18n/.
  4. Rebuild and redeploy the app.
Custom sections are fully compatible with the existing JSON schema and sync pipeline. Changes to sections only affect new inspections; existing inspections retain their original section structure.
Removing a section type from the configuration does not delete historical inspections that contain that section. Those inspections will still display correctly, but the section will appear as “Unknown section type” in the section header.
The app currently ships with two languages: Spanish (es) as the default, and English (en). The active language is set via the VITE_DEFAULT_LOCALE environment variable at build time.To change the default language to English, set the following in your .env file and rebuild:
VITE_DEFAULT_LOCALE=en
Inspectors can also switch the language at runtime via Settings → Idioma without requiring a rebuild. The selected language is persisted in localStorage and will be remembered across sessions.To add a new language, copy the src/i18n/es.json file, rename it to the target locale code (e.g. fr.json), translate all string values, and register the new locale in src/i18n/index.ts. Contributions of new language files are welcome via pull request.
By default, the app accepts photos up to 5 MB each after compression. The maximum is controlled by the VITE_MAX_PHOTO_SIZE_MB environment variable.Before storing a photo, the app automatically:
  1. Resizes the image to a maximum of 1920 × 1080 pixels (maintaining aspect ratio).
  2. Recompresses it as JPEG at 85% quality.
  3. Rejects the image if the resulting file size still exceeds VITE_MAX_PHOTO_SIZE_MB.
In practice, most device camera photos will be compressed to 0.5–2 MB per image. For a typical inspection with 15–20 photos, expect 10–30 MB of total photo storage.
Base64 encoding adds approximately 33% overhead compared to the raw binary size. A 2 MB JPEG photo will consume approximately 2.7 MB in IndexedDB. Keep this in mind when estimating storage requirements for high-volume workshops.
The PDF inspection report is generated in whatever language the app is currently set to. To produce a report in English:
  1. Switch the app language to English via Settings → Idioma → English.
  2. Open the inspection you wish to export.
  3. Tap Generar informe / Generate report.
  4. The downloaded PDF will use English labels, section names, and status text.
If you need reports in multiple languages for the same inspection, switch the language, generate the report, then switch back. The underlying inspection data is language-neutral; only the display labels change.
Local-only installations (without VITE_API_URL) do not have automatic backup. Data lives exclusively in the browser’s IndexedDB and will be lost if:
  • The browser’s storage is cleared manually.
  • The device is lost, stolen, or factory-reset.
  • The browser decides to evict storage for an origin that hasn’t been visited recently (this is more common on mobile browsers).
To protect your data:
  • Enable backend sync by setting VITE_API_URL to point to your Euroautos backend instance. This is the most reliable option.
  • Export regularly using Settings → Almacenamiento → Exportar datos and save the JSON file to a network drive or cloud storage.
  • Install the app as a PWA — browsers are less likely to evict storage for installed PWAs than for regular visited sites.
Workshops handling insurance claims or regulatory inspections should always use a backend with proper database backups.
1

Export your data first (recommended)

Before deleting anything, go to Settings → Almacenamiento → Exportar datos to download a backup of all local inspections.
2

Open the clear data dialog

Go to Settings → Almacenamiento → Eliminar todo and confirm the action in the dialog.
3

Reload the app

The app will clear the inspections, photos, and sync_queue stores and reload automatically. You will see an empty inspection list.
Alternatively, you can clear storage through the browser:
  • Chrome / Edge: Settings → Privacy and security → Site settings → <your app URL> → Storage → Clear data.
  • Firefox: about:preferences → Privacy & Security → Cookies and Site Data → Manage Data → find the app URL → Remove.
  • Safari: Settings → Safari → Advanced → Website Data → find the app → Delete.
Yes. The Euroautos Inspection Form exposes a REST API sync endpoint (when the backend is deployed) at POST /api/v1/inspections that accepts standard inspection JSON payloads. Workshop management systems (WMS) can consume this endpoint to import completed inspections automatically.For outbound integration (pushing inspection data from Euroautos to your WMS), the backend supports configurable webhooks: when an inspection reaches the completed or approved status, a POST request with the full inspection payload is sent to the configured webhook URL.Set the webhook URL in the backend environment configuration:
WEBHOOK_INSPECTION_COMPLETED=https://your-wms.example.com/api/inspections/inbound
The webhook payload is identical to the Inspection JSON Schema, making it straightforward to map fields to your WMS’s data model.For systems that cannot accept webhooks, the JSON export file (from Settings → Exportar datos) can be ingested as a batch import using the WMS’s bulk import feature, if available.

Build docs developers (and LLMs) love

Get started for freeTalk to us