Working on the v2 version of the API, it will have OpenData support and syncing capabilities. Now all of the data will be internal to a database and allow users to custom insert their own routes/trips/schedules. That way it allows for easier access. Unfortunately with this comes the deprecation of the older API specifications but the newer one seems cleaner.
Woah, more changes since the last devlog, and many helpful ones. In my attempt to provide a more developer friendly library, I switched from using the API to using saved data. The tldr is that after a bit of research, I was able to find an official GTFS (General Transit Feed Specification) from the transit entity under my gov’s opendata platform. As such, I am beginning the process of an automated migration of those data to an internal library database. Furthermore, i fundamentally reworked the library to use multiplatform compose - and as such support to many platforms.
Finished iteration v1.0 of the bus tracking api with a tracker using kotlin coroutines and channels
oh my god this notion library is going to be the bane of my existence.
