Very good question, and one I've been trying to answer in a concise way. Essentially it's "static" in the sense that it could be used to generate a fully rende

Very good question, and one I've been trying to answer in a concise way. Essentially it's "static" in the sense that it could be used to generate a fully rendered page that is also an interactive (javascript) application. It can also process actions on the server and generate a new HTML page in response to that that will be hydrated in the client. It's an attempt to give you the best-of-both-worlds with a SPA, but one that arrives fully-rendered so there are no delays loading content. It's an SSR approach but without using a javascript engine or framework on the server, the server-side component is completely developed in Rust. As far as "static app", I would say it's closer to something like Disqus being used on a static doc site or Firebase used for storage when github pages are used to host a site. It means it doesn't rely on server-side rendering to function as a PHP or ASP.net site does, but it can use it if available.