Youssef Elzok

He studied computer science and artificial intelligence at Benha University's Faculty of Computers and Artificial Intelligence — an engineering education rather than a design one, which is most of what explains how he works. He designs in the same vocabulary the engineers build in: components, states, constraints and tokens, not a flat picture of a screen that somebody else has to work out how to assemble.

His work starts with behaviour. Before any visual decision is made, the question is what the product should do — what a user is trying to accomplish, what they know when they arrive, what happens when the input is wrong or the list is empty or the connection drops. Interfaces fail in those states far more often than they fail in the state that gets designed first, and designing the happy path alone is how a product ends up looking finished and feeling broken.

He builds and maintains the studio's design systems: component libraries, design tokens, and the typographic and spacing rules that keep a product coherent across dozens of screens and more than one team. The point of a system is not consistency for its own sake but decisions made once instead of thirty times, which is what makes a small studio able to ship at the standard it does.

Bilingual interface design is his most specialised territory. Arabic is not a translated string dropped into an English layout: direction reverses, so navigation, iconography, form flow and progress all have to mirror; Arabic typefaces sit on different vertical metrics and resolve narrower at the same size; and Arabic labels tend to run longer than the English they replace, which quietly breaks any layout measured for one language. He designs both directions at once rather than adapting one into the other.

He also owns the studio's visual identity and the identities it builds for clients — the part of the work that decides whether a product reads as considered or merely assembled, and the part that is hardest to recover once it has been got wrong.