Make oSparc a Progressive Web App (PWA)

[jsaq007]

Title: As a user, I want the web app to function as a Progressive Web App (PWA) so that I can have a seamless, app-like experience across devices, even when offline.

Description:

Users currently interact with the web app through a standard web browser. While this works, they want the convenience of using the app as if it were a native application. This includes offline access, push notifications, and the ability to install the app on their home screen or app drawer. By converting the existing web app into a PWA, users will enjoy faster load times, offline capabilities, and a more engaging experience.

Additional Notes:
User Training: Consider providing a brief tutorial or notification to inform users of the new PWA capabilities and how they can install the app on their devices.
Performance Monitoring: Implement analytics to track the usage of PWA features, such as installation rates, offline usage, and push notification interactions, to gauge user engagement and adoption.

• Installable on Home Screen: #1676
  Users should be able to install the web app on their device's home screen/app drawer.
  The app should have a custom icon and launch screen, and should open in a standalone window rather than in a browser tab.

• Manifest File: #1678
  A web app manifest file should be included, specifying the app name, icons, theme color, and other relevant metadata to enhance the native app-like experience.

• Browser Compatibility: #1679
  The PWA should be compatible with major browsers, including Chrome, Safari, Firefox, and Edge, across both mobile and desktop platforms.

• Device size exclusions: #1675
  Load page for devices under our size specification. i.e 1179 x 719 and less

• Responsive Design: #1677
  The app should be responsive and function well across a range of devices and screen sizes, from mobile phones to desktops.

• Offline Functionality:
  The app should be able to cache necessary resources and allow users to interact with the app offline, at least for critical functionalities.
  If the app requires online data that isn’t available, it should notify the user and display a custom offline page or cached content.

• Fast Load Times:
  The app should load quickly, even on slow networks, by leveraging service workers and caching strategies.
  The first visit should register the service worker and cache essential assets.

• Push Notifications:
  The app should be capable of sending push notifications to users for important updates, provided they give permission.
  Users should have the ability to manage their notification preferences.

• Secure (HTTPS):
  The app must be served over HTTPS to ensure secure connections, which is a requirement for PWAs.