roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Hotwire interviews on building interactive apps from server-rendered HTML, as Rails does by default. Covers Turbo Drive, Frames and Streams, morphing, Stimulus and Hotwire Native.
87 of 87 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 87 new. 0 cut, outside your plan.
Hotwire questions usually arrive inside a Rails loop rather than in a round of their own: a technical conversation about a feature you built, a pairing session on an existing app, or the frontend half of a full-stack design discussion. They tend to start from a symptom. A form that fails validation and appears to do nothing. A frame that shows Content missing after a session expires. Timers that pile up each time the Back button restores a page. A broadcast partial that shows the wrong edit button because it was rendered with no request and no current user.
What earns credit is the mechanism behind the symptom. Turbo Drive renders the response to a failed submission when it carries an error status such as 422, and expects a successful one to redirect with 303 See Other. A cached snapshot comes back with its markup, so connect() runs again on elements whose earlier setup was never torn down in disconnect(). A broadcast is rendered outside any request, so its partial must take its data as locals. From middle level up, interviewers also ask for trade-offs: a targeted stream against a morphing refresh, an outlet against a dispatched event, how broadcasts reach users connected to other app servers, and which screens of a mobile app should stay web.
Turbo and Stimulus are thin layers over the browser, so the plan opens there. The History API is how Turbo Drive records a visit without a full page load. Event delegation and custom events are what a Stimulus action descriptor and this.dispatch compile down to. <turbo-frame> and <turbo-stream> are custom elements, and a MutationObserver is how Stimulus notices controllers entering and leaving the page. Two framework-neutral ideas come next, because Turbo Drive implements both: prefetching on hover and the version skew between a new deploy and a tab still running the old assets.
The product itself begins with navigation: Turbo Drive for whole-page visits, then Turbo Frames for a region of the page that navigates by itself. Stimulus and its values and outlets come before the live updates on purpose, because a morphing refresh can disconnect and reconnect the controllers on elements it changes, and the questions about it assume you know that lifecycle.
Live updates start with Turbo Streams, targeted changes sent in a response or broadcast to every open page, then morphing refreshes, which re-render the page and keep what has not changed. Action Cable follows both because it is the transport their broadcasts travel over, and the questions about pub/sub adapters and allowed origins are production questions. Hotwire Native closes the plan: its bridge components are Stimulus controllers, and its shells drive Turbo visits.
If you already write Rails views, begin at Page Navigation and keep the browser modules for the follow-up questions you cannot answer. If you come from a single-page framework, spend real time on Turbo Drive and Frames first, since most early mistakes come from expecting a client-side router and JSON. With an interview a week or two away, raise importance to must know and work through navigation and Live Updates before Stimulus. Senior candidates should be ready to argue morphing against targeted streams and to explain how broadcasts reach every app server. Set aside the Mobile Apps module unless the job mentions iOS or Android. The plan covers the browser side of Hotwire and the transport behind its broadcasts. Routing, controllers, partials, layouts, forms and the asset pipeline that serve the HTML are Rails itself, and the [Ruby on Rails roadmap](/roadmaps/ruby-on-rails) covers them.
If you already write Rails views, begin at Page Navigation and keep the browser modules for the follow-up questions you cannot answer. If you come from a single-page framework, spend real time on Turbo Drive and Frames first, since most early mistakes come from expecting a client-side router and JSON. With an interview a week or two away, raise importance to must know and work through navigation and Live Updates before Stimulus. Senior candidates should be ready to argue morphing against targeted streams and to explain how broadcasts reach every app server. Set aside the Mobile Apps module unless the job mentions iOS or Android.
The plan covers the browser side of Hotwire and the transport behind its broadcasts. Routing, controllers, partials, layouts, forms and the asset pipeline that serve the HTML are Rails itself, and the Ruby on Rails roadmap covers them.