About Desktop Amberbase
Why we exist
Desktop applications still carry the work of traders, editors, technicians, and operators who cannot afford a browser tab that forgets their place. Yet many product teams inherit windowed clients that feel awkward to use and expensive to change. Desktop Amberbase was founded to give those teams a clear outside reading — pairing interface critique with maintainability judgment.
Origin
The practice began in Chiang Mai after years of reviewing native and cross-platform clients for regional product companies. We noticed the same pattern: UX research decks that never met the code, and architecture reviews that never watched an operator struggle with a modal. The consulting offer stitches those two lenses together on purpose.
Who you work with
Engagements are led by consultants who have shipped desktop UI themselves — Qt, WinUI, Electron, and native Cocoa among them — and who still read production code during reviews. We stay small so findings stay specific to your product, not a recycled slide template.
Working approach
- Observe first — we watch real tasks before arguing about widgets.
- Tie friction to code — every major UX note should point at a module or state model that makes improvement hard.
- Rank, don’t overwhelm — recommendations arrive sequenced with effort bands.
- Leave the build with you — we advise; your team owns the commits.
Values in practice
- Honesty about limits: if a problem needs a specialist accessibility lab or a security firm, we say so.
- Respect for operators: we treat workarounds as evidence, not “user error.”
- Local presence: Office 10, 53 Demo Street keeps us reachable for Thai and regional teams who prefer face-to-face walkthroughs.
Community
We publish Field Notes on desktop UX and maintainability decisions, and we occasionally host small reading groups in Chiang Mai for engineering leads. Ask on the contact form if you want an invitation to the next session.