Dude, thanks for your input! Very appreciated. Regarding your point about App support: This would not be an issue if the manufacturer chose Android (or a modification of it) instead of making their own. I am no expert by any means, so I don't know about the cost or problems of doing that. Maybe someone knows more?
Thanks for taking my remarks in the spirit they were intended (i.e. just a healthy debate amongst friends, rather than a personal 'attack') . That shows that you are more mature than some people around Head-Fi
I'm not an Android expert, either, but, as I see it, one of the biggest problems with Tidal implementation on audiophile DAPs is that it means you need to add RF hardware to a DAP which otherwise wouldn't need it. That means enormous effort must be made, to protect the circuit from RF interference (and even some of the best companies, designers, and devices may never achieve 100% RF immunity, as it's such a problem). Then you've got to include more code in the firmware, and pray that it doesn't make the operation of the hardware and firmware unstable (there is a Chinese DAP which I will not name, that is currently struggling with firmware stability with wireless functions, even though a lot of people really like its sound quality at its pricepoint).
RF hardware also takes up precious space (so does the RF shielding), and it consumes more power, meaning the battery has to be larger, and so the end result is a device that is bigger and heavier than competitors' DAPs that don't have RF hardware.
Additionally, some manufacturers have gone to the trouble of implementing Tidal, only to discover that Tidal fans are now demanding
more - they're demanding
offline Tidal functionality, and Tidal are seemingly very wary of allowing less-mainstream brands to implement this.
More hoops to jump through,
more delays,
more hassle, for DAP-makers who need to get their devices onto the market A-S-A-P, before competing DAPs 'steal' sales from them.
There's also the aspect that some DAP-makers may choose to use the Android platform (which is already developed to function well with touchscreens), but may not want to include parts of Android like Google Play. Instead, they want to use a stripped-back, barebones version of Android, to maximise battery life, minimise the number of running processes (which may also benefit sound quality), etc. etc. etc. I will concede that some have tried a dual-boot approach, to get the best of both worlds.
Hey-ho... I'm gonna shut-up now, as this is a bit off-topic for a flagship IEM thread!