About Between worlds

Half engineer,
half the other thing.

Portrait of Michał Uzdowski, black and white.

I’m Michał Uzdowski, a designer and developer based in Poland. I design interfaces and build the systems behind them, and I have never managed to treat those as two separate jobs.

My oldest public repository is from 2020 - a calculator and a couple of small games. After that came a video chat on WebRTC, a Django API with a Vue front end, and a scraper that turned government dashboards into a database so I could draw a map of it.

Today I build my own products through my company, Binary Brain Technologies - Declario, Convertly and Lista Marzeń - and websites for a small number of clients. I design and build them end to end - from the first sketch to the database and the deploy.

I like problems where the idea and the implementation cannot be separated: where the way something looks depends on how it works, and the data model has to be shaped by what the interface needs to say.

My GitHub profile puts it plainly: “Stuck between high-tech and fantasy books.” This site is what that sentence looks like when it is built.

Capabilities Grouped by what they are for

From an idea to a deployed system.

  1. Idea
  2. Design
  3. Interaction
  4. Application
  5. System
  6. Deployment

01

Design

Deciding what the thing is before deciding how it looks.

  • Art direction
  • Interface design
  • Design systems
  • Motion concepts
  • Figma prototypes

02

Build

Interfaces that hold up on a slow phone as well as a large screen.

  • TypeScript
  • React
  • Next.js App Router
  • Tailwind or plain CSS
  • SVG and WebGL
  • GSAP

03

Systems

Data models, permissions and the parts nobody sees until they fail.

  • Postgres and Supabase (RLS)
  • Prisma, Drizzle
  • Server actions and REST APIs
  • Stripe and Paddle
  • Sanity CMS
  • Claude API

04

Ship

Getting it live, fast, indexable and kept honest.

  • Vercel
  • Performance
  • Accessibility
  • Technical SEO and structured data
  • Resend, Upstash, Sentry

Everything listed here is in use in the projects on this site.

Process How I work

Process

  1. 01Listen.Understand the people and the problem before touching a pixel.
  2. 02Think.Find the one idea the whole product can be built around.
  3. 03Design.Give that idea a visual language with rules the whole team can follow.
  4. 04Build.Make the interface and the system behind it - one person, one model of the problem.
  5. 05Break.Try to prove it wrong: slow devices, empty states, keyboard only, bad input.
  6. 06Ship.Put it live, measure what matters, and keep the copy as true as the code.

The work says more than this page. See the work or write to me.