jbamberger / fhg-android-app Goto Github PK

The layout of the VPlan was reverted to the original layout. This causes the apps parser to fail. Therefore the app stops updating.
The easiest fix is to roll back to version 3.0.2, since only the feed layout and vplan layout changed since then.

Two alternatives:

• As an entry in the about section
• As a menu item

The current feed implementation is uncached (expect for the okhttp cache). Therefore loading is slow and uses a lot of bandwidth.

A solution should satisfy the following points:

1. work with the paged loading
2. allow for updates to articles
3. allow for the deletion of articles
4. delete old entries to avoid infinite growth
5. work seamless with the network data

The support for wide / tablet devices is quite bad at the moment.

1. Feed split into multiple columns on horizontal / tablet devices
2. Contact screen should relocate the FHG logo or remove it completely
3. The settings are quite ugly on 7 inch screens
4. Cap the VPlan header text width or split the content into multiple columns on wide screens

Describe the bug
Clicking the menu item "Online Vertretungsplan" opens the legacy substituions site. This site has not been updated since 07th of October 2020.

Expected behavior
The WebUntis substitutions site should be opened

The Feed is shown in reverse, i.e. the newest item is at the bottom.

Androidx is stable stable and will replace the android support packages. Therefore the application must be migrated to androidx, since the com.android.support packages will not receive updates anymore after the next major system release.

Proguard notes some classes and misconfigurations.
The reflection json converter should be replaced with generated converters to save space (the kotlin reflect dependency is necessary for the reflection converter).

The VPlan format changed and therefore broke the parser.

Primary focus should be to restore the function of the application.
The new format provides more information, which should be shown in the Application.

Add a direct link to the website, such that parser errors can be confirmed easily.

Travis CI provides free continuous integration for open source projects.

Crashlytics provides a free plan which is integrated into the dev console

The java utils module is no longer necessary, since the remaining code is migrated to Kotlin.

The best option would be to process the vplan on a server and push the updates to registered devices. This saves battery and bandwith on the user devices, because no background service must be scheduled.

Add an option to report parser errors directly from the vplan screen, preferably per item, such that the context is preserved.

The report should contain:

• the full html page for the misclassified day
• the exact entry that was not parsed correctly