4 ms·
This is a really beautiful approach IF you don't need mobile. If you do need mobile, then you may be better served (pointlessly) running React on web and re-usi
by nikodunk 4y ago
This is a really beautiful approach IF you don't need mobile. If you do need mobile, then you may be better served (pointlessly) running React on web and re-using all of the logic/fetchers, etc for React-Native on mobile IMO.
Your other option would be to do something like 37 Signals and render web with htmx (or in their case Hotwire) and server-render mobile too, but wrap the web views with a thin native mobile navigation layer to make it feel more native.
Very jealous if your project is web-only - this can work wonderfully and be incredibly efficient! I've been thinking about this a lot recently and also just blogged about it (https://nikodunk.com/2022-05-10-the-tech-stack-for-maximum-efficiency/ https://nikodunk.com/2022-05-10-the-tech-stack-for-maximum-e...).
- paulryanrogers 4y agoEfficient for dev time, not so sure about mobile app size, RAM usage, or response time.
- nikodunk 4y agoDefinitely! Wasn't considering the other 3 in this discussion. The most efficient for all of these is most likely a native app everywhere, and all the complexity/duplication that brings.
- recursivedoubts 4y agoIf the hypermedia approach really grabs you, you could pair an htmx-based web application with a HyperView-based mobile application: https://hyperview.org/ https://hyperview.org/
- haolez 4y agoI can't decide if this is awesome or terrifying. Will try it out :)
- recursivedoubts 4y ago:) why not both?
- nikodunk 4y agoThis is super interesting - thanks for sharing!
- canadianfella 4y ago