Skip to content
Snippets Groups Projects
Select Git revision
  • drop-django-two-factor-auth
  • weblate-frontend
  • master default protected
  • check/update-pyproject-toml
  • check/update-builddeps-package-json
  • check/update-tox-ini
  • migrate-crud-to-vue-3-and-generalize
  • 1182-migration-to-vue-3-and-vuetify-3
  • feature/object-routes
  • stable/4.0.0
  • fix/migrations-leftovers
  • migrate-to-uv
  • 1307-free-busy-feed-does-not-handle-recurrences-and-date-ranges-correctly
  • 1268-add-specific-availability-planning-frontend
  • db-init
  • 1259-generalise-places
  • 1298-vcard-content-type-and-version
  • tmp-ticdesk-4-0
  • 1297-freebusy-calendar-does-not-work-over-caldav
  • 1288-email-field-of-person-form-has-to-pass-empty-string-instead-of-null
  • 4.0.3 protected
  • 4.0.2 protected
  • 4.0.1 protected
  • 4.0.0 protected
  • 4.0.0.dev16 protected
  • 3.2.2 protected
  • 3.1.7 protected
  • 4.0.0.dev15 protected
  • 4.0.0.dev14 protected
  • 4.0.0.dev13 protected
  • 4.0.0.dev12 protected
  • 4.0.0.dev11 protected
  • 3.2.1 protected
  • 3.1.6 protected
  • 4.0.0.dev10 protected
  • 4.0.0.dev9 protected
  • 4.0.0.dev8 protected
  • 4.0.0.dev7 protected
  • 4.0.0.dev6 protected
  • 4.0.0.dev5 protected
40 results
Blame Permalink
20_pwa.rst 2.55 KiB

PWA (progressive web application)

What is a progressive web application?

A PWA is an application developed with common web technologies and delivered in form of a website, but which offers some features a traditional website does not and overall creates an impression that resembles that of a native application.

AlekSIS PWA features

The AlekSIS PWA offers the following features (not all available on all platforms):

  • Installable and displayable in a separate window
  • Caching and serving, if given page cannot be accessed, of non-interactive pages and needed assets
  • Provision of an offline fallback page if wanted page cannot be accessed and there is no cached one
  • Indicator whether the served page is served from the PWA cache

Installation of the PWA

The procedure to get a native feeling using the AlekSIS PWA varies from platform to platform. On some, you are prompted to add AlekSIS to your home screen of desktop using a popup; on others, you have to take action yourself and find the corresponding menu entry. As of the time of writing, “installable” PWAs are supported by all major platforms except Firefox Desktop and Safari Desktop which nevertheless support the other features.

Chromium-based browsers (e.g. Chromium, Google Chrome, Microsoft Edge) will usually prompt you to install the PWA by a popup on both mobile and desktop devices; for the former using a banner

PWA installation prompt on the mobile version of the Chromium browser

and for the latter using an appearing button in the address bar.

PWA installation prompt on the desktop version of the Chromium browser

In both cases, a click on the notification is enough to start the installation process.

Firefox Mobile will also prompt you using a dot near the menu button; then Install has to be clicked.

PWA installation prompt on the mobile version of the Firefox browser

On Safari Mobile, you need to open the share popup and click on the Add to Home Screen button.

PWA installation prompt on the mobile version of the Safari browser

No matter what platform is used, AlekSIS can be accessed as an independent application entry, just like any other installed native application, after installation.