roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Livewire 4 interviews by explaining what each server round trip does to a component. Covers state and actions, forms, loading and navigation, Alpine, payload security and testing.
118 of 118 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 118 new. 0 cut, outside your plan.
Livewire usually comes up inside a Laravel loop rather than as a round of its own: a live-coding task that adds a search box or an edit form to an existing app, or a review of a component someone else wrote. The questions test whether you can see the request behind each interaction. An input bound with `wire:model.live` sends one as the user types, after a short debounce. A public property holding an Eloquent collection is serialized into the snapshot, shipped to the browser and rehydrated on every update. A public `$userId` set in `mount()` can be rewritten in the browser unless it is `#[Locked]` or checked again inside the action. A junior answer describes the directive: `wire:click` calls the method, `wire:loading` shows the spinner. A senior answer describes the round trip: which hooks run while the component is rebuilt and in what order, what the snapshot checksum protects and what it does not, what goes wrong when an `#[Async]` action changes state, and when a lazy component, an island or a few lines of Alpine in the browser cost less than another request.
The plan opens on the decision before the code: [why a team picks server-driven components](/topics/be-laravel-frontend-tradeoffs) over Inertia or a separate SPA, and the [starter kit](/topics/be-laravel-frontend-starter-kits) that scaffolds a Livewire app. [Blade](/topics/be-laravel-blade-artisan) follows because every component renders a Blade view, and its escaping, slots and layouts carry straight into Livewire templates. Server State pairs a concept with the product. [What a server-rendered page serializes](/topics/fe-meta-frameworks-concepts-execution-boundary-serialization) comes first, so that [components and their public properties](/topics/be-livewire-components) read as state that travels to the browser and back, not as ordinary class fields. [Actions and events](/topics/be-livewire-actions-events) are the calls that state answers to. Forms build on both: Laravel's [validation rules](/topics/be-laravel-validation-rules) and [error messages](/topics/be-laravel-validation-messages) come before [binding](/topics/be-livewire-binding), where `#[Validate]` and Form objects reuse them. The [hook order](/topics/be-livewire-lifecycle) of a single update request comes after you have written a few components, because it explains the bugs those first components produce. The middle of the plan is about the wait a user feels. [Client navigation and prefetching](/topics/fe-meta-frameworks-concepts-routing-navigation-prefetch) frames what `wire:navigate` does, and [lazy loading](/topics/be-livewire-loading), loading states and polling decide how slow a page seems. [Alpine and the JavaScript hooks](/topics/be-livewire-alpine) handle what should never need a request at all. [Uploads](/topics/be-livewire-uploads) come after the [disks](/topics/be-laravel-filesystem-disks) they are stored on, since the temporary file and the final one live in different places. Security comes late because it needs everything before it. [Where authorization belongs](/topics/be-authz-access-control-enforcement-placement) and Laravel's [gates and policies](/topics/be-laravel-auth-gates-policies) lead into [payload security](/topics/be-livewire-security): any public method can be called from the browser, and every argument it receives is user input. [Component tests](/topics/be-livewire-testing) close the plan, together with what they cannot prove about the browser.
A Laravel developer who already writes Blade can skim the opening stretch and begin at Server State; someone new to Laravel should get Blade and validation solid first, because Livewire questions take both for granted. With a week or two before the interview, narrow level to the range you are applying at, raise importance to must know, and spend most of the time on properties, binding and the lifecycle, where the scenario questions sit. Senior candidates can go straight to payload security and the hook order, and should be ready to argue when a component is the wrong tool and Alpine or a plain Blade page would do. Livewire is one part of a Laravel job. Routing, Eloquent, queues and deployment are not in this plan; the [Laravel roadmap](/roadmaps/laravel) carries them, with Livewire as one of its UI options. Inertia, the other path Laravel offers to the front end, sits on that roadmap as well.
Livewire usually comes up inside a Laravel loop rather than as a round of its own: a live-coding task that adds a search box or an edit form to an existing app, or a review of a component someone else wrote. The questions test whether you can see the request behind each interaction. An input bound with wire:model.live sends one as the user types, after a short debounce. A public property holding an Eloquent collection is serialized into the snapshot, shipped to the browser and rehydrated on every update. A public $userId set in mount() can be rewritten in the browser unless it is #[Locked] or checked again inside the action.
A junior answer describes the directive: wire:click calls the method, wire:loading shows the spinner. A senior answer describes the round trip: which hooks run while the component is rebuilt and in what order, what the snapshot checksum protects and what it does not, what goes wrong when an #[Async] action changes state, and when a lazy component, an island or a few lines of Alpine in the browser cost less than another request.
The plan opens on the decision before the code: why a team picks server-driven components over Inertia or a separate SPA, and the starter kit that scaffolds a Livewire app. Blade follows because every component renders a Blade view, and its escaping, slots and layouts carry straight into Livewire templates.
Server State pairs a concept with the product. What a server-rendered page serializes comes first, so that components and their public properties read as state that travels to the browser and back, not as ordinary class fields. Actions and events are the calls that state answers to. Forms build on both: Laravel's validation rules and error messages come before binding, where #[Validate] and Form objects reuse them. The hook order of a single update request comes after you have written a few components, because it explains the bugs those first components produce.
The middle of the plan is about the wait a user feels. Client navigation and prefetching frames what wire:navigate does, and lazy loading, loading states and polling decide how slow a page seems. Alpine and the JavaScript hooks handle what should never need a request at all. Uploads come after the disks they are stored on, since the temporary file and the final one live in different places.
Security comes late because it needs everything before it. Where authorization belongs and Laravel's gates and policies lead into payload security: any public method can be called from the browser, and every argument it receives is user input. Component tests close the plan, together with what they cannot prove about the browser.
A Laravel developer who already writes Blade can skim the opening stretch and begin at Server State; someone new to Laravel should get Blade and validation solid first, because Livewire questions take both for granted. With a week or two before the interview, narrow level to the range you are applying at, raise importance to must know, and spend most of the time on properties, binding and the lifecycle, where the scenario questions sit. Senior candidates can go straight to payload security and the hook order, and should be ready to argue when a component is the wrong tool and Alpine or a plain Blade page would do.
Livewire is one part of a Laravel job. Routing, Eloquent, queues and deployment are not in this plan; the Laravel roadmap carries them, with Livewire as one of its UI options. Inertia, the other path Laravel offers to the front end, sits on that roadmap as well.