Designing Interfaces¶
Tidwell, J. (2010). Designing Interfaces: Patterns for Effective Interaction Design. O'Reilly Media.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Design Patterns
This sourceCatalogues UI/interaction patterns for desktop, web, and mobile. Cited inline in §5 (tier B — supports the HCI/UI-pattern-library breadth claim).
- Gestalt Principles
- A well-formatted code file exploits the gestalt principles consistently and structurally — the same operational use of proximity, similarity, continuity, and closure that Tidwell (2010) catalogues as core UI patterns in Designing Interfaces applies directly to code legibility.
This sourceCatalogues UI patterns whose effectiveness rests on operationalized gestalt principles (proximity, similarity, continuity, closure) for interface organization across desktop, web, and mobile.
- A well-formatted code file exploits the gestalt principles consistently and structurally — the same operational use of proximity, similarity, continuity, and closure that Tidwell (2010) catalogues as core UI patterns in Designing Interfaces applies directly to code legibility.
Mechanisms¶
- Summary-Detail View
- Its strength is browse-and-inspect at scale: a user keeps an overview of the whole set while pulling the full detail of any one item on demand and returning to the set — the master–detail pattern that makes large collections navigable without loading or showing everything.
This sourcePresents Overview Plus Detail as keeping an overview visible while users inspect selected details without displaying all detail at once.
- Its strength is browse-and-inspect at scale: a user keeps an overview of the whole set while pulling the full detail of any one item on demand and returning to the set — the master–detail pattern that makes large collections navigable without loading or showing everything.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:c1363b4600c3 · see in the full table