my-photo-timeline VS scalaonandroid

I had a similar issue with photos/videos and ended up building a cli app to organize everything, it has worked for my use case relatively well, still, there are uncovered corner cases. For example, this compares hashes only instead of the same photo in a different dimension: https://github.com/wiringbits/my-photo-timeline

I understand that https://photostructure.com/ has a far more sophisticated dedup algorithm, which can be worth a try.

Here's the 1.0.0 version of FxCalculator

Im my free time I experiment with the GraalVM approach, which is quite different (JavaFX or ScalaFX for GUI, no Android SDK). You can take a look here: https://github.com/makingthematrix/scalaonandroid

https://github.com/makingthematrix/scalaonandroid - that's my weekend project

I'm experimenting with this idea: https://github.com/makingthematrix/scalaonandroid

You can build a mobile app with GraalVM Native Image and JavaFX, but without Gluon - I have one such example: https://github.com/makingthematrix/scalaonandroid/tree/main/HelloFXML

In my case, I put them as separate files in the resources/ folder, like here with main.fxml and history.fxml. And then I load them separately in the code:

https://github.com/makingthematrix/scalaonandroid - Here's a repo where I'm doing some experiments with this approach, putting Scala on top of it (it's GraalVM so I can write in Scala if I want to, ha).

This can feel a bit hacky, but... here's my tutorial how to use GraalVM and Gluon to write an Android app in Scala. You can follow it step by step, just ignore the Scala part. https://github.com/makingthematrix/scalaonandroid

Here's how to make an Android native image with Graal, but a desktop one is not much different: https://github.com/makingthematrix/scalaonandroid