Signed in asUserRoleUserBadge noNot setStationNot setMy watchA WatchAccess statusApprovedPrivate data areauserCloud syncLocal onlyPlatformAndroid, iPhone, Web
Your overtime, daily work, leave, station, and watch entries are saved under your own account in this test build. The live version will store this securely in the database.
Setup
Ready checklist
Personal dataExport or restore my records
Exports and imports only the data saved under this account.
Help
Quick start
1Check your watch
Use My watch at the top to choose A, B, C, or D. The 28 Day and Month tabs will follow that watch.
2Record what you were on
Use Daily Work to save station and role for normal shifts. Use Overtime for extra days or nights.
3Add leave
Add Annual Leave or Winter Leave by date range, then review everything in Leave Overview.
4Report problems
Use Feedback if a date, time, watch, station, role, or screen does not look right.
Support summaryReady
Copy this if you need to send app details with a support request.
Monthly summary
This month
OT hours0 hrsOT entries0Days recorded0
Dashboard
Year view
Year OT0 hrsYear OT entries0Recorded days0
OT by month
Most common On
Upcoming duties
Irish public holidays
Public holidays
FN pay dates
Pay dates
Feedback
Report an issue or idea
0 reports
Install
Add the app to your device
Browser mode
iPhoneSafari
Open the app in Safari, tap Share, then choose Add to Home Screen.
AndroidChrome
Open the app in Chrome, tap the menu, then choose Add to Home screen or Install app.
ComputerChrome or Edge
Use the install icon in the address bar, or open the browser menu and choose Install app.
Go live
Security and launch readiness
LoginPrototype gate
Next live step: connect a hosted login provider so passwords and sessions are protected outside the browser.
User records0 users
No access requests yet.
Private dataPer user ready
Daily work, overtime, leave, stations, and watch settings are already separated by signed-in user in this test build.
Launch readiness0%
Setup in progress
Stable restore pointruntime-restore-1
Known-good copy saved before future changes.
Change ruleSmoke check before handover
Login, tabs, logout, 28 day, month view, and startup order are checked before testing.
Rollback pathRestore point ready
If a future update misbehaves, restore the saved build instead of guessing.
Pre-flight
Automatic launch checks
Checking
1
Roster app prototype
Watch schedules, leave, overtime, stations, holidays, pay dates, and admin flow are built.
2
Secure user accounts
Add real hosted authentication, owner admin access, approved users, and reset controls.
3
Cloud database
Move each user's entries from local test storage into private cloud records.
4
Test release
Invite a small group, test iPhone, Android, and web, then fix any real-world feedback.
Backend foundation
Supabase setup pack
Database schemaPrepared
Tables are defined for profiles, daily work, overtime, leave, ambo hours, admin audit events, and app settings.
User privacyPlanned
Each signed-in user only reads and writes their own records. Admin can manage access records.
Supabase projectNeeded
Create the hosted project, then run the setup SQL file to turn this into live storage.
1. Create Supabase project2. Run supabase-schema.sql3. Add project URL and public anon key4. Connect login and records to cloud tables
AuthReal user sign-in
Replace local access keys with hosted accounts, sessions, password reset, and owner admin roles.
PrivacyRow level security
Keep each member's daily work, overtime, leave, and ambo records private to their account.
MigrationMove prototype data
Export the migration pack, map records to hosted users, then import into cloud tables.
ReleaseSmall pilot first
Test web, iPhone, Android, admin approval, user privacy, and backup before wider sharing.
Step 1Owner check
Confirm admin login, user approval, 28 day view, month view, daily work, overtime, leave, ambo hours, and backup export.
Step 2Two-user privacy test
Approve two users from different watches, record sample entries, then confirm neither user sees the other's private records.
Step 3Small pilot group
Invite a mix of iPhone, Android, and web users across watches and stations. Record feedback before changing anything else.
Prototype data migrationExport live-ready data pack
Packages users, access records, current account overtime, daily work, leave, and backend settings for the cloud migration stage.
Backend connection not configured yet.
Cloud login bridge
Hosted account readiness
Check needed
Cloud test user
Create one hosted test account
Not created
Create one test user before switching the main login to cloud accounts.
Users to migrate0Daily work records0Overtime records0Leave records0
Local prototype data is ready to export before cloud migration.
Migration map
Local data to cloud tables
Preview
Cloud live check
Hosted setup readiness
Check needed
Backup check
Export readiness
Check needed
Owner audit
Admin and user data check
Check needed
Mobile check
Install and platform readiness
Check needed
Privacy test
Two-user data check
Not run
Launch checklist
Track go-live progress
0/8 done
Release notes
Test build history
Current build
Tester share pack
Invite pilot testers
Test release
Tester sign-off
0 tests
Pilot report
Sign-off summary
Testing issues
Issues to fix before live
0 open
Recommended next build stageThe backend setup file is now prepared. The next step is creating the hosted Supabase project and connecting this app to it.
Owner admin
Access and security
Platform supportAndroid, iPhone, Web
Built as a PWA so it can be installed from the browser on phones, tablets, and desktops.
Your roleOwner admin
You control access keys, user approvals, and user access once the app is connected to secure accounts.
Data separationPer user
Each user will have private records for overtime, daily work, stations, leave, and watch settings.
User access keysPer approved user
Each approved user gets their own key. New keys are generated when you approve or reset a user.
Owner admin keyDFB-ADMIN
Only the owner/admin should use this key to access admin controls.
Admin controls
Approve new usersSuspend accessReset individual keysReset admin keyKeep each user data private
Admin summary
Control centre
Ready
Cloud sync
User backup review
Check needed
User access
Pending and approved users
0 users
Admin activity
Access history
0 events
Security noteThis screen separates the owner admin key from individual user access keys. Real security still needs a hosted login service and database so keys cannot be bypassed in the browser.