Lack of Built-in Audio Player in AnkiDroid Poses Long-Term Risk (Opus, Future Codecs)

I would like to raise a concern about how audio is handled in AnkiDroid.

Currently, AnkiDroid relies entirely on the Android system to play audio files, instead of having its own built-in audio player. This creates a long-term risk for users who rely heavily on audio in their decks.

For example, I use the Opus format because it offers much better compression and quality compared to MP3, which helps me save a lot of storage space when dealing with thousands of audio files.

However, there are discussions about new audio formats like OAC (a potential successor to Opus). Even if this takes many years, it raises an important concern: what happens if Android eventually drops support for Opus?

If that happens, all AnkiDroid users who have large collections of Opus audio files may suddenly lose the ability to play their audio. Since AnkiDroid depends on the system player, there would be no fallback solution.

I understand that formats like MP3 have remained supported for decades, largely due to their universal adoption. Because of that, if MP3 support were ever at risk, it would likely receive much more attention and faster solutions.

Opus, on the other hand, is less widely used by the general public, especially within Anki decks. This could mean that potential compatibility issues might not receive the same level of urgency, leaving some users more vulnerable.

This becomes even more concerning when thinking about the future. What if someone wants to use, share, or even sell their decks 40–50 years from now? If the audio format is no longer supported by the system, those decks could become partially unusable.

Converting thousands of audio files later would also be extremely difficult and time-consuming.

Because of this, I would strongly suggest considering the implementation of an internal audio player in AnkiDroid, with built-in support for formats like Opus. This would ensure long-term compatibility and protect users’ data regardless of changes in Android.

Thank you.

Converting thousands of audio files later would also be extremely difficult and time-consuming.

It feels like the post is predicated on this line, and it’s not the case. Bulk media conversions are trivial.

This isn’t going to be on the roadmap. We’re time/effort constrained, and I’d rather focus on user-facing improvements, rather than spend significant dev effort protecting against the chance that a bad decision is made 20 years from now.

When it’s likely to be an issue, please re-post. I can’t see this being close to relevant for at least a decade, but time will tell.