I'm currently working with the guys from the ITSZ to get an account rolling, so we can publish the app.

Hope to have everything set up by next week, so we can publish a first version starting with august.

Please test this.

Fixes #190 Fixes #179 Fixes #118

Fixes #72 Fixes #109 Starts progress in #43 & #165 Fixes #156 Fixes #90 Fixes #195 Fixes #194 Fixes #121

This redoes the entire networking layer and removes SwiftyJSON and Alamofire from our dependencies.

It makes our networking a bit more type-safe and relies less on casting.

And it introduces caching

Fixes #72 Fixes #109 Starts progress in #43 & #165 Fixes #156 Fixes #90

While I was at it I also fixed: #121 with the same workaround as android

The current onboarding screens have the following problems:

• The text is a mix of German and English.
• The text-only layout is not very inviting.
• The spelling of TUMonline is wrong.

Here’s a potential update to the onboarding screens:

Let me know what you think.

Open questions:

• The three separated textfields are odd. For a cleaner layout, they could be replaced with a button that opens an alert with a textfield, where the user can enter their TUM ID. Opinions?
• We could use some sort of illustration as eyecandy, for instance the sketch of the TUM tower. Opinions?

I've noticed that a lot of our issues happen because we're not testing enough due to time constraints. Maybe be should consider opening up a beta trough TestFlight or Crashlytics.

Thoughts?

We will have a grant from the F13 chair to print a few posters for the new iOS release.

Someone up to designing it? I think I have the PSD for the Android one somewhere... Let me know.

@mammuth and I were thinking it's about time to do a release Party!

I'd say that after the next release of 1.1 with all the bug fixes we can all celebrate together!

Since @kordianbruck is always so eager to organize things, I suggest he should be in charge.

I implemented the basic functionality of the Study Rooms Feature. It's linked in the More-View, fetches the rooms, and displays them in a sorted manner

Big ToDo's:

• [x] Decide on how to handle groups (sections vs. Picker as for movies vs. ?) (Right now there are only 3 groups: "Bibliothek Mathe/Informatik", "Magistrale Mathe/Informatik", "Garching-Hochbrück (EG)"
• [x] Link to Room Maps on click (of the whole row?)
• [x] Pull To Refresh (?)
• [ ] Make layout "better" (I just moved the labels around to have "something", let's add some constraints)
• [x] Hate me for my color choices (Optional)

@mathiasquintero it'd be great if you could check this out and tell me whether I heavily ignored the wished patterns and concepts ?? Also I'm pretty sure there is room for small improvements at many places.

The API request returns a JSON with rooms and groups in it. I'm not quite sure how to handle this, currently our TumDataReceiver is made to receive [DataElement]. Same for the Handlers. Any views on that?

I think we should implement the slides from the news screen in the app. The api looks straight forward and easy to use: rss. Maybe using cards like this.

See Ticket #880490

So far we get the user details by a search with the exact name and filter the list a bit afaik. Perhaps tinker with the filtering a bit or try to fetch it from the LRZ id.

So from what I've tested the app does not seem to cache most of the data. Most noticebly it happend several times that the app was unresponsive due to load some data (10-20 seconds in the case of the calendar).

We will run into problems with the TUM. Especially the calendar uses a lot of resources on their mainframe. That should be updated once every 7 days or so at the very most! (Ask @xsrf for more details on this)

Please take a look at the Androids caching mechanics: https://github.com/TCA-Team/TumCampusApp/blob/master/app/src/main/java/de/tum/in/tumcampusapp/managers/CacheManager.java

Push Notifications Service => BA Anton

• First PR for setting up basic push notifications integration
• Implemented Campus Backend gRPC Client
• Added device registering to the campus backend

I was thinking about into cloning my student card into a smaller form factor like a ring or wristband when I looked into this thread on the apple support page and found out that Digital StudentCards on IOS are actually a feature at other universities campus apps.

If anybody with the necessary knowledge, enough time and ambition wanted to look into the implementation of this feature: Please do so I’d love to see the function on my own phone and watch one day!

Otherwise even just seeing this suggestion getting a spot on the roadmap of planned features would be amazing.

I was not able to find a official page to suggest features, neither did I find this feature on your roadmap, so I hope it’s not a problem for you, that I went ahead and posted it as an “Issue”.

Thank you for reviewing my request :)

PS: to the ones who implemented the new “Home” Page/Tab in the IOS App, I joined the test flight Program for beta testers and I love it :D

Unlike the iOS and iPad OS Versions, the Mac Campus app doesn't show the switch to select day, week or month view above the calendar so you're stuck in day-view.