The old version of aedict, version 2, was open source. GPLv3. Aedict is an English/Japanese dictionary for Android. The author stopped working on that in 2012 and now sells a closed-source version on the Play Store. I do not use the closed-source version. The APK from the final open source release back in early 2012 works just fine with Android 5.1, which is nice, and I currently use it and like using it.

That APK has some URLs hard-coded for dictionary files, and one of these days those URLs will need to be changed. They point to an old server that, when the hardware fails, won't be replaced at the same URL. There's no immediate rush to fix this, because the hardware hasn't yet failed.

Also, it would be really nice to get the app into F-Droid. Then many more users could easily find and install it.

Also, it might be nice to bundle the dictionary files. I don't know. Although that would make the APK significantly larger, and would force a version change to get a dictionary change, it would make installation simpler. Assuming that making a new release is quick, it could be a good idea. The dictionary files change very slowly, so even if there were only an annual release, just to choose a lengthy period of time, that would be peachy.

I've never built any Android apps. It seems that this one was/is built using maven, which I've never used. Is this kind of stuff tricky? Is it worth spending any time? If I can change a few text files and XML files and type mvn somethingorother and get a new APK, that would be cool. If it's too time-consuming to learn, though, can't do it.