Skip to content

UX review: findings and follow-ups #262

Open

Description

@DeepDiver1975

Senior-UX-designer pass over the whole app, refreshed on 2026-10-16 against main (1ed810d). Struck-through items no longer apply (each says why). Items marked partly fixed now describe only the remaining gap. New findings from the refresh are marked 🆕. Items marked → #N have been split into their own issue, with a release milestone: #601–#604, #605, #650–#659 and #668–#670 in v0.9, #680 in v0.10. This issue stays in the Backlog as the umbrella; tick an item here once its split-out issue closes. Updated 2026-10-19: every v0.9 split (#601–#605, #650–#659, #668–#670) is closed and ticked below. The theme half of #605 moved to #680 (v0.10), which is the only split still open.

Context

LageBuch runs live in the ELW during an active Einsatz, alongside Atemschutz countdowns, a Rückzugsalarm and spoken ILS reminders. Every finding is judged by one question: does this cost seconds or invite an error when someone is stressed, standing and half-watching a radio?

Done

Atemschutz (safety-critical) — highest priority

Cross-cutting

Kräfte

Aufgaben

Führung & Funktionen

  • Partly fixed: who holds role X. The default filter shows only running assignments, which works as a holder list. There is still no summary of unfilled Stammdaten Funktionen, and nothing shows the holder outside this tab.
  • "Alle Funktionen" interleaves ended and running rows in insertion order, told apart only by BIS "—". 🆕 → Funktionen: every running assignment card on a phone shows "BIS —" #668 Phone card bug: ToDisplay is never null, so every running card shows "BIS —" (RolesView.axaml:352-353). Fixed by Funktionen: every running assignment card on a phone shows "BIS —" #668; the interleaving remains.
  • Partly fixed: near-duplicate Funktion names. Case and whitespace now snap to the Stammdaten spelling, and unknown names get an amber hint. "EL" vs "Einsatzleiter" still splits the history.
  • → Funktionen: correcting the name keeps the previous person's phone and Funkrufname #656 The transfer prefill needs an exact name match and fills only blank fields. 🆕 If you pick the wrong person and then correct the name, the first person's phone and Funkrufname stay, with no warning.
  • 🆕 A Funktion cannot be ended without a successor (RolesViewModel.cs:373-376).

Stammdaten

Workspace / sharing

CO-Messprotokoll

Checkliste / Einsatzdaten / Dateien

Positives worth keeping

The ETB "record it fast" flow; TransferRole's atomic handover; the join-failure taxonomy with its cancellable connecting state; the ConfirmDialog's focus on ABBRECHEN; and the keystroke budgets in KeystrokeBudgetTests.


🤖 Generated with Claude Code

Activity

  1. added
    enhancementNew feature or request
    uxUser interface and usability
    trackingUmbrella issue collecting findings or sub-tasks; not a single task
    on Sep 21, 2026
  2. DeepDiver1975 commented on Oct 16, 2026

    @DeepDiver1975
    ContributorAuthor

    Refreshed the body against main @ 1ed810d. Three read-only audits checked every open item against the current code, with file:line evidence, and did a first pass over the views the original review never saw (Checkliste, Einsatzdaten, CO, Workspace/Sharing, TaskDialog, F1 overview).

    • Struck as obsolete: keyboard support (epic: keyboard-only operation (tracking) #545), missing AutomationProperties (feat(a11y): AutomationProperties labeling + keyboard navigation for Kräfte flyouts #283), single-click role-ending, ETB icon buttons.
    • Rewritten as partly fixed: 10 items now describe only the gap that remains.
    • New (🆕): 16 findings. The most urgent is the Atemschutz double-click: ABGENOMMEN appears in the slot RÜCKZUG just left, so one double-click ends a Trupp's monitoring with no confirm and no undo. Also new: an app-wide raw ex.Message leak into German UI text, the Kräfte Stärke flyout leaking uncommitted values into the grid row, and sharing that can be stopped without a confirm.

    🤖 Generated with Claude Code

  3. DeepDiver1975 commented on Oct 19, 2026

    @DeepDiver1975
    ContributorAuthor

    Split the remaining trust findings into their own issues.

    v0.9 — Security and trust:

    Backlog: #657 (Stammdaten blocked without a readable reason), #658 (sticky and overwritten task timer), #659 (due task chimes once).

    The rule for picking was the one v0.9 already applies (#601–#604): the app must not lose or misrecord what someone typed, must not act irreversibly on a mis-tap, and must show failures instead of hiding them. Every item was rechecked against main @ ce084dd before splitting. The header also now places #605 in v0.10, where it is milestoned.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttrackingUmbrella issue collecting findings or sub-tasks; not a single taskuxUser interface and usability

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions