Applied screens
Component states in context
Inspect real fields, saving, navigation and progress components at high resolution.
On this page
Capture context
| Area | Evidence |
|---|---|
| States | Focus, menu open, saving, complete/incomplete and collapsed/expanded where captured |
| Framing | Native component containers; popup bounds measured before crop |
| Content | Real course text; isolated generic state labels are specimen-only |
| Limit | Not every source state has a populated capture |
How to inspect
- Use the Desktop/Phone controls where both exist. TeachKit’s source appearance is light only.
- Open an image for fit-to-view inspection, then Actual pixels or Open original for detail.
- Component details and complete screens have separate filenames and recorded intrinsic dimensions.
- Compare text, focus, menus and media against the source; do not treat a pictured state as proof of live persistence.
Examples from the app
Actual TeachKit UI with Thomas McGee’s course content. Session, progress and connection specimens are simulated; no student data or live changes. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision d8cf23d0a329 · Documentation v0.1