Ankiety

Why doesn't the app have a backend?

Because the survey includes a health questionnaire — blood clots, pregnancy, heart conditions, cancer. That's health data, a special category of personal data under GDPR Article 9, subject to a stricter regime than a plain name.

Having no server isn't a cost-saving move here — it's a way to sidestep that entire class of problems. Surveys stay in the reception's browser IndexedDB, so guest data never leaves the device: there's no database to leak, no server to secure, no data processor to appoint. As a bonus, the app keeps working when the guesthouse's internet drops, and hosting costs nothing, because it's static files.

Why a PWA, not a native app?

Reception installs it straight from the browser — no store, no developer account. Updates land the moment it's reopened — I'm not waiting on review, and I'm not asking anyone to click anything.

Why does export produce a ZIP, not a single PDF?

Reception archives surveys in batches, not one at a time. The bundle contains PDFs named by client surname and treatment date, a dane.csv for spreadsheets, and a backup.json for restoring the app's state. Since the data only lives in the browser, the backup isn't an extra — it's what makes this architecture honest.

Why did .htaccess need an AddType for .mjs?

Apache on OVH doesn't map a MIME type for .mjs, so the browser refused to run the pdf.js worker — a module served with an empty MIME type gets blocked. The second rule disables caching for sw.js: without it, PWA updates don't land, because the browser keeps holding onto the old service worker. Neither shows up in a screenshot, but without them the app simply doesn't work.