UI/UX design for apps and complex software

UX design decides how the product works: who the users are, what they need to get done, the order of steps and what happens when something goes wrong. UI design decides how it looks and feels: layout, typography, colour, components and motion. A beautiful interface on a confusing flow still fails, so both are done together.

Enterprise software shows a lot of information to people who use it all day. Good design here is less about decoration and more about speed: clear tables with useful filters, bulk actions, sensible defaults, and screens that change by role so a cashier and a finance manager each see what they need.

Every screen also needs its empty, loading, error and no-permission states designed, not left for developers to guess. That work sits behind products like HealthOS, where I led product design, and the Railway Ticketing Platform, where my role was product design and the mobile experience.

Right-to-left design is more than flipping the screen. Navigation and progress move right to left, but some icons, such as play buttons or brand marks, should not be mirrored. Numbers, phone numbers and product codes stay left to right inside RTL text, and Arabic and Urdu scripts need fonts and line heights chosen for them. Designing both directions from the start avoids layouts that break when the language is switched.

Handover is planned so the design can be built exactly. You get organised Figma files, a component library with named variants, design tokens for colour, type and spacing, a clickable prototype of the main flows, and notes on behaviour that a static screen cannot show.

If I am also building the product, the same components carry straight into the code. If your own team builds it, they work from a system rather than a set of pictures.