mohamed elwed©26
available

portfolio — 2026

lusail, qatar

design& engineering*

( move the lens — عربي )
*mohamed elweddesign engineer — end to end6 projects · 4 disciplines

I work across the stack of making things — from brand & design systems, through product UX/UI, into web, mobile and AI/LLM & automation engineering

01 / about

I'm a design engineer I live in the seam between design and code, where an interface stops being a mockup and starts being a real, running thing.

One person, end to end: strategy → design → code → launch. The person who draws the interface is the person who ships it to production — no handoffs, no translation loss, no "that's a dev problem". That's the whole advantage.

06projects
04disciplines
06shipped
03writings
the full story ↗

02 / what i do

(01)

design

brand, systems & visual identity

(02)

ux · ui

product flows & interfaces

(03)

web

apps, tools & platforms

(04)

mobile

native & cross-platform

03 / the method — scroll

oo1

listen & map.

Every project starts as a conversation — goals, users, constraints, budget. I turn it into a written scope we both sign: pages, features, dates. No vague promises.

oo2

design in the open.

Wireframes first, then one key screen polished to done. You see real progress in days and correct course while changes are still cheap.

oo3

build the system.

Before any page: tokens, type scale, components — a design system in code. Everything after gets faster, and nothing drifts off-brand.

oo4

engineer end-to-end.

Same brain, both sides: the person who drew the interface writes the frontend, backend and CMS. What you approved is what ships — to the pixel.

oo5

harden & launch.

Performance, SEO, accessibility and analytics are checked before go-live, not after. Then we ship to your real domain, with monitoring on.

oo6

iterate in production.

Launch is the start, not the finish. Real usage shows what to sharpen — I stay on for the follow-through, version by version.

listen & map.Every project starts as a conversation — goals, users, constraints, budget. I turn it into a written scope we both sign: pages, features, dates. No vague promises.

04 / selected work

Chosen
output.

all work (6) ↗

05 / writing

all posts ↗
May 18, 2026Designing in the seam between design and codeMar 02, 2026The terminal as an interface metaphorJan 20, 2026Shipping real features with LLM agents