07 · Journal · React EngineeringVol. 10 · Q2 2026kleiotechnology.com

React frontends built like furniture.

Next.js, Remix, React Native. Frontends built like furniture — square, joinery visible, tested.

Habakkuk 2:2

Write the vision, and make it plain upon tables, that he may run that readeth it.

Back to journal Talk to us

§ I — Cover concept

The context behind the article.

Journal 025

5 min

Image direction

React Engineering

5 min

Article

Next.js, Remix, React Native. Frontends built like furniture — square, joinery visible, tested.

Why it belongs in the journal

This entry exists to make the operating logic visible: not just the system we would build, but the constraint, tradeoff, or failure mode that forced the architecture to matter in the first place.

§ II — Article

React frontends built like furniture.

The React stack is now an ecosystem

There is no single "React stack" anymore. There is Next.js for SEO-bearing surfaces and full-stack apps. There is Remix for forms-and-data web apps. There is React Native for shared mobile codebases. There is plain React on top of Vite when the app is genuinely a single-page client.

Picking correctly between these is half the work.

How we build a React frontend

Server components by default when the data layer permits it, client components when interactivity demands it
Type-safe data flow from the database edge to the rendered DOM
Design system components owned by the team, not imported from a third party that may not exist in two years
Accessibility verified in CI, not after a launch
Performance budgets enforced on bundle size, LCP, and INP

Joinery visible

We do not hide framework conventions behind clever abstractions. New engineers should be able to read a route, find its data source, and trace the render path without a tour.

Mobile when it fits

React Native shares a meaningful amount of code with web React, but it is not free. We use it when a product needs native presence on two platforms with shared logic.

A frontend codebase ages well when the next engineer can read it without a guide.

§ III — Reading note

What the article is really about.

Operating tension

Next.js, Remix, React Native. Frontends built like furniture — square, joinery visible, tested. In practice, the hard part is usually not implementation syntax but aligning delivery, controls, and operator trust so the thing can survive contact with a real team.

Kleio view

We treat these articles as public design memos: short, opinionated, and anchored in systems that have to be bought, operated, and defended long after launch week.

§ III — Continue reading

Three adjacent articles.

Cloud Computing

Modernization is a pipeline, not a rewrite.

We killed a $400K rewrite in week two and replaced it with a three-tier modernization pipeline. Eleven modules extracted, 19,000 lines of dead code retired, drift down 62% — without a single big-bang cutover.

Audit before you automate.

An association almost spent $180K automating a workflow that ate twenty-four hours per year, while an 8,680-hour problem sat untouched. The fifteen-minute audit that caught it is the cheapest piece of work in any AI engagement.

Agentic AI

MCP servers are the orchestration layer, not the demo.

Most AI tooling lives one paste away from the systems it could help with. Model Context Protocol servers close that gap without giving up the security posture an enterprise can defend.

Back to journal