01 / 04
Websites
Responsive interfaces, layouts, interaction and front-end development — explored through complete concept builds and smaller experiments.
- Written by hand
- Every width
- Fast by default
Skip to the four disciplines
Alaa Abbod · Herne, DE
Four disciplines
Design and development are not separate halves of my work. These four areas are where I keep testing how visual thinking and technical thinking can strengthen each other.
02 / 04
Mobile Apps
Interface systems for mobile — screens, navigation, states, flows and interaction patterns for iOS and Android.
- iOS & Android
- Flows, not screens
- Works offline
03 / 04
E‑commerce
Digital storefront concepts focused on product presentation, hierarchy, browsing and checkout interaction.
- Own the journey
- Payments stay with a provider
- Your data, your accounts
04 / 04
Graphic Design
Logos, identity systems, posters, advertising pieces and visual studies built around type, colour and composition.
- Marks & construction
- Full identity systems
- Campaign & advertising
true of every build
The same practice, whichever discipline it is
Scoped before it starts
Every project gets a real plan before any code or design work begins.
Iterated, not first-drafted
Revisions are part of the process, not an afterthought bolted onto the end.
Set up properly
Domain, hosting and repository set up the way I'd want to come back to them.
Readable source
Any developer, including a future me, can open the files and read what they say.
Accessible from the start
Built to WCAG 2.1 AA practice while it is made, not audited on afterwards.
Nothing left half-finished
A project ships as a complete, coherent experience or it doesn't ship at all.
One person, both halves
The same hands do the design and the build, so nothing gets lost between them.
Made to be explored
Every build here is meant to be opened, clicked through and read, not just looked at.
not a discipline, a discipline
Measuring accessibility & performance
A scanner reads markup. It cannot press Tab, and it cannot tell you that the thing it just passed is unusable. So checking a build by hand — the keyboard, the contrast, what still moves under reduced motion — is part of how I finish anything I make, this site included.
The numbers below are this site's own, published rather than claimed, so the method is checkable by anyone who wants to see it.
Measured on this site, 10 August 2026
axe‑core: 0 violations across 23 routes × 2 viewports
keyboard: 0 of 1,526 tab stops with no visible focus indicator
Method: how this is measured. No manual screen-reader pass has been run, and none is claimed.
- Keyboard walk of every interactive control, by hand
- Focus order, focus visibility and focus traps
- Contrast, measured, with the pairs that fail listed
- Headings, landmarks, names and roles
- Reduced-motion behaviour, and what still moves
- Load and interaction cost, on a throttled connection
three of the ten, picked for range
You can run every one of them
Arke Estates
Editorial restraint · self-initiated · 2025
Signalform
Dense product UI · self-initiated · 2024
Root & Ritual
A storefront, end to end · self-initiated · 2025
Each one started with a different question.
whichever of the four it is
See how it comes together
The ten projects on this site walk through the decisions behind each of these four areas — what worked, what didn't, and what I'd do differently next time.
Always exploring the next idea.