Batchmaker family · React application
W-Make Batch · React
The standalone Next.js frontend for the existing Express/SQLite domain core of W-Make Batch.
- Responsibility
- Frontend architecture, migration strategy, and technical quality.
- Technology
- Next.js 16 · React 19 · TypeScript · Tailwind CSS · SWR · Playwright
- Status
- Live · frontend modernisation
- Positioning
- A controlled UI transition: the domain backend contract remains stable while the client is modernised incrementally.
Situation
Situation
A production system cannot exchange its UI like a marketing page. Bookings, roles and the API have to remain stable during a migration.
The Express/SQLite domain core therefore remains the source of truth. The React frontend reaches it through a clear server proxy rather than moving business logic into the browser.
Decisions
Decisions
- 01
App Router and components modernise the interface without rewriting the domain booking path.
- 02
API access remains server-mediated; the browser receives neither direct database access nor secrets.
- 03
The legacy fallback is a narrow emergency path, not a second permanent product.
- 04
Route, role and smoke checks make the UI transition verifiable.
What you can inspect
A look at the application.
What you can inspect
The flow as a model.
01
Backend contract
The existing domain core remains the source for auth, roles and bookings.
02
Server proxy
The Next.js application mediates API calls without exposing backend details in the browser.
03
React interface
Modules are modernised as verifiable routes and components.
04
Fallback
A narrow emergency path remains separate from the normal React bundle.
What remains
What remains
Modernisation is safe when the domain boundary stays stable. A new client must not quietly reinvent the production contract.
batchmaker-react.w-make.com →30-min analysis · free