Veldriq Web vs Veldriq Field
Veldriq Field
Screen path for the PWA: office CMS command palette Field (browser). Screen path for this product: native Welcome back → Today. They do not share a binary, a Drift database, or a marketplace SKU.
Preconditions
Section titled “Preconditions”| You want | You need |
|---|---|
| Office planning, invoices, portal, public booking | Veldriq Web (veldriq) |
| Browser technician client | Field PWA (ships with Web) |
| Native Android / iOS technician app | This product and an eligible Web backend |
Native Field requires an eligible Veldriq backend (same deployment you license Field on). Field PWA uses the same login origin as the office CMS and does not need this Flutter package.
| Surface | Veldriq Web | Veldriq Field |
|---|---|---|
| Office CMS | Yes | No |
| Customer portal | Web | No |
| Public booking | Web | No |
| Field PWA | Included | No |
| Native technician app | No | Yes |
| Flutter source | No | Yes |
| Offline native DB (Drift) | PWA has a different offline mechanism | Yes (schema v4) |
| Separate marketplace item | Veldriq Web | Veldriq Field |
| Creates work orders | Yes (office) | No |
| Closeout label | PWA: Complete appointment | Native: Complete job |
| Van consume online | PWA can require sufficient stock | Flutter always queues; offline replay may go negative |
What works / does not work
Section titled “What works / does not work”| Native Field | Field PWA | |
|---|---|---|
| Home-screen icon / splash | Compiled in the binary | Browser chrome |
| Offline photos | Queue on device, then upload | Different PWA mechanism |
| Office Complete on the work order | No | No (office CMS only) |
Admin setup (technicians, assignments, licence) lives in Veldriq Web. Technician execution on the phone is this documentation.
If someone installed only Web and expected this app: activate Field, compile this source, and assign appointments. The PWA is not a substitute binary.