It's created by Basecamp which makes Turbolinks [0], Turbolink iOS [1], and Turbolinks Android (deprecated) [2], so there's a good chance that snappiness you're

It's created by Basecamp which makes Turbolinks [0], Turbolink iOS [1], and Turbolinks Android (deprecated) [2], so there's a good chance that snappiness you're seeing is due to those awesome tools! (In fact, this Github issue comment [3] seems to confirm that HEY uses Turbolinks.) On a related note, really wish things had gone this direction. Instead, it feels like React, Angular, etc. re-created the backend in the frontend, so now for most apps you essentially have two backends plus one frontend to maintain. I think as soon as our frontends started requiring controllers and routes to work we should have been like, "Hey, wait a minute..." But I guess design folks tend to know JS, so I can see how that combo won. My $0.02 from 5+ years in the industry is that you probably don't need React, but Godspeed if you think you do - just maintain extreme discipline or you'll end up with spaghetti code (esp. if contractors are involved) faster than you can blink. Long-term, I hope things move back to sanity. React and company work OK for some problems, but 95% of websites/webapps can probably get by with either straight HTML/JS/CSS or server-side rendering/templating. [0] https://github.com/turbolinks/turbolinks https://github.com/turbolinks/turbolinks [1] https://github.com/turbolinks/turbolinks-ios https://github.com/turbolinks/turbolinks-ios [2] https://github.com/turbolinks/turbolinks-android https://github.com/turbolinks/turbolinks-android [3] https://github.com/turbolinks/turbolinks-android/issues/111#issuecomment-631617956 https://github.com/turbolinks/turbolinks-android/issues/111#... Edit: Formatting