Feature Wiki
Tabs
(Project) improve mobile Support for ILIAS
Page Overview
[Hide]1 Aim of Project
The aim of this project is to enhance the mobile-friendliness of ILIAS by envolving features and user experience. Based on user-surveys (see below) the needs of its users: students, educators, and learners in vocational learnings shall be adressed.
1.1 targeting mobile devices
In an increasingly interconnected digital landscape, mobile technologies have evolved into the central interface through which individuals engage with their enviroment. Targeting mobile devices ILIAS will be part of this. This, however, does not imply that the use of desktop devices has lost its relevance. Rather, the emphasis should increasingly shift toward addressing mobile platforms and leveraging the opportunities they present.
By embracing a mobile-first approach, the project seeks to redesign the LMS so it becomes fully responsive, intuitive, and optimized for smartphones and tablets. This shift not only caters to the technical realities of the target audience—many of whom rely primarily on mobile devices—but also supports greater flexibility, accessibility, and learner autonomy.
1.1.1 User Survey ILIAS.nrw
In July and August 2024, ILIAS.nrw carried out a representative user survey focusing on required enhancements for mobile usage and the types of devices employed. The insights gained from this survey provide a solid foundation to ensure that future developments are closely aligned with the needs and expectations of our users.
As part of ILIAS.nrw, a survey was conducted at a university in NRW to explore which features are considered important or unimportant by users when accessing ILIAS via mobile devices. A total of 543 participants shared their perspectives on this topic.
Sample size: 543 participants (124 instructors, 419 students)
Translation of the displayed graph:
Answers: 1. Automatic login, 2. Access via an app icon on the device’s home screen, 3. Adaptation of text size and buttons, 4. Content sharing, 5. Notifications (push notifications), 6. Design elements consistent with the operating system, 7. Take and upload photos
Rating: From green (very important) to brown (not important at all)
As part of the same survey, participants were asked which devices they use to access ILIAS. Out of 607 respondents, 442 indicated that they use a smartphone to access ILIAS. Among the 124 instructors surveyed, 62 reported using a smartphone for ILIAS - exactly half. Notably, among the 419 students, 380 stated that they use a smartphone for ILIAS, which is over 90%. At the university surveyed, there are approximately 10,000 enrolled students; extrapolating from these results, more than 9,000 students are likely using a smartphone to access ILIAS.
The participants were also asked which tasks they perform in ILIAS on their smartphones and how they would rate their experience using these functions.
Sample size: 442 participants (62 instructors, 380 students)
Translation of the displayed graph:
1. Display of content, 2. Editing of content, 3. Communication and sharing of content
Rating: From green (very good) to ochre (inadequate) - brown (don't use it)
1.2 targeting individual learning
Mobile accessibility enables students to engage with learning content in a manner that aligns with their individual rhythms and preferences—whether during commutes, transitional moments between classes, or from the comfort of home. This flexibility fosters self-directed, personalized learning journeys that adapt to diverse needs and contexts. At the same time, educators benefit from intuitive, mobile-optimized tools that allow for responsive course management, timely feedback, and learner-centered communication.
1.3 targeting ILIAS Core development
The project should focus on core development. This way, several issues are avoided:
- All development benefits usage across all device classes.
- ILIAS-Functionalities do not need to be implemented multiple times.
- Adaptations to the needs of the instance operators (branding) only need to be made in one place.
- In combination with a mobile-first approach in development, all components benefit from improved usability.
Overall, with a core-driven approach ressources spend for develeoping will enhance not just the mobile Support. Therefore no specific App / several Apps shall be developed.
1.4 merge existing initiatives
The project page is also intended to consolidate existing efforts aimed at enhancing mobile-friendliness. These initiatives are currently spread across different components and exist at varying stages of maturity. As a centralized overview, the project page should therefore serve to make the conceptual potential visible. Therefore every every FeatureRequest can be added by the author.
SIG mobile
https://docu.ilias.de/go/grp/5182
1.5 Effiencient and ressource-friendly development
In the ILIAS developments, there are partly contrary Concepts to the implementation of ILIAS on mobile devices. The project aims to consolidate these efforts in order to use financial and developer resources more effectively.
Furthermore a mobilefriendly ILIAS Usage shall not be limited due to ongoing maintenance and usage fees.
2 Involved Authorities and Stakeholders
- upcoming
3 Timeline
ILIAS 11 |
|
---|---|
ILIAS 12 |
|
ILIAS 13 | |
... | ... |
... | ... |
4 Related Feature Requests and Status
Feature Request | Suggested by | Funding | Planned Release | Status |
---|---|---|---|---|
funding required | ILIAS 11 | JF needed | ||
funding required | ILIAS 12 | JF needed | ||
funding required | ILIAS 12 | JF needed | ||
… |
Feature Request | Suggested by | Funding | Planned Release | Status |
---|---|---|---|---|
The mobile functionality of the breadcrumb is not user-friendly | Matthias Becker | funding required | ILIAS 11 | open |
Add hamburger menu for mobile view | Matthias Becker | funding required | ... | Idea |
Adapt tree view layout for mobile view | Matthias Becker | funding required | ... | Idea |
Add Home Button in Breadcrumb | Matthias Becker | funding required | ... | Idea |
... | ||||
… |
Feature Request | Suggested by | Funding | Planned Release | Status |
---|---|---|---|---|
funding required | ILIAS 12 | JF needed | ||
funding required | ... | Draft | ||
Camera as File Upload-Option | funding required | ... | Idea | |
Camera as Mediacast Upload Option | funding required | ... | Idea | |
mobile Contacts as Mail recipient | funding required | ... | Idea | |
... | ||||
... | ||||
… |
General Notification features
Feature Request | Suggested by | Funding | Planned Release | Status |
---|---|---|---|---|
Add Support of Push Notification to the notification component | funded | ILIAS 11 | In Development | |
funding required | ILIAS 12 | JF needed | ||
Push Notification for iOS | funding required | ... | Outdatet due to Add Support for Progressive Web App | |
… |
Implementations
Feature Request | Suggested by | Funding | Planned Release | Status |
---|---|---|---|---|
funding required | ... | Draft | ||
funding required | ... | Draft/ JF needed | ||
funding required | ... | Draft | ||
… |
5 Further Results
- …
6 Additional Information
…
7 General Discussion
Please discuss specific questions of feature requests on the related feature wiki pages. This discussion section is only for a general discussion of the project and its realisation.
Technical Board, … :
UI-/UX-Experts, … :
…
Last edited: 22. Jul 2025, 14:17, Stake, Sebastian [sstake]