I’m Bianca. At Codinental I design products whose interface has to express business logic clearly. My work covers user flows, information architecture, components, states, and rules that make implementation and approval manageable.

Design systems as a basis for decisions

In complex products, a polished screen is rarely enough. Users learn patterns, business stakeholders review flows, and development needs binding specifications. I build Figma libraries with components, variants, tokens, and documented states.

Loading, empty, error, success, permissions, disabled actions, focus behavior, and microinteractions are treated as part of the system. That reduces follow-up questions during implementation and limits drift in later extensions.

UX for reviewable workflows

Good UX comes from information architecture and flows that make decisions understandable. I prototype early so business teams, management, and engineering can review the same workflow. Then hierarchy, copy, feedback, state logic, and error situations are worked out precisely.

The product has to guide, explain, and limit complex rules. Users should understand which action is available, which input is missing, and which next step is permitted by the process.

Handoff with dependable specification

I deliver specifications with variants, spacing, breakpoint behavior, states, edge cases, and acceptance criteria. Design QA accompanies implementation so the interface reflects the agreed product logic. This gives Halil a dependable basis for components and interactions.

How it connects at Codinental

Andrei provides backend contracts and platform standards. Halil turns the business logic into web and mobile applications. I ensure flows, states, and interactions express that logic correctly. This keeps the product consistent as the scope grows.

AI as support

We use AI internally for variant work and recurring tasks. When AI is embedded in a product, the interface needs clear references to sources, confidence, approval steps, and correction paths. In document-heavy processes, UX often decides whether an output can be used in daily work.

I enjoy products where the interface carries responsibility. That is where design has to be precise, reviewable, and ready for implementation.