An alternative mobile client for the Untis timetable system.
You can download the latest automated debug build from my website.
It was more and more obvious that my original version of BetterUntis had many design and performance flaws. As a result, development became increasingly more difficult. So I came to the conclusion to scrap the project and start over from scratch.
Although I reused some parts of the original code, my plan was to entirely switch to Kotlin. Kotlin has many features and libraries that immensely help to communicate with the Untis API and process the timetable data.
- Select your school by name or ID, no URL needed
- Login by optionally using your password instead of app key
- Zoomable timetable view
- Improved overall design
- Improved timetable selection dialog
- Faster RoomFinder
- Near instantaneous timetable loading
- Lag-free timetable scrolling
- Flexible timegrid allows to display hours outside the regular timetable (like consultation times with teachers)
- Support for multiple accounts
- Support for using a custom proxy server for increased privacy
- Info Center for viewing events, contact hours and own absences.
Missing features (TODO)
No support for teacher-specific features (like editing homeworks or class management)- This is currently being worked on. View progress in the absence-check branch.
- Almost no unit and integration tests
Versions since 3.3.0 will also include:
- Chinese (Simplified)
- Norwegian Bokmål
Project Git Structure
I established a simple system to manage this Git repository. Basically, there are two main branches: master and develop. They both are permanent and can't be deleted.
This branch always and only contains the latest release version. This includes alpha/beta releases.
This branch contains the current development version. Small changes and fixes can be committed directly to this branch.
When it reaches a state ready to release, it can be merged into the master-branch and a new release can be published.
Especially bigger features which require multiple commits should branch off develop and merge back into it. These should be named in a way to describe the feature as clearly as possible.
These branches have a limited lifetime. After the last merge back into develop, they should be deleted if no longer needed.
Translating into your language
There you can click the “Start new translation“ button if your language does not exist. If your language already exists, you can directly correct possible mistakes.
Your translation will be included in the next release of BetterUntis.
Implementing new features / Fixing bugs
Anything that requires you to perform code changes should be done on the develop branch. Pull requests should always be based on this branch, except for larger, experimental or incomplete features. These can be on their own, new feature branch.
Please do not submit pull requests that merge into the master branch, except for changes that only affect the repository on GitHub (e.g. README.md changes).