Skip to main content
Back to Updates
Dev LogJanuary 27, 2026

Product Signals, Accessibility, and App Quality

Improved product signals, accessibility, configuration, and app quality so Protocol can keep getting more reliable as it grows.

Shipped

  • Product signals

    • Improved how Protocol measures core product flows during development
    • Made product telemetry easier to review before changes reach users
    • Expanded documentation around the events that matter for onboarding, workouts, and insights
  • Accessibility improvements

    • Introduced ProtocolModalDescription to improve screen reader context for data restoration and preferences flows
    • Enhanced PlateDetailsModal with semantic dialog descriptions and screen reader–friendly summaries
    • Refactored ExerciseAutocomplete and TimerDialogs to use DialogDescription and standardized modal semantics
    • Improved aria attributes, dialog structure, and button sizing across multiple components
  • Configuration + app quality

    • Updated Next.js config to skip type checks during builds for better Windows worker compatibility
    • Extended ESLint coverage to include generated service worker bundles
    • Added ESLint report outputs for improved code quality visibility
  • Design system + documentation

    • Added obsidian-glass.md documenting the Obsidian Glass design language
    • Added a UX/UI audit + Shadcn migration plan document
    • Updated backend, ERD, and feature docs to align with recent schema and Insights/Profile changes
    • Synced shallow index and current-state docs to reflect the evolving architecture

Why

  • Better product signals help catch confusing flows earlier
  • Accessibility improvements compound over time and are easiest to fix while surfaces are still evolving
  • Tight config and linting reduce friction as the codebase grows and contributors change environments

Notes

  • This is a maturity pass: fewer ad-hoc fixes, more intentional quality standards.

Next

  • Add minimal guardrails around product event quality
  • Continue migrating remaining legacy dialogs to shared modal primitives
  • Start measuring Insights engagement now that instrumentation is stable