Work stations

What happens the second you open it

The app loads straight into a project creation screen. No tutorial, no welcome tour, just a blank form asking for a project name. The interface is minimal — a few buttons, a clean white background, and no obvious onboarding flow. This is a tool built for managers who already know what they want to do. The first step is naming your project, and from there, the app guides you through a linear setup process: create workstations, add employees, and then assign people to shifts. The entire experience feels like filling out a spreadsheet on your phone. It is not flashy, but it gets straight to the point. For a manager with a team to schedule, that directness is a feature, not a flaw.

How the access levels and shift allocation work together

The app offers three access levels: Admin, Manager, and Viewer. The Admin has full control — they can create projects, add or remove workstations, and manage the employee list. Managers can assign employees to shifts but cannot change the underlying structure of the project. Viewers can only see the schedule; they cannot make any changes. This hierarchy is crucial for real-world use. In a healthcare setting, for example, a head nurse (Admin) sets up the wards and staff list. Shift supervisors (Managers) then allocate nurses to specific wards for each day and shift. Regular nurses (Viewers) open the app to check where they are assigned. The system works because the access levels mirror the organizational structure. The Admin builds the framework, the Manager fills in the details, and the Viewer consumes the information. This three-tier approach prevents chaos. Without it, anyone could accidentally reassign staff or delete a workstation. The app enforces order by limiting what each role can do.

The real-world performance: what works and what does not

The app performs reliably for its core function: scheduling. Creating a project, adding workstations, and populating the employee list takes less than five minutes for a small team. The shift allocation interface is straightforward — you pick a workstation, a day, a shift (morning, afternoon, night, or custom), and then select employees from a dropdown list. The app saves each assignment instantly. There is no lag, no crashes during testing, and no obvious bugs in the allocation logic. However, the app does have limitations. The changelog mentions "minor bug fixes", which suggests that issues exist, even if they are not visible during casual use. The lack of a detailed changelog is a drawback — users have no way of knowing what was actually fixed. The app also lacks any analytics or reporting features. You can see the schedule, but you cannot export it, print it, or generate any kind of summary report. For a manager who needs to share the schedule with upper management or HR, this is a significant gap.

The final technical detail: storage and data management

The app stores all project data locally on the device. There is no cloud sync, no backup option, and no way to export the data. This means that if you lose your phone or uninstall the app, all your schedules, workstations, and employee lists are gone permanently. The app does not offer any data recovery mechanism. The only way to share the schedule is to show someone your phone screen or take a screenshot. For a team scheduling tool, this is a major limitation. The app also does not integrate with any calendar apps or messaging platforms. You cannot automatically notify staff of their assignments — they have to open the app and check manually. This makes the app suitable for small teams where the manager can personally communicate the schedule, but it falls short for larger organizations that need automated notifications and data backups. The app's simplicity is its strength, but that simplicity comes with real trade-offs in functionality and data safety.