Repository navigation
docs(ux): audit Studio's interface against usability principles - #28
Merged
Merged
Conversation
Finds that Studio has no interaction primitive: picking something has no consistent result and screen regions have no fixed meaning. Adds the evidence, a scorecard, a proposed rule and tests that can falsify it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
ui-ux-audit-report.md, a UI/UX audit of Studio at5cd5d53.Main finding: Studio has no interaction primitive. Picking something can open a tab, fill a side panel, split the current tab, change the tab's content or change the whole window's scope, depending on where you are. Screen regions have no fixed meaning, so results can't be predicted.
The report also covers the object model, vocabulary, navigation, scope and safety signals, and message severity. It includes a scorecard, what to keep, a proposed rule with an object-by-object table, an order of work, and tests that could prove the audit wrong.
Limits: no users were tested. The evidence is code, specs and offscreen renders on the sample graph, and the rule and glossary are proposals. Quotations and external links should be checked before they are reprinted.
Documentation only, with no code changes.
🤖 Generated with Claude Code