Skip to content
Deutsch Current language: English

Glossary

Laravel Inertia: Vue or React without building an interface

A connecting layer that attaches a JavaScript front end to Laravel without an API of its own having to exist.

Anyone wanting to use Vue or React normally builds two things: the front end, and an interface through which it gets its data. That interface is real work, even though nobody except your own front end uses it.

Inertia leaves it out. The application answers neither with finished HTML nor with a general interface, but hands exactly the data this one page needs straight to a component in the front end. Routing and permissions stay where they belong, which is in Laravel.

When the route fits

Inertia makes sense when there is experience with Vue or React on the team anyway and the interface is getting demanding, but there is no second consumer of the data.

As soon as a mobile app or another system needs the same data, the picture shifts. Then the interface appears regardless, and it should be cut from the start so that several consumers can work with it. What matters there is under API and backend development.

FAQ

Häufige Fragen

Can we still connect an app later?
Yes, and then the interface does appear after all. Inertia saves you one for your own screens; it blocks nothing. The business logic sits in the application and not in the connecting layer, so it can be offered through an API as well.

Related

Terms that belong with this one

  • Livewire

    An extension that lets parts of a page update without a second project in JavaScript coming into being.

  • Routing

    The mapping that decides which address in the browser calls which part of the application.

A project, or a question?

Write and tell us what it is about. You get an assessment from somebody who works with Laravel themselves, not from a sales desk.

Start a project 0711 21955388