OmarHassan
I build the interfaces people work in all day — clinical records, learning platforms, internal tools. Usually as the only frontend on the project, which means the architecture, the component library and the production incidents are all mine.
Most interface work fails in the seams — the form that loses an entry on a slow connection, the report that renders wrong for one clinician, the endpoint that changed on a Friday. I work in those seams.
Shipping production frontend, usually the only one on the project
Clinical modules in one doctor-facing dashboard, built solo
UI libraries. The component library was written by hand
Chosen, not collected.
Each one built rather than restyled. Scroll to move through them.
Meridian
A university platform with three role-specific portals on shared infrastructure, built to test whether institutional complexity is a question of boundaries rather than of styling.
Read caseCairn
Back-office software for a mountaineering expedition company, where three roles share one operational universe and the same URL renders three different products.
Read caseChrono
An enterprise device-operations console built around one idea — time is the interface. Operators scrub, pin and compare moments instead of navigating pages.
Read caseHelix
An enterprise cloud operations platform — sixteen product areas, five multi-step forms and a permission model that governs what renders, built on three runtime dependencies.
Read case- Meridian
- Cairn
- Chrono
- Helix
- 01Learning platform
Meridian
A university platform with three role-specific portals on shared infrastructure, built to test whether institutional complexity is a question of boundaries rather than of styling.
Read case - 02Expedition operations
Cairn
Back-office software for a mountaineering expedition company, where three roles share one operational universe and the same URL renders three different products.
Read case - 03Device operations
Chrono
An enterprise device-operations console built around one idea — time is the interface. Operators scrub, pin and compare moments instead of navigating pages.
Read case - 04Cloud operations
Helix
An enterprise cloud operations platform — sixteen product areas, five multi-step forms and a permission model that governs what renders, built on three runtime dependencies.
Read case
Four moves, always in this order.
What the screens are, which data they need, and what is actually due. Nearly every day I have gained on a deadline came from arguing about scope early rather than building faster later.
The API before the interface. On one project a proxy layer generated from the OpenAPI spec removed most of the rework every time the backend changed; on the current one I write both sides of it.
Tables, dropdowns, modals, forms — written by hand where the project rules out a UI library, and reused everywhere afterwards rather than forked per screen.
Playwright, unit tests and manual QA before release; chart errors, failed OTP delivery and breaking API changes after it. Shipping is the middle of the project, not the end.