david_allison
Joined 6 years ago
Joined 6 years ago
They should be after 2 years, I occasionally get emails, linking: https://support.google.com/accounts/answer/12418290
E-waste is awful, as is cutting off old devices. We still backport security fixes to minSdk 21.
To Google's credit, post-21 is a much more pleasant experience and requires very little developer time. API desugaring[0] has worked perfectly, their compatibility classes[1] handle most of the common cases, and there's often very little to actually code[2].
[0] https://developer.android.com/studio/write/java8-support-tab...
[1] https://developer.android.com/jetpack/androidx/releases/appc...
[2] https://github.com/ankidroid/Anki-Android/blob/main/compat/s...
This is regarding 2.25.0alpha4.
* We target minSdk 24
* We're still using XML views
* We target a large variety of form factors
* We have a lot of screens, and these have a lot of configuration options.
I really wish it was "point an agent at it, and walk away", but many screens ended up being hours of iteration with Fable driving my phone/an emulator to produce an acceptable outcome.
Given that my Pixel 9 Pro has system screens which are still broken under edge to edge, it's not an easy change, and takes up time which could have been going towards feature development.
The next update won't be huge, (Google required us to make all screens 'edge to edge'[0], which took up most of my time last month). I'm hoping for some solid improvements now that's out the way, once the release pipeline has returned to normal.
Feel free to get in touch if you fancy contributing.
[0] https://developer.android.com/develop/ui/views/layout/edge-t...
It's not clear given Google's policy wording and replies. We've removed the links, and can move forward once clarification has been provided.
Interesting! Do you have a source for this?
I predict that things will be 'good' within the next 5 years, but your intuition is correct (and the SOTA models are often producing worse prompts than older models).
Are you sure? I played in 2024 on PC and it was playable.
The wrapper around these is very lean, FFI-based[1], it's abstracted to a library so Android devs never need to know there's rust/codegen involved.
We then define a light Kotlin-based wrapper around the protobuf-generated API[2]. This is a candidate to move to Kotlin multiplatform in the near future (mostly for test speed improvements).
[0] https://github.com/ankitects/anki/tree/main/proto
[1] https://github.com/ankidroid/Anki-Android-Backend/blob/a0428...
[2] https://github.com/ankidroid/Anki-Android/blob/68192585a7ae4...
https://github.com/david-allison
gmail: davidallisongithub
Sponsors: https://github.com/sponsors/david-allison/
https://opencollective.com/ankidroid