How to Think About UX for Windows Apps - A Decision Table for ToC, ToB, Monitoring, Field Terminals, and Tray Tools

Five things to decide first

Before worrying about how “modern” it looks, settle these:

1. Who uses it (beginners, power users, mixed)
2. Where it is used (desk, field, factory floor, reception)
3. What they operate it with (keyboard, mouse, touch)
4. How much they use it (first run only, daily, all day)
5. What a mistake costs (mild, severe, dangerous, audited)

Decision table by use case

For ToC utilities

• Usable as soon as it launches
• Limit primary actions to one or two
• The empty state should not feel cold
• Do not surface every setting up front

That said, power-user tools like photo editors, video editors, and investment analysis apps are different. They prioritize efficiency and density.

For ToB data entry

• Every feature reachable from the keyboard
• Easy to move back and forth between list and detail
• Filters and sort order persist
• Show errors inline, not in dialogs

The natural navigation is “feature categories on the left, list in the middle, detail on the right.”

For ToB monitoring and operations

• Anomalies are obvious at a glance
• Show state with color + text + icon + timestamp (not color alone)
• Confirmation dialogs use specific button labels (“Delete”, not “OK”)
• One click to logs and history

For field terminals

• Buttons large enough to hit reliably
• Aim for one purpose per screen
• Do not rely on hover (touch has no hover)
• Prefer selection or scanning over free text input

Note: ToB does not automatically mean high density.

For power-user tools

• High information density
• Frequent actions stay close, secondary features can sit deeper
• Layouts can be saved
• Strong Undo/Redo

If you bury everything in menus to be “beginner-friendly”, power users wear out.

Choosing a navigation pattern

UX items you cannot skip

1. Keyboard-complete - Tab order, visible focus, Enter/Space support
2. Survives text scaling and contrast themes - avoid pixel-fixed layouts
3. No dialog spam - field-level errors go inline
4. Multiple paths to important commands - button, context menu, shortcut
5. Recoverable from mistakes - Undo, autosave, preserve in-progress edits

Common design mistakes

• Assuming “ToB = dense, ToC = light”
• Building hover-only interactions (unusable on touch)
• Conveying state with color only
• Putting every validation error in a dialog
• Building fixed-size layouts

Eight questions to answer before you start

1. Who uses it - sets density and vocabulary
2. Where it is used - sets button size and input method
3. What they operate it with - sets Tab order and shortcuts
4. How much they use it - discoverability vs. efficiency
5. Cost of a mistake - need for confirmation flows and Undo
6. Information per screen - card-based or list-driven
7. Customization needed - column picking, layout saving
8. Accessibility requirements - text scaling, contrast, screen readers

Summary

UX is not decoration. It is designing for “can this person, in this place, with this input method, work without getting stuck?”

• Use standard controls as they come
• Primary actions complete from the keyboard
• No dead ends with touch or assistive tech
• Multiple paths to important commands
• Recoverable from mistakes