@Tuxilio

I added a lot documentation and an asciinema video: https://asciinema.org/a/BytB6HM8kpoXtlLC

I added a Logo. I am not good at this but it should incorporate both a clock face and a Transport-Network-Map. After creating the Foreground-Part of it in Inkscape, I wasted two entire hours trying to get it into an Android Asset. They don’t directly support SVGs but after converting it in Resource Manager, it was cropped on the Splash Screen, while it wasn’t on the launcher. This drove me crazy. After trying various settings in Android Studio, I decided to just make it smaller. I am pretty sure, the Logo could still be improved but I am definitely not an artist.

There is now an option to save the api token and auto-login with it! The login prompt also shows now automatically when you’re not logged in, making it easier to get a start :) The token save prompt only shows after a successful use of the token, so you can’t really save a wrong token.

I completely redesigned the dashboard! It now looks more like “normal” Traewelling clients and in my opinion much nicer :)

I added symbols for the travelling mode (e.g. suburban, regional rail, tram bus) and you can now also see the status message another one has posted together with the checkin!

I just finished a big feature in my project! The login now works perfectly, and after successfully logging in, you’ll see your dashboard displaying check-ins from people you follow (plus your own, of course). The dashboard isn’t complete yet - I plan to add status messages and a progress bar showing if someone is currently traveling.

I’m building a terminal user interface for Traewelling (https://traewelling.de/) using Ratatui in Rust, with Vim-style keybindings (: for command mode, q to quit, :login for token-based authentication). The basic UI is working well with a header, dashboard body, and mode-specific footer, but still needs polish before the next iteration.

This is my first Devlog. Mover is an App to see the Departures of Public Transit Stops on your WearOS Watch. It uses Transitous as it’s API and (currently) does not require a Companion App. You are already able to see the Departures but the Stops are still hardcoded. This is my next Goal: Have a Searchbar for Stops.

We now have a Search Button! This took so freakin long because I can’t simply add a Text-Field like on normal Android. Instead, I have to invoke an Intent that launches GBoard. Now onto the next Step: Actually making it functional…

The Search is finally working! Well… sort of. As you can see in the Video, there is no “Search Results” Page. It just displays, whatever Transitous returned first. I removed the Hardcoded Stations on the Homescreen and replaced them with Stations, that you previously searched for. My next Goals are a Results-Page and the ability, to see Stations near you.

PS: The Artifacts and Frame-Jumps are related to the encoder of scrcpy. It looks pretty™ smooth in Real Life.

This is just a quick Update: I added an initial ReadMe.md and a search results screen. When you now search for a stop, you will be able to select from multiple results.

Mover can now use your device’s location for showing stops around you! This is implemented using the reverse-geocode endpoint. The requesting of the permission was not easy though. I did not understand how to utilize onRequestPermissionResult so the App will put you back on the Home-Screen the first time you use it. I am a bit unsure on what to work on next. I might add a Screen to show an entire Journey.

I have added an initial view of a whole Journey. It is still very rough and needs a lot more polish, especially with the Text-Wrapping of the Stops. But for now, it works…