## glossary
What is Designer?
A designer is the professional who devises solutions to concrete problems, balancing function, aesthetics and technical constraints. To design means to plan and shape something deliberately, and that is the essence of the job: it is not about decorating, but about deciding how something should work and present itself.
That distinction matters because the common perception reduces design to appearance. In practice, a large share of a digital product designer’s decisions are about structure: what shows up first, what gets grouped with what, how many steps a flow has.
The digital specialties
- UX Designer — research, flows, information architecture and usability. Focuses on how the experience works.
- UI Designer — the visual interface: typography, color, spacing, components and states.
- Product Designer — covers UX and UI, and also takes part in product decisions and metrics.
- Design Systems Designer — creates and maintains the library of components and tokens that standardizes the products.
- UX Writer — writes the interface copy, which often solves more usability problems than visual tweaks do.
How the process works
A typical flow starts with research — understanding the user and the problem. It moves to definition, narrowing down what will be solved. Then comes ideation and prototyping, turning alternatives into something concrete. And it ends with testing with real users, which tends to invalidate a good portion of the initial assumptions.
The central point is that design is iterative. The first version is wrong by definition — the question is finding out how much and where, as cheaply as possible. Testing a prototype costs a fraction of discovering the problem after development.
The boundary with development
Collaboration improves when the two disciplines share a vocabulary. A well-built design system defines tokens — colors, spacing, typography — with the same names used in the code, turning the handoff into a literal translation instead of an interpretive one.
/* the designer defines it in Figma, the dev consumes it in CSS */
--cor-primaria: #14b8a6; /* primaria/500 */
--cor-erro: #ef4444; /* feedback/erro */
--espaco-3: 0.75rem; /* 4px scale */
--raio-md: 0.5rem;
--sombra-card: 0 1px 3px rgb(0 0 0 / 0.12);
/* without tokens, every screen reinvents values and
the interface silently loses consistency */Objective criteria do exist
Design is not just taste. Nielsen’s heuristics offer assessable usability criteria — visibility of system status, error prevention, consistency. Accessibility has verifiable metrics, such as minimum contrast and keyboard navigation. And user testing produces concrete evidence about what works. The impact of AI on this field appears in artificial intelligence in design.
## faq
Frequently asked questions
What is the difference between UX and UI?
UX (User Experience) deals with the whole experience: flow, structure, how easy it is to complete a task. UI (User Interface) deals with the visual and interactive layer: how elements look and respond. A beautiful interface with a confusing flow has good UI and bad UX.
Does a designer need to know how to code?
They do not need to write production code, but understanding the technical constraints — what is expensive to implement, how responsive behavior works, what the team’s framework makes easy — makes deliverables far more feasible and reduces rework.
How do you evaluate whether a design is good?
By verifiable criteria, not opinion: does the user complete the task? How fast? How many mistakes do they make? Does the interface meet accessibility requirements? Is it consistent with the rest of the product? Usability tests and usage metrics answer these questions better than debates about taste.