Product design
Dashboards, tables, ERP screens. Dense data that has to stay readable at 3am on a support call, and the states, empty cases and failures that decide whether an operator trusts the screen.
- Dashboards
- Data tables
- Flows
- Prototypes
Anton Dvorianinov, Senior UX/UI Designer
0Portfolio 2026 · Burgas, BG / EET
Senior Product Designer · Design Engineer · Remote, EET
Ten years designing SaaS platforms, dashboards, ERP and mobile apps. I work on the screens where the money is actually made: the ones that decide how fast a customer starts paying, what a mistake costs, and how many support tickets never get written.
Experience · CV
From print and branding to complex interfaces, dashboards, tables and ERP systems, and the design system that keeps them consistent.
Selected work
Case studies and side explorations across SaaS platforms, dashboards and design systems. There is more inside than UI.
What I do · 03
Not a menu of services. These are the parts of product design I have actually shipped, repeatedly, on a platform that people use for their job every day.
Dashboards, tables, ERP screens. Dense data that has to stay readable at 3am on a support call, and the states, empty cases and failures that decide whether an operator trusts the screen.
Typography, colour, spacing and components pulled into one library, documented, and kept honest across releases so a screen built three years apart still matches.
Interviews, usability testing and heuristic review, enough to know which of the five arguments in the room is the one the user actually cares about.
How I work · 04 steps
The same four steps whether it is a single screen or a five-year platform. Most of the value is in the first and the last one.
01 / 04
Who uses this, what breaks their day, and what the business needs out of it. Interviews, existing tickets, watching people work.
02 / 04
Information architecture and flows before pixels. Cheap to change here, expensive later. Agreement on scope in writing.
03 / 04
Wireframes to high fidelity, built from the system rather than around it. Every state drawn: loading, empty, partial, failed.
04 / 04
Detailed handoff, support through implementation, then look at what people actually do with it and fix what I got wrong.
Track record
Years in the craft, facilities running the work, releases that went out.
Remote from Europe. Systems design, large platforms, and work shaped by real user feedback.