[01] Red ClayUnderstand
Find what the product has to say before writing a component. For Red Clay: origin before the catalogue.
I build products where engineering meets the interface.
A senior frontend and mobile engineer in Lagos. I care about the unglamorous parts — states, edge cases, release discipline — because that’s where people decide whether to trust a product.
[ no portrait — the work is the face ]
Capabilities, with receipts
[ scroll — the image follows ][01]Product engineering
Lumina — Invoice creation, delivery, payment, receipts and audit log — with one status language across the app, the API and the marketing site.
[02]Mobile engineering
SabiVest — Shares, dividends and trades in React Native and Expo, where every action shows its state on a small screen.
[03]Platform & systems
Twikkie — HR, payroll, recruitment and operations around one record — an interface that keeps the next action obvious.
[04]Creative development
Red Clay — Editorial pacing and motion that hand documentary imagery off to commerce.
How I work
[ four verbs, in order ][01] Red Clay[02] LuminaArchitect
Separate the marketing site, product app and API so each can move without breaking the others.
[03] SabiVestBuild
Ship financial flows in React Native where every action shows its state on a small screen.
[04] LuminaRefine
Tune defaults, states and copy until a small team can read their cash position at a glance.
The toolkit
[ chosen per product, not per trend ]Web
- Next.js
- React
- TypeScript
- GSAP
Mobile
- React Native
- Expo
- TypeScript
Data
- PostgreSQL
- REST APIs
Let’s build
the next one together.
Have a product that needs careful frontend or mobile engineering? Tell me about it — I read everything.