Your users first
Who's using it, what they're trying to do and where they trip up. I did Google's UX courses on empathising, defining and ideating, and I use that process.
UI/UX design
Apps that look like someone designed them.
Most AI-built apps look the same because nobody overrode the defaults. I override them. Deliberate colour and type, layouts that were chosen rather than accepted, and flows that make sense to the people using them.
fig. 1 · UI/UX design
2 Google UX certificates
Who it's for
Sound familiar?
I design and build interfaces for Base44 and AI-built apps. Real design decisions instead of the defaults, so your app looks like someone actually thought about it.
- Your app works, but it looks like every other AI-built app.
- People get lost, stuck or confused somewhere in the flow.
- You're about to launch and the first impression has to land.
- You want a design system you can keep adding screens to.
What you get
What you actually get.
01 02 A design system you can keep using
Colours, type, spacing and components that work together, so the next screen you add still looks like it belongs.
03 Mobile first and accessible
Tap targets you can hit, text you can read, focus states that show up and keyboard support that works.
04 Motion with a reason
Small animations that explain what just happened. Nothing that makes you wait, and it calms down for people who prefer less motion.
05 Designed and built by the same person
I design and build, so nothing gets lost in a handover between a mockup and the real app.
How it goes
How it goes.
Five steps, in this order. You see progress at every one of them.
Step 01
Use it like a user
I go through your app the way your users do and write down everything that's confusing, slow or ugly.
Step 02
Pick a direction
We agree the look and feel on a few key screens before I touch the rest.
Step 03
Build the system
Tokens, components and patterns, built into the real app, screen by screen.
Step 04
Check it properly
Phones, tablets, keyboards, reduced motion and contrast. The bits nobody tests.
Step 05
Hand it over
Notes on how the system works, so you can add new screens without it drifting.
Proof
Where I've done this before.
What people said
Read every reviewHis UI work is some of the best I've seen, and he's prompt, helpful, and genuinely invested in getting things right.
Charles LangBase44 review He doesn't put you in mind just as a client, he puts your users in mind and is able to bridge the wonderful balance and thoughtfulness of design and core competencies with his full stack knowledge.
MeganBase44 review
What I've built
- hattle.app
Hattle
Brand, design and build: a sticker-wall look, sketched on paper and shipped in 8 hours.
Read the case study - whatsbaas.base44.app
What's BaaS?
Base44's backend drawn as a map you can hover, with a playground that prints a receipt.
Read the case study
- Base44Data, logins, backend functions and hosting.
- ReactThe frontend for my Base44 apps.
- Tailwind CSSStyling, straight in the markup.
- ClaudeThinking things through, and my own Claude skills.
- CodexOpenAI's coding agent.
FAQ
Questions people ask.
Something else on your mind? Ask me. I answer everything myself.
Ask a questionYes. I work inside your existing Base44 app, screen by screen, so the look changes without starting again from scratch. We agree the direction on a few screens first, so there are no surprises.
Mostly I design and build together, because that's where the design survives. If you really need design only, tell me what you've got and I'll tell you straight whether it makes sense.
Because the builder has a house style, and if nobody overrides it, you ship the house style. Same gradients, same cards, same centred hero. Fixing it is mostly about making decisions on purpose: type, colour, spacing and layout.
That's fine. We can pick a direction together: a few colours, a type pairing and some simple rules. It doesn't need to be a huge brand project to look intentional.
Goes well with
Pairs well with.
Base44 app development
Full-stack Base44 apps, built properly from the data up.
- A data model that makes sense
- Access rules from day one
- The whole stack
SEO and performance
Faster pages that search engines and AI answer engines can read.
- Technical SEO for a single-page app
- Structured data
- GEO for AI answer engines
Backend and integrations
Stripe, Resend and third-party APIs, wired in and working.
- Stripe payments and subscriptions
- Email that arrives
- Third-party APIs, safely
Want your app to look like it means it?
Send me a link and tell me what's bugging you about it.