iOS & Android apps
Native and cross-platform, from the first build in your hands to a listing on both stores. Offline state, notifications, payments, and the review process that comes with them.
[ 03 · Build the system ]
Product Engineering
iOS, Android and the web. Designed and engineered end to end.
Taking projects · worldwide
[ 01 ]The build arm
The discipline where I make systems instead of breaking them.
Two crafts uncover what's hidden; this one creates what comes next. The same eye for how a system actually behaves, its edges, its failure modes, the assumption it quietly makes, now points at building the thing instead of taking it apart. It runs across every surface a product lives on: an iOS or Android app, a web application, the API underneath them, and the interface design that decides how any of it feels to use. Knowing exactly how software breaks is not a footnote when you're the one shipping it.
[ 02 ]Selected work
Work you can open right now.
Products with their own users, a journal mid-launch, and sites built under someone else's name. Every link goes to the live thing, not a case study.
ProductsShipping, with their own users.
Sybil Sight — opens sybilsight.com in a new tab
A mentalism operating system for smart glasses. Peeks, scripts and cues, visible only to the performer.
QA engineerBooked Solid OS — opens booked.kivimedia.co in a new tab
An AI booking department for working entertainers. Maps the buyers, writes the outreach, works the inbox.
Developer
In productionLive site, first issue this autumn.
Sapien Journal — opens sapienjournal.com in a new tab
A subscription journal of propless mentalism. Monthly effects, essays and interviews. Issue № 1, autumn 2026.
Co-founder
CommissionsBuilt under another name.
Charlie Hewish — opens charliehewish.com in a new tab
A bookings site for a close-up magician and mindreader. Showreel, packages, one way to enquire.
Sole developer
[ 03 ]What I build
End to end, no handoffs.
Web apps & product sites
Full applications with auth, data and state, and the sites that sell them. Same discipline whether it's one sharp landing page or a product carrying real users.
Product design
Interface, flows and motion, decided before implementation and by the head that implements them. Wireframes through to a design system the build can hold to.
[ 04 ]How I build
What holds after the launch.
Considered
Every screen earns its place. Design and engineering decided together, by one head, so the product feels intentional instead of assembled.
Fast
Performance is the spec, not a cleanup pass. Cold start on a mid-range phone, Core Web Vitals in a browser, accessibility and a small payload: all of it designed in from the first commit.
Resilient
Built by someone who breaks systems for the other half of the week, so edge cases, failure modes and security are handled before they're a problem.
[ 05 ]How a build runs
From idea to shipped.
01
The brief
One message with what you're making, who it's for, and which platforms it has to land on. We agree the goal, the scope and what 'done' actually looks like.
02
Design & architecture
Screens you can see and a stack you can question, decided together and before a line of production code is written.
03
The build
Engineered in the open, shipped in increments you can watch land. Tested and accessible as it goes, not after: on mobile that means a build on your own device from the first week.
04
Ship & support
Through App Store and Play review, or onto infrastructure that holds. Handed over clean and kept fast after go-live. Not abandoned at the finish line.