Component inventory
What exists, what's used, what's dead. Honest accounting, not a wishlist.
// react development
React, done with discipline.
React work for teams whose codebase has accumulated three versions of state management glued together. We rebuild what's brittle and ship what wasn't there.
// where teams get stuck
Your React app shipped. Then it kept shipping.
- Three state libraries fighting over the same store.
- Component sprawl — twelve buttons, four of them dead.
- Tests that pass locally and fail in CI for reasons nobody remembers.
- Junior engineers afraid to refactor because nothing has types.
// what's included
What we leave behind.
State strategy decision
One store pattern, written down, defended in the architecture doc.
Hooks discipline
Custom hooks where they pay, not as decoration. Rules of hooks enforced in lint.
Type coverage at the boundary
API responses, form inputs, route params. The places types catch real bugs.
Migration path forward
RSC where it makes sense, client-only where it doesn't. Documented either way.
// how we work
Three phases. Built to last.
01 · Calibrate
Codebase audit. Written scope. What stays, what gets rebuilt, what gets deleted.
02 · Build
Weekly demo. PRs reviewed against the architecture doc. No "just one more refactor."
03 · Hand off
Architecture doc updated. Tests green. Support window starts. Your team owns it.
// common questions
What teams ask before signing.
Yes. We've done 17 → 18, 18 → 19. Done with a written migration plan, tested in stages, not a big-bang weekend.
Yes. A post-launch support window is included on every project. After that, optional ongoing care plans cover bug fixes, dependency upgrades, and small features — sized to your team, pause-able month to month.
We use RSC where the data fetching wins are real and skip it where the client-side complexity isn't worth the cost. The architecture doc explains which is which.
Where they pay. We don't chase coverage numbers. We test boundaries — payments, auth, data integrity.
Murcia, Spain. We work remote across Europe, the UK, and North America.