Selected experience archive
Five projects get the full write-up. This is the rest of the record: sites, portals, dashboards and applications delivered across healthcare, finance, local business and hospitality. Some are a decade old, some were internal, some are simply no longer online — and together they are the reason an unfamiliar domain stops being intimidating.
Why there are no links here
Parts of this work are ten years old, some of it was internal, and some has been redesigned by other people since. Pointing you at a URL that no longer reflects what I built would be misleading — so each entry gives the product context, my part in it and the stack, and stops there.
01 / Selected experience archive
Medical products carry a constraint most software does not: the person using it is mid-consultation with a patient waiting. Information has to surface in seconds, the interface has to stay legible to someone barely looking at it, and “ask the developer” is never an acceptable answer during clinic hours.
Across portals, drug information, forums and clinic systems the work kept rhyming: strip the interface down to what the moment needs, protect readability, and hold the design together as modules pile up. dr100 from the same field is written up as a full case study.
UI/UX research · Frontend
01Research and a frontend concept for a medical-sector product — the stage where you work out what clinicians will actually use, before anyone writes production code.
Scope and stack: UI/UX research, Frontend
Frontend · UI/UX · Custom animations
02A software house selling into medicine, so the site had to read like engineers you would trust with patient data. Custom WordPress frontend, animations built by hand rather than dropped in from a plugin.
Scope and stack: Frontend, UI/UX, Custom animations · WordPress
Frontend · UI/UX
03A showcase site for a medical product, built around the question a doctor asks first: what does this actually change during a visit?
Scope and stack: Frontend, UI/UX
Frontend · UI/UX
04A medical portal built around practical tools rather than articles — the things a doctor opens mid-consultation and closes a minute later.
Scope and stack: Frontend, UI/UX
Frontend · UI/UX · Accessible interface
05Drug information for older readers. Type size, contrast and tap targets were the brief itself, not a pass at the end.
Scope and stack: Frontend, UI/UX, Accessible interface
Frontend · UI/UX
06A clinic website on WordPress with a hand-built frontend, so the practice could keep editing its own content without inheriting a theme's habits.
Scope and stack: Frontend, UI/UX · WordPress
Frontend · UI/UX
07A landing page for a software company in the healthcare market — short, and load-bearing, because it was the entire first impression.
Scope and stack: Frontend, UI/UX
Frontend · UI/UX · Community product
08A discussion forum for doctors. Community products die of friction, so posting, finding an old thread and reading on a phone all had to be effortless.
Scope and stack: Frontend, UI/UX, Community product
Frontend · UI/UX · Content portal
09A medical news portal where the frontend's job is mostly to get out of the way of the reading.
Scope and stack: Frontend, UI/UX, Content portal
Frontend · UI/UX · Content portal
10Medical news and information, structured so a reader who arrives at one article leaves having found three more.
Scope and stack: Frontend, UI/UX, Content portal
Frontend · UI/UX
11A specialist medical portal for navigating dense domain information — the kind of product where search and filtering matter far more than the homepage.
Scope and stack: Frontend, UI/UX
Frontend · UI/UX · Product workflows
12A clinic management application covering the operational side of a practice: who is coming, what was done, what gets billed.
Scope and stack: Frontend, UI/UX, Product workflows
Frontend · UI/UX · Product interface
13Clinic management on a Vue.js frontend — appointments, records and the medical workflows wrapped around them.
Scope and stack: Frontend, UI/UX, Product interface · Vue.js
02 / Selected experience archive
Internal tools get the least design attention and the most daily use, which is also where the expensive mistakes live: a stale number in an investment view, a moderation queue nobody can keep up with, a report assembled from data that was entered twice.
Product interfaces where being correct and being quick to operate beat visual ambition — real-time collaboration, admin panels moderators actually open, and financial data rendered so it is obvious when something is off.
Web application · Product development
01A project management application on Meteor.js, where real-time collaboration means two people editing the same thing must not surprise each other.
Scope and stack: Web application, Product development · Meteor.js, MongoDB, Blaze
Admin panel · Frontend · Product interface
02The administration side of an anonymous chat product. Moderation tooling is unglamorous and load-bearing: if it is slow, moderators quietly stop using it.
Scope and stack: Admin panel, Frontend, Product interface · Meteor.js, React, MongoDB
Frontend · Financial interface · API integration
03An investment application reading financial data over a REST API, where a stale or misread number is not a cosmetic bug.
Scope and stack: Frontend, Financial interface, API integration · React, REST API
Admin panel · Frontend · UI/UX
04An internal dashboard for university teachers — built for people who open it twice a semester and should not have to relearn it each time.
Scope and stack: Admin panel, Frontend, UI/UX
03 / Selected experience archive
For a service company the site usually is the sales process: someone searches, lands, decides in a few seconds whether these people look competent, and either calls or leaves. Most of these businesses also need to edit their own content without breaking the layout.
Hand-built frontends over WordPress and Joomla rather than a bought theme, so the design survives contact with real content — plus loading-speed work wherever visitors arrive on a phone with two bars of signal.
Frontend · UI implementation · CMS integration
01A company site for architectural products that cut noise inside buildings. A Next.js frontend pulling content from WordPress over the REST API, so the marketing team kept the editor they already knew.
Scope and stack: Frontend, UI implementation, CMS integration · React, Next.js, Material UI, WordPress REST API
Frontend · UI/UX
02A company site for a Polish firm building custom digital solutions — the classic problem of describing bespoke work without sounding like everyone else.
Scope and stack: Frontend, UI/UX
Frontend · UI/UX
03A Warsaw car detailing business, where the site has one real job: turn a local search into a booked slot.
Scope and stack: Frontend, UI/UX · WordPress
Frontend · UI/UX
04A local car repair shop in Warsaw. Same job, blunter: phone number, location, and enough signal that these people know what they are doing.
Scope and stack: Frontend, UI/UX · WordPress
Frontend · UI/UX
05A corporate site for a brand agency working the German market. An agency's own site is the hardest brief there is, because it is also the portfolio.
Scope and stack: Frontend, UI/UX
Frontend · UI/UX
06The Polish-market counterpart, sharing a design language while talking to a different set of clients.
Scope and stack: Frontend, UI/UX
Frontend · UI/UX · Load speed optimization
07A German bakery chain on WordPress — frontend plus the loading-speed work, since most visits arrive on a phone somewhere between two shops.
Scope and stack: Frontend, UI/UX, Load speed optimization · WordPress
Frontend · UI/UX
08Another German bakery chain, this one on Joomla with a hand-built frontend on top.
Scope and stack: Frontend, UI/UX · Joomla
Frontend · UI/UX
09A German carpentry business — Joomla, custom frontend, and the kind of plain clarity the trades sector responds to better than decoration.
Scope and stack: Frontend, UI/UX · Joomla
Frontend · UI/UX
10A bakery and café presenting itself to customers: opening hours, what is actually in the counter, and how to find it.
Scope and stack: Frontend, UI/UX
04 / Selected experience archive
These are the same problem in different clothes: someone is comparing options and will pick whichever is easiest to understand. A shoe, a hotel room and a dog-friendly guesthouse all lose to a clearer competitor.
Customer-facing interfaces built for finding and comparing — photography given room to work, filters that answer the question people actually arrived with, and nothing standing between wanting the thing and being able to ask for it.
Frontend · UI/UX · Product presentation
01A Polish children's footwear brand, where the frontend has to do what a good shop assistant does: show the product properly and get the size right.
Scope and stack: Frontend, UI/UX, Product presentation
Frontend · UI/UX · Discovery interface
02A discovery site for dog owners looking for hotels that will take the dog. Filtering is not a feature here, it is the product.
Scope and stack: Frontend, UI/UX, Discovery interface
Frontend · UI/UX · Hospitality website
03A German hotel presenting rooms and offers, with the quiet goal every hotel site has: get the booking directly rather than through a platform.
Scope and stack: Frontend, UI/UX, Hospitality website
Next project
What carries over is not the industry, it is the pattern: land in an unfamiliar domain, work out what the interface genuinely has to do, and ship a frontend the next person can maintain. That has happened often enough now to be repeatable rather than lucky.