Applications that run in the browser.
WHAT THEY DO
Build interfaces that update without reloading the page.
WHY THEY EXIST
For applications with complex interaction: dashboards, editors, anything behaving like software rather than a document.
WHAT THEY PRODUCE
Either files served like a static site, with the application running in the browser.
Or a server application rendering pages, which needs a server capable of running it.
THE DISTINCTION THAT MATTERS FOR HOSTING
Output that is plain files: works on any hosting, including shared.
Output requiring a running process: needs a server that supports it.
WHAT SHARED HOSTING SUPPORTS
Static output, always.
Server-side rendering, generally not.
WHAT TO ESTABLISH BEFORE BUILDING
Which kind your project produces.
Discovering after building that it cannot be hosted where you intended is an expensive surprise.
WHO NEEDS ONE
Applications. Not brochure sites.
