Progressive Web App

1 Initial Problem

Based on Basic ILIAS APP - with differences (= no reference to app stores due to Progressive Web App approach)

E-learning in schools takes more and more place on mobile devices such as tablets. Schools that investing in IT equipment do no longer buy standalone computers or laptops but tablets. Hardware providers like Apple or Samsung are actually pushing this by special projects and conditions for German schools. This change has also a strong implication on how e-learning applications are used today. Teachers and pupils are more and more focused on apps. For example, Apple released the app „iTunes U“. This allows the management of learning materials and course management. Although the system is far inferior to the functionalities of ILIAS or other LMS, it is very popular in schools as it is available as an APP.

Teachers and pupils want an icon on their tablet that starts their ILIAS installation without logging in. But it doesn’t matter if this installation is presented in a browser. A native app is no requirement. Most of these users do not even know the difference.

The already existing Pegasus App is not a solution for these schools. They do not want - or are not able - to pay the annual fee for using it. They also do need most of the features offered by Pegasus and prefer not to have concurrent tools in both systems. The basic requirement for these schools is just a simple app that authenticates the user and opens her/his ILIAS installation on the tablet (or mobile phone).

2 Conceptual Summary

Contrary to Basic ILIAS APP this approach focuses on the "Progressive Web App" framework. It will therefore NOT be available in Apple App Stores / Google Play Store.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Kiegel, Colin [kiegel]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.