Technical specification

The Engine

The diagram shows a proposed architecture. The current demo stores simulated signals locally in IndexedDB; Service Worker and server sync are not active.

Lighthouse demo values

The displayed 100/100 scores are demo targets, not measured results. A Lighthouse test of the published site is still needed.

100

Performance

Target · not measured

100

Accessibility

Target · not audited

100

Best Practices

Target · not audited

100

SEO

Target · not audited

Architecture diagram · data flow

01

HTML5 Browser APIs

Location data is simulated in this prototype; real browser sensors are not queried.

02

Service Worker interceptor

Proposed extension: a Service Worker could cache navigation and assets. Not active yet.

03

IndexedDB via Dexie.js

Every record is persisted locally in a transaction and flagged with a synced marker. The queue survives reloads, tab switches and app restarts.

04

Serverless Supabase endpoints

Proposed extension: server-side sync. For now, queued records are only marked as synced locally; no upload.

osc_data_flow.svg
HTML5 APIsGeolocation · StorageService WorkerFetch InterceptorIndexedDBDexie · osc-field-labSupabaseServerless EndpointConcept: server sync · local status change only

Specification in detail

Stack & budget

Rendering
SSR + hydration, file-based routing
Persistence
IndexedDB (Dexie.js) + LocalStorage
JS budget
Target, not measured
Fonts
self-hosted, variable subsets
Images
no raster assets on the critical path
Interaction
0 ms transition and animation delay

Privacy by Design (GDPR)

Third-party scripts
none in demo code
First-party cookies
none in demo code
Tracking / analytics
not embedded
External fonts
not embedded
Telemetry upload
not implemented
Telemetry storage
device only
Book a B2B architecture audit with MyQuests