SPA feel without a separate API
Inertia lets Laravel controllers return Vue pages directly. You get client-side navigation without building, versioning and securing a REST API that only your own frontend ever calls.
Case Study
Uusloo: full-stack site on Laravel and Vue
Laravel backend, Vue frontend, joined by Inertia.js
Risto Tõldsep built Uusloo as a full-stack custom website with a Laravel backend and a Vue frontend connected through Inertia.js, giving the site single-page-app responsiveness with server-rendered routing.
The challenge
Uusloo needed a site that feels as responsive as an app while keeping server-rendered routing, without the overhead of building and maintaining a separate API and a separate frontend application.
What I built
- A Laravel backend handling routing, data and business logic.
- A Vue frontend for the interface.
- Inertia.js joining the two, so pages are Vue components but routing and data still come from Laravel.
Technical highlights
One codebase, one deploy
Backend and frontend live and ship together, which for a project this size is considerably less to operate than two applications.
Tech stack
LaravelVueInertia.jsPHPMySQL
Frequently asked questions
When would you use Inertia instead of a REST API?
When the only consumer of the API is your own frontend. Inertia removes a whole layer you would otherwise build and maintain for no external benefit. If you need a public API or a mobile client too, that calculation changes.
Related projects
Get in touch
Want to know more about me, tell me about your project, or just say hello?
Drop me a line and I'll get back to you as soon as possible.