81–90 of 150 posts
Earlier quoted context omitted.
This is more of an HTMX native
Yeah, the moment I read "Serve your app as XML" my brain instinctively began to move on but it's really just HTML-like semantic snippets that remind me of WebComponents. Example: https://github.com/Instawork/hyperview/blob/master/demo/back... However, this warning statement should be in bold at the top: "If your app relies on offline data or local computations, Hyperview won't be the right choice." For that reason, I…
For the love of God, stop putting "Native" in web frameworks. No, React will never be native.
Earlier quoted context omitted.
Minions of people use SAP daily that does not mean it's a nice thing to interact with.
I agree that numbers alone might not mean much, but I do think B2C apps with millions of users have a higher bar in terms of design and polish compared to B2B/ERP apps. Also, fixed typo!
Using web technology to build "native" mobile apps has been around almost as long as mobile apps themselves. I used Appcelerator Titanium and Phonegap to do this beginning in 2012 (maybe even 2011) before eventually trying Native development later after finding these options underwhelming. I have a reasonable amount of experience doing both, and my opinion is that development tools aren't really the problem. The bigg…
It takes a very insignificantly small amount of JavaScript to make a website a Progressive Web App, which iirc can be listed on app stores.
If you dont use React or any fancy frameworks, I believe last time I ever did such a project our JS was under 50 lines of code to have our PWA working fully offline. There were some odd hacks, like detecting network connectivity.
Earlier quoted context omitted.
Just because there are multiple technologies does not make it complicated per se. Indeed, something could evolve to a simpler model, which it seems RSC on RN is.
Keep dreaming man. Just look at what Next has become... It has taken "render component on the screen" and turned that into an experts domain. It's a nightmare for anyone who isn't the most skilled, for projects that are more than just toy apps and AI one-offs.
Any "app" framework that isn't offline-first seems broken by default to me. It seems ridiculous to me that client-server architecture is considered the easy thing now. Where did it all go wrong?
When companies decided that they need to know as much as possible about the end user, and don't want to care about backwards compatibility (old version apps, all users are using latest)
Using web technology to build "native" mobile apps has been around almost as long as mobile apps themselves. I used Appcelerator Titanium and Phonegap to do this beginning in 2012 (maybe even 2011) before eventually trying Native development later after finding these options underwhelming. I have a reasonable amount of experience doing both, and my opinion is that development tools aren't really the problem. The bigg…
> Just build it on the web. It takes a very insignificantly small amount of JavaScript to make a website a Progressive Web App, which iirc can be listed on app stores. If you dont use React or any fancy frameworks, I believe last time I ever did such a project our JS was under 50 lines of code to have our PWA working fully offline. There were some odd hacks, like detecting network connectivity.