Blagger milestones

Milestones describe the level of usefulness, safety and coherence Blagger is intended to reach. They are not promises to implement every desirable feature before moving on.

Beta 2 - Dependable for real use

Definition

Beta 2 should make Blagger dependable for the project owner's continuing daily use and responsible use by a small number of invited testers.

It should be:

  • safe enough to hold other people's real data;
  • coherent enough for a new user to understand its main model and workflows;
  • materially more useful for the project owner's own recurring work;
  • recoverable from foreseeable operational failures;
  • honest about its browser and JavaScript requirements.

The project owner is Blagger's primary and most experienced user. Repeated friction in her real use is valid product evidence and may justify Beta 2 work independently of tester demand.

Beta 2 does not require Blagger to be commercially complete, broadly marketable or polished to the standard of a mature public service. It does not require speculative features unsupported by observed user needs.

Inclusion tests

An issue is a good candidate for Beta 2 when at least one of the following is strongly true:

  1. It protects real data, privacy or account security, or prevents a serious correctness error.
  2. The project owner has repeatedly encountered the problem during normal use.
  3. A beta tester has encountered the problem during realistic use.
  4. It unlocks a valuable workflow that the project owner currently performs awkwardly or outside Blagger.
  5. Omitting it would make the description of Beta 2 as dependable for real use misleading.

The strongest evidence is a problem encountered in real use. An issue should not enter Beta 2 merely because a mature product might eventually be expected to have it.

Completion test

Beta 2 is complete when:

  • its remaining P0 and P1 issues are resolved or explicitly accepted with a documented reason;
  • production data is backed up off the Raspberry Pi and a restore has been tested;
  • authenticated use has a clear JavaScript requirement and known browser-history privacy risks have a proportionate mitigation;
  • the principal activity, period, timeline, search and navigation journeys are coherent on desktop and mobile;
  • defects repeatedly affecting the project owner's real use or encountered by testers have been addressed or consciously deferred;
  • the remaining backlog consists mainly of enhancements, broader product development and accepted limitations rather than obstacles to dependable use.

The milestone should then end. Further polish and new ideas belong in later milestones unless they expose a newly discovered serious defect.

Beta 1 - First usable invited beta

Released: 14 September 2026

Summary

Beta 1 established Blagger as a usable multi-user application which could be installed and tried by invited users while continuing to support the project owner's own time tracking.

Its delivered shape included:

  • verified multi-user database isolation;
  • activity totals, including descendant time;
  • recent activities based on activity timestamps;
  • search across activities and periods;
  • a canonical reverse-chronological timeline;
  • responsive activity-duration presentation on mobile;
  • installation as a Progressive Web App;
  • validation preventing future period times and support for long durations;
  • removal of activity and period content from production logs;
  • public guides and statements for initial use;
  • an initial app drawer and primary navigation suitable for release.

Outcome

Beta 1 made it possible to invite real users, observe how they understood Blagger and collect feedback from actual desktop and mobile use. It was an initial usable beta, not a claim that operational resilience, every security edge case or the wider product model was complete.