"Serve your app as XML" As someone who started his professional career in 2005: All the old is new again.
[deleted]
Hyperview – Native mobile apps, as easy as creating a website
101–110 of 150 posts
Re: Hyperview – Native mobile apps, as easy as creating a website
#102Not even a day after the post about HTMX not living up to its promise! There are only two certainties in life, death and frontend churn.
> frontend churn. Frontend churn hasn't been as much of a thing for years now, see e.g. https://2022.stateofjs.com/en-US/libraries/front-end-framewo... . If you stuck with Angular or React 10 years ago, you're still good today. jQuery is even older but still on 75% of websites ( https://w3techs.com/technologies/overview/javascript_library ), and Bootstrap is on nearly a quarter. Frontend churn is only a thing if you…
React didn't have hooks 10 years ago, but at least they're compatible with classes
Re: Hyperview – Native mobile apps, as easy as creating a website
#103Earlier quoted context omitted.
That’s only true on the surface: if you chose React, you had to rebuild and relearn everything about once every two years. Averages out to about the same workload as following the latest fad. Maybe more, since refactoring legacy code is 10x harder than building from scratch.
this is just not true. even the worst offenders (looking at you, react-router) do not require to "rebuild and relearn everything". What an unnecessary hyperbole.
Maybe not React itself, but the ecosystem as a whole. I can list some of these changes that generated a lot of work from memory:
- the move from in-browser JSX compilation to build tools / webpack
- the move from class components to functional components and hooks
- all the changes related to ES6 classes and modules + build system
- server-side components
- Flux -> Redux
- Redux -> MobX -> Relay -> Redux Toolkit -> Context API -> Zustand / Jotai / Recoil -> react-query (next: zero?)
- Next.js and Remix, 7 react-router versions (latest with major breaking API changes again)
- Signals and more SSR stuff (I stopped looking at this point)
And this is ignoring all the React Native churn over the years as I imagine not everyone is involved with that.
Even if your particular project didn’t go through all of these migrations, you had to relearn things to be able to work in other/newer projects.
It’s impossible to measure, but having written and used a ton of different frameworks, I really do feel like the overhead of keeping up with the changes was equal to or larger than learning a new one every couple years.
Re: Hyperview – Native mobile apps, as easy as creating a website
#104Earlier quoted context omitted.
Three things you need: * Manifest file * HTTPS - for localhost I dont remember the workaround, browsers have made this increasingly more complicated from recent experiences * Service Worker - This is where I said I had maybe 60 lines of JavaScript. If you have these three things, a browser should pick up that your sites a PWA and server running it should be irrelevant... So you MUST have a minimal amount of JavaScrip…
The service worker thing is a weird amount of boilerplate. Every time I go back to making a PWA, I skip through 10 search results explaining what a service worker is (idc) until I just find whatever .js code I have to copy. And it's not some trivial one-liner. I get that in theory a PWA can do offline stuff and whatever, but 99% of the time someone is only making a PWA to make the app installable on a phone home scre…
It is not a trivial one liner no, but you need 3 events implemented in your service-worker file, then in your main.js file you register it.
Service workers are just JavaScript that runs in the background in their own process in a browser. Could think of them as separate threads. Anyway, all of that can be done in less than 20 lines of JS?
I consider it simple compared to people building React apps and making the process more complicated than it needs to be just to build a PWA.
I was able to build a PWA out of a bootstrap HTML5 web app, with minimal JS for REST calls and ag-grid population.
Re: Hyperview – Native mobile apps, as easy as creating a website
#105I am very unclear reading the documentation and clicking around, how do you actually implement the logic? Some sort of JavaScript runtime?
Its a client/server system. So the logic is done by the server and snippets of HXML are served:
https://hypermedia.systems/building-a-contacts-app-with-hype...
That's an example using Flask. There's a demo client bundled with the repo, but I assume you can customise and deploy it. I'm not familar with Expo.
Re: Hyperview – Native mobile apps, as easy as creating a website
#106Earlier quoted context omitted.
> frontend churn. Frontend churn hasn't been as much of a thing for years now, see e.g. https://2022.stateofjs.com/en-US/libraries/front-end-framewo... . If you stuck with Angular or React 10 years ago, you're still good today. jQuery is even older but still on 75% of websites ( https://w3techs.com/technologies/overview/javascript_library ), and Bootstrap is on nearly a quarter. Frontend churn is only a thing if you…
Angular of 10 years ago... you mean the 1.0 framework that's wholly incompatible with 2+ because it was a ground up re-write?
[deleted]
Re: Hyperview – Native mobile apps, as easy as creating a website
#107Earlier quoted context omitted.
I mean those 1st party integrations directly listed in WeChat services page are probably good examples of services that "feel" nice to interact, because they are used by millions of people everyday and they are need to optimized and polished to be able to serve millions of users. Here's a screenshot of the list, if you want to Google and check out some of them: https://imgur.com/a/KKEdliE
There's a pretty big difference in what UX "feels nice" to East Asian audiences vs Western audiences. This video provides some insight into why this might be: https://www.youtube.com/watch?v=WSMFnJnY7EA
The comments make it seem like it's more a case of users tolerating it due to the apps usefulness. Interesting video though, haven't had any contact with Chinese apps, so that was enlightening.
Re: Hyperview – Native mobile apps, as easy as creating a website
#108Using 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…
What I have learned after all these years, is either do a Web site that is mobile friendly, or go native, anything else is a kludge in the search of holy grail of cross platform development without costs.
However this is a lie, because after going after the dream of cross platform, one lands on the (N + 1) reality, with team having anyway to master the leaky abstractions of the underlying platforms.
Re: Hyperview – Native mobile apps, as easy as creating a website
#109Using 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…
This * 100. I have a lot of experience with these types of apps and the biggest issue I've encountered is the platform keeping up with native technologies and OS updates.
Re: Hyperview – Native mobile apps, as easy as creating a website
#110Using 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…
[deleted]