Count to 10 Before Choosing Your Frontend for Laravel
summary
Presents four concrete frontend options for Laravel: Blade for simple server-rendered pages with minimal JavaScript and full page reloads; Livewire for Laravel-centered interactivity without writing JS but needing many backend calls and optimizations like debounce and query caching; Inertia.js to connect Laravel routing to a React/Vue/Svelte SPA (props serialized from PHP, requires a Node SSR process for SEO); and full JavaScript stacks such as Next.js/Nuxt when teams accept separate JS backends, SSR tooling, and independent auth/session handling.
AI-written summary · about
chapters (13)
- 0:00Frontend choice context
- 1:03Frontend solutions
- 2:28Blade rendering
- 5:56Livewire interactivity
- 8:43Livewire performance
- 14:50Inertia.js bridge
- 18:02Inertia.js navigation
- 21:14Inertia.js SSR
- 23:22Laravel JS client
- 26:36Next.js hybrid
- 28:23Full Stack JS auth & routing
- 30:09Comparison summary
- 32:19Q&A
related talks
50mVue.js x Laravel
28mLivewire vs InertiaJS: which to choose?
22mLaravel, Inertia and Vue
46mRethinking Server-Side Rendering in Modern PHP Applications
28mHave your cake and eat it too with Inertia.js
22mLaravel, Inertia, and Vue
07mLightning Talk: A Backend Engineer's Vue of Front-End Development
30mGetting Started with Inertia.js