Re: Web application framework and Smartphone apps

I'm not a big fan of using "fat" client-side Javascript to implement what would otherwise be static content.

For something more "app-like" (a weather information app), I had great success with using Perl to prepare the JSON and then Javascript to implement a Progressive Web App on the client side to render the JSON into something interactive.

I've given a presentation about this and the code is online as Weather::MOSMIX and https://github.com/Corion/PWA-WeatherClient for the client-side Javascript.

Comment on Re: Web application framework and Smartphone apps

Replies are listed 'Best First'.
Re^2: Web application framework and Smartphone apps by monx663 (Sexton) on Apr 06, 2021 at 10:46 UTC
Thanks for the input, Corion. As an Android user, who's a seasoned web systems developer, I'm sick and tired of being asked to download apps from whatever app store, to do things that are easily done by visiting a responsive web site. There are times that an app is needed, as I have recently found out with a mini web app I wrote for tracking a mobile device using the browsers' geolocation api and feeding the positions to our server via AJAX and JSON. Despite my attempts for power management and permissions to the mobiles' Firefox, my "tracker" web app kept going to sleep when the screen of the phone went off, or the browser went to running as a background app. Apps seem to make better use of the device than a browser app does. I am actually all for abolishing app stores and pushing users to apps developed in the browser, either with frameworks like React and AngularJS or by ensuring that web sites cater for every client, using well defined and corporation neutral technologies.	[reply]

Replies are listed 'Best First'.

Re^2: Web application framework and Smartphone apps
by monx663 (Sexton) on Apr 06, 2021 at 10:46 UTC

As an Android user, who's a seasoned web systems developer, I'm sick and tired of being asked to download apps from whatever app store, to do things that are easily done by visiting a responsive web site.
There are times that an app is needed, as I have recently found out with a mini web app I wrote for tracking a mobile device using the browsers' geolocation api and feeding the positions to our server via AJAX and JSON.
Despite my attempts for power management and permissions to the mobiles' Firefox, my "tracker" web app kept going to sleep when the screen of the phone went off, or the browser went to running as a background app.
Apps seem to make better use of the device than a browser app does.
I am actually all for abolishing app stores and pushing users to apps developed in the browser, either with frameworks like React and AngularJS or by ensuring that web sites cater for every client, using well defined and corporation neutral technologies.

[reply]