Your new post is loading...
Mobile browsers for Android such as Firefox, Opera, or Chrome support Progressive Web Applications. PWAs are somewhere between a mobile page and a native Android app. Unless the features involve real-time graphics processing or other features that require high-use computational resources, a PWA is surprisingly capable of offering an experience indistinguishable from mobile apps. It can handle virtually every one of their features, from a menu icon to offline access, notifications, and use of the mobile device’s camera and sensors.
Moodle users can take advantage of the Moodle Mobile apps to access their site (provided it’s enabled) and enjoy features such as offline access to many activities and notifications. But a Moodle PWA could offer some additional benefits:
* Moodle PWA could be lighter than the native Moodle Mobile app. (Large offline content such as videos notwithstanding.) PWAs can offer offline content without a problem.
* Updating the PWA could be easier and quicker, and the updates would not have to wait for the bi-monthly release of Moodle Mobile updates.
* It could be easier to entice users to turn a website visit into a direct installation of the PWA without having to take the extra step of going to the app store.
Moodle users can take advantage of the Moodle Mobile apps to access their site (provided it’s enabled) and enjoy features such as offline access to many activities and notifications. But a Moodle PWA could offer some additional benefits:
* Moodle PWA could be lighter than the native Moodle Mobile app. (Large offline content such as videos notwithstanding.) PWAs can offer offline content without a problem.
* Updating the PWA could be easier and quicker, and the updates would not have to wait for the bi-monthly release of Moodle Mobile updates.
* It could be easier to entice users to turn a website visit into a direct installation of the PWA without having to take the extra step of going to the app store.
Via Miloš Bajčetić
