Case study

Property API — modern full-stack foundation

Laravel’s official React + Inertia starter: Fortify handles auth features, Inertia bridges server routing to a React UI, and Pest anchors tests—ideal for growing a domain like property or internal tooling.

Laravel 12 Inertia React Fortify Sanctum Pest

What it is

The repo follows the starter-kit layout: PHP owns routing, authorization gates, and form validation; React pages render via Inertia responses instead of classic Blade views. Wayfinder-related tooling aligns with current Laravel front-end conventions.

Architecture

Hybrid MVC: controllers return Inertia props, not HTML strings. Session auth flows use Fortify actions; SPA navigations feel client-side but respect Laravel CSRF and middleware. This trades a classic Blade simplicity for a unified typed UI layer in React.

Browser (React) │ ▼ ┌─────────────────────────────┐ │ Laravel route │ │ middleware + Fortify │ │ Controller → Inertia::render│ │ (shared props, validation)│ └──────────────┬──────────────┘ ▼ Page JSON + React render

Highlights

One deployment unit with a modern component UX.
Server-authoritative validation reduces duplicated rules vs a pure SPA+API split.
Pest encourages concise feature tests around critical flows.
First-party starter means upgrade paths track Laravel releases.