@leehu that’s pretty plain as what I’ve wrote.
Apple got decent latency on iPhone 2G so they’re about 10!!! years with tested working audio api and also AU is an active format (where is JUCE DirectX plug-in support ).
Apple got BLE MIDI on September 2014 and with iOS 9.x and macOS 10.11 they’re working pretty well.
Google got BLE on 2015 with Marshmallow. (there’s great implementation prior to that @ https://github.com/kshoji/BLE-MIDI-for-Android) however I’ve switched to SDK MIDI as it’s more reliable.
Summary,
For audio… Apple is by far on head start than Google.
I believe Android WILL become a platform supporting Audio but:
- Fragmentation makes proper audio sdk limited so only devices from ~2015 should be targeted if Latency is a major factor of the app.
- Notice that there’s a FEATURE_AUDIO_LOW_LATENCY (where for iOS this isn’t an optional feature)
https://developer.android.com/ndk/guides/audio/audio-latency.html
(make your actual market shrink…) - Even today there’s still no proven audio api. it seems only Android O would finally provide us reasonable API as @Doug linked to the aaudio. check for yourself how much Android devices uses Android 7.0…
- My daily driver, Nexus 5X, still haven’t proven me it’s awesome with latency
so…
Fragmentation Fragmentation Fragmentation… So to get people with decent latency it’ll take ~ 3years (if most people would upgrade their device by then since companies are sometimes slowww to upgrade older products and most users aren’t going the custom ROM way