Malte Dölker

@Naktibalda just saw your comment (it got lost in the tons of emails raining down on me). My take is that we are looking at two different use cases here....

Looks like `/index/stops` in combination with `/index/routes` will get us all the data that is needed. We could also generate a more condensed version daily and have the app download...

Hmm looked into it a bit more and its not easy to relate them with these endpoints. Having looked into graphql a bit lately I was able to extract the...

We have to query the lines in a way that returns them only for the area we look at though if we keep adding new cities. Will check if the...

When the itinerary is opened, the overlay with the routes/lines shifts up as well. The line should be connected to the pier. 

Please note that while this use case of push notifications is now generally allowed on iOS, it requires user consent via an opt-in setting.

Also note that we need some kind of backend to keep track of the device tokens used to send notifications (e.g. Firebase), i.e. this is not a frontend only change.

Renamed this to make it clear that this is not mainly about push notifications, but about how to inform the user about anything that is happening with Trufi App or...

This is rather complex. On the technical side, we need a backend that allows us to write and send news/notifications and handles device tokens. The app needs to handle the...

We could add a priority column to the search data that the client can sort by. This can be calculated based on different signals, for example the place you suggested.