Filmreif: internal app for three branches
Internal PWA for three branches: orders as tickets, team feed, cover. In internal testing, with operation and privacy thought through from the start.
Three branches, one team, one shared interface: orders as tickets, a team feed for actions and information, a cleaning schedule and cover for absences. Built for the phone in the shop, not for a desk.
The app is in internal testing. This page therefore shows how it is built, not how it holds up over months of use.
Starting point
What was needed was one shared interface for all three branches: customer orders as a traceable process, a feed for actions and information, a cleaning schedule, and a cover rule that does not depend on who happens to pick up the phone.
Solution
The result is an internal progressive web app for phone and desktop. Customer orders become tickets with status and ownership. Team feed, actions, cleaning schedule and cover for absences come on top, with notification on the device.
Underneath sits a React interface built with Vite, a Fastify API, PostgreSQL, background jobs through a queue, and Web Push. The application runs on a server in Germany; only the web server with HTTPS is reachable from outside.
Operation and data protection
Privacy is part of how it is built, not a chapter at the end. Customer data in tickets is anonymised automatically after a configurable period; that run is a job and is logged. The audit log records events without document content and without secret fields. Logs contain no customer data.
Operation is designed in: a nightly backup, a regular restore test and a documented full restore. On top, two-factor login for administration, upload checking before storage, hardened operation and a server in Germany.
That is built and tested. How it behaves over months only shows after launch; that is why this page says internal testing.
How it was built
I built it AI-assisted in sprints, with cross-checking. Before the introduction the system was reviewed, and rework happened before launch. Before every release a verification chain runs types, lint, tests, backup test and performance budget; end-to-end tests run on iPhone and Android.
Result
An internal app for three branches with the functions named above, ready to use and in internal testing. What it delivers shows after launch, not on this page.
Limit
The app is internal and not publicly accessible, so screenshots show demo data. This page does not show any effect in numbers, nor that the same model fits another business. Anyone who wants to see the app gets a guided look at the demo data in a call.
More
How software is built here is described under Custom software & apps. The box “AI-assisted, but not unchecked” there describes the verification chain. The interface as its own topic: Interfaces & modules.