Anki-Android

One of the things they don't mention is that J2K makes you pick between: * A conversion in 1 commit: complicating/breaking the 'follow' behaviour of 'git blame' * A conversion in 2 commits: the first 'rename' commit doesn't compile, complicating/breaking 'git bisect' I hacked up a script which makes the 'rename' commit compile (when I was working with a ~100KLOC Kotlin conversion). This may be useful for others: * https://github.com/ankidroid/Anki-Android/blob/937a6560913ec... * https://github.com/ankidroid/Anki-Android/blob/937a6560913ec...

The standard Android ability to get WebView history is only the history for the instance of the WebView which you created (totally reasonable IMO, there's lots of non-nefarious purposes that you'd want to intercept requests[0]). To my limited understanding, the file on Xiaomi phones is a dump of all the packets that your router would see. If you're using HTTPS, it's probably leaking the sites, but it's mostly garbage. [0] https://github.com/ankidroid/Anki-Android/blob/31cfbc914a746...

Get in touch with the maintainers if it's causing a problem, they probably don't realise and it's typically very easy to perform a parallel release under a different applicationId. GPL'ed code, but so is FairEmail: https://github.com/ankidroid/Anki-Android/blob/7082f6ee93ed1... Most of the relevant code is in parallel-package-name.sh

If you have an Android device, AnkiDroid 2.16 (currently in alpha) has basic drawing functionality [0]. Image Occlusion is available via a third-party app[1]: The app is open to pull requests (raise an issue/pop into chat), and provides an API which allows external apps to create cards. [0] https://github.com/ankidroid/Anki-Android/releases [1] https://f-droid.org/en/packages/io.infinyte7.ankiimageocclus...

Wish this article had been written a year ago when when I added Anki import to my learning app (https://traverse.link/)! Especially importing media files and de-renaming them was a pain, as well as handling the different types of cloze deletes (some of this is described quite well in anki's docs, for example here https://docs.ankiweb.net/#/templates/generation) Another link on their DB structure which saved me a lot of time was this one: https://github.com/ankidroid/Anki-Android/wiki/Database-Stru...

Android's default linting already contains a "missing translation" lint rule which you can activate: "MissingTranslation"[0] For Android specifically: Gradle and Android Studio both support a powerful linting framework (to the level that it can provide auto-fixes to the IDE). It's better to provide an in-editor to guide your contributors before it hits CI, then have CI nag if they didn't fix the in-editor warnings/errors: Some examples of custom lint rules[1] and the default rules which Android Studio runs[2]: [0] https://android.googlesource.com/platform/tools/base/+/32923... [1] https://github.com/ankidroid/Anki-Android/tree/master/lint-r... [2] https://github.com/ankidroid/Anki-Android/blob/master/lint-r...