The short version
SSD Manager comes directly from my role in the Schulsanitätsdienst at school. It is not a hypothetical productivity tool: it is built around duty plans, availability, absences, announcements, roles, and the operational details of coordinating a real group of student first-aiders.
Inside the project
Selected screens and details.
A closer look at the product in its current form.
Why I built it
I was organizing the workflow before I started coding it.
Our school first-aid service involves roughly 29 active student first-aiders. Coordinating who is available, who is assigned, what changed, and who needs to know is real work. Because I help with that organization, I could see exactly where a tool could remove friction.
What exists
The app follows the service from duty plan to notification.
The Flutter app and PHP/MySQL backend cover duty planning, sign-ups, absences and sick reports, announcements with attachments, user administration, role-based permissions, notifications, device sessions, backups, and school-scoped data. The repository also contains store-ready screenshots and deployment documentation.
- Student first-aiders, leadership, teacher supervision, and secretariat roles see different actions.
- Closures, special events, capacity, and history are part of the duty model.
- Security, privacy, backups, and account deletion are treated as product work.
Things that went wrong
Real-device testing found the failures a diagram could not.
Date formatting broke because a shared locale was not initialized. A production-account login issue turned out to be an app build pointing at a local API. File-provider duplicates disrupted an Android build. Each failure forced the project to become more explicit about environment selection, time zones, refresh behavior, and release checks.
Where it is now
Already useful, still shaped by the service.
SSD Manager is in active development as an internal, real-world tool. The core app and backend exist; I continue to refine the workflow around the actual service rather than presenting it as a finished commercial product.