ATTENDR
Giving Attendr a clearer home.
Looking back at the July website rebuild, with real interface screenshots and a more complete route into the product.
- WORK DATED
- WRITTEN
A look back at this stage of the project, written later from the development record. Product details describe that point in time.
Show the thing people will use
Attendr is a shared presence board: staff status, location, return times and comments in one place. A short description can explain that, but the dashboard makes the idea much easier to understand.
The website history for 5 July records a complete rebuild covering pricing, payment wiring, screenshots and application builds. It also records a Windows version update that day. This was work on how the product was presented and reached, alongside the application itself.
Different screens explain different jobs
The dashboard answers the everyday question of who is where. The kiosk view brings that information to a shared screen. Administration pages show how an organisation manages departments, locations and statuses.
Showing those screens gives the explanation something concrete. It helps a visitor connect the features to the work they need to do, instead of asking them to imagine an interface from a list of claims.
The website belongs to the product experience
An application can be useful while the explanation around it still needs work. The website has to help someone understand its purpose, decide whether it fits their environment and find a sensible next step.
This rebuild is one dated point in Attendr’s development, rather than its origin story. The project continued to change afterwards. Looking back at it now, the useful thread is the same: make the software visible, then make the route into it clear.