I started building BootISO, an EFI application to boot ISO images from GRUB/rEFInd, the EFI shell, or (on some systems and probably not really viable), the Boot Options menu.
Currently, it opens a file handle to an ISO file, which in further development will be copied to a ramdisk, which can then hopefully be used for booting. Unfortunately, neither OVMF nor my laptop seem to support Simple File System, so I’ll need to check how to load the file instead.
Up to there, there aren’t any errors, so I feel quite confident, although a debugger might end up coming in handy …
I’ve gotten used to the architecture of the UEFI crate by now, which should probably speed up development and reduce AI usage further along.
(edit: it turns out I accidentally used the LoadedImage handle to initialize SimpleFileSystem 🤦)

You can now change the Transport Types that the Application will use for Routing! For me, this is very practical because I am not able to take High-Speed Rail with my Ticket here in Germany.
For some reason though, the Application had some performance-issues recently. I will have to investigate this further…

I have started on implementing a Settings-Screen. Right now, it only offers you to reset Mover but it should also be possible to change the Transport Types using it (i.e. disabling High Speed Rail or Coaches from Routing Results)

I added a :like command! You can now like checkins using :like <index>, where you can find the index beside the username in the checkin header!

You can now Bookmark your Journeys for Quick Access!
Thanks to Jetpack Compose (I really, really love it) it was pretty easy and even works offline! I am still thinking on how I can improve this because you do not actually see the Destination of your Journey in the HomeView yet..,

I added a View to actually see the suggested Route. I stole most of the Code from the “Entire Journey”-View and added Cards, that show a Walk.
This means, that Mover is now starting to actually get usable. You can figure out how to get from somewhere to somewhere. The biggest Problem right now is that you always have to type in the destination as that is not cached and the selected Route isn’t either…

Initial Routing support!

There was a lot I had to implement for this. After thinking about how you can actually enter the two Stations, I decided to just put a Search-Button on the Departure List and reuse most of the existing UI. It also was not easy to adapt the Data-Models because Transitous also returns Walking-Instructions as Trips.
Let me repeat that: AS TRIPS. In which world should a Walk between two nearby stations be in the same array as the normal Trips?!

Anyways, this is far from completion as you can’t actually see how you are supposed to travel.

I added Pause, Previous and Next Buttons directly in the UI as this was previously only possible using the Media-Keys.

I added the ability to remove Songs and to add Songs to the Queue. I do not really like the design of the “Autocomplete” List but it at least works. However, it is not yet possible to play an entire Album, Artist or Playlist.

I added a Login Window and made the queue more readable. This now also means, that I can open-source this project because the password is no longer hard coded.

I used Bootstrap 4 to start working on a basic UI. I am not very good at letting CSS look nice so this is what I have done. I also had some issues with Zed not counting my time and I actually worked longer but I have to revert back to VSCodium for now.

I am building Navabox. It is supposed to be a Subsonic Client made for the Jukebox. The Subsonic Jukebox Mode allows you to play music on the server and control it from other clients. Most clients I tested had buggy implementations of it, if they had that feature at all. My first goal has already been achieved: Make the current song visible and controllable through your OS-Interface. Unfortunately, both Chromium and Firefox require you to have a dummy media playing which is very cursed.

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 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.

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…

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.

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.

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.

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…