Index

About

AJIKO is a one-person frontend studio. No team page, no rotating roster. When you hire AJIKO, you get me, every meeting, every commit.

I started in 2017 on a UK retail employee portal. Joined as the most junior engineer in the room, left four years later as the senior on the team. Since then I've shipped frontends across fintech, retail, Web3, and SaaS. Nine years of frontend, all remote, all global teams.

The best frontend work I've seen came from people who stayed.

That's why AJIKO exists. Consultants leave. Contractors finish their tickets. The interfaces that age well, the ones that still feel right after three years, almost always belong to someone who showed up every Monday and cared what the codebase looked like in 2027.

I'd rather do that for two clients well than ten clients badly. So the studio stays small. Permanently small.

Practice

01

Build from zero

Greenfield work. I set up the architecture, the component system, the type discipline, and the first production deploy. You keep all of it.

02

Scale what works

Embedded with your team. Ship features without trashing the codebase. Quiet refactors, paid down in passing.

03

Repair what doesn't

Slow interfaces, brittle state, untyped sprawl. I diagnose, write the upgrade plan, ship it.

04

Stick around

Most engagements run multiple quarters. The work that matters compounds. That only happens if someone actually stays.

Tools I reach for

LanguagesTypeScript (strict, always) · JavaScript
FrameworksReact 18 · Next.js 14 · Vite where it fits
StateTanStack Query · Zustand · Context for the simple stuff
StylingTailwind · CSS Modules · Radix primitives
TestingVitest · Playwright · RTL where it earns its keep
ToolingStorybook · Figma · Git · Bitbucket
APIsREST first · GraphQL as needed
HostingVercel · Cloudflare · whatever you're already on