I love the concept behind htmx & started reading the book today. But every time I think about using it, I remember that I'll eventually have to support native mobile apps as well and I'll be completely re-writing not only my frontend but much of my backend to do it. I know about hyperview.org but a react-native app won't really cut it for the use cases I'm interested in.
Thanks for the link. I read both Carson's (your?) article and Max's. In general I see the point, but I think what's missing is a htmx-specific Android/iOS app template. Something that wraps a WebView but perhaps preprocess and reacts to mobile specific html tags or special hx-mobile-xxx attribues to existing tags that know how to do special mobile things. I'll have to think more about this.
Comments
I love the concept behind htmx & started reading the book today. But every time I think about using it, I remember that I'll eventually have to support native mobile apps as well and I'll be completely re-writing not only my frontend but much of my backend to do it. I know about hyperview.org but a react-native app won't really cut it for the use cases I'm interested in.
https://htmx.org/essays/splitting-your-apis/
keep your domain logic out of your controllers
Thanks for the link. I read both Carson's (your?) article and Max's. In general I see the point, but I think what's missing is a htmx-specific Android/iOS app template. Something that wraps a WebView but perhaps preprocess and reacts to mobile specific html tags or special hx-mobile-xxx attribues to existing tags that know how to do special mobile things. I'll have to think more about this.