When there's a new iOS version and iPhone out my wife asks about it because all her nursey mates on the ward are talking about it. It's think how much that's worth.
I honestly haven't explored the Bluetooth stack too extensively, but I know the lack of a unified LE stack hurt a number of people I know developing products. And it will have ramifications for a long time due to the slow pace of OS updates on the platform.
It's the decisions that Google made when implementing the Camera and MediaRecorder classes that hurt me the most, and will continue to for a long time going forward. What's easy on iOS and BlackBerry 10 is exceedingly difficult on Android. It's a PITA, but also a good thing for me since it makes the barrier to entry by my competitors much higher that I can rest a bit easier. And I can take a page from Google's book and port it back to older OS versions to fix it on all devices so that other devs can use it. Such are the pros and cons of the platform.
That having been said, if you want more BT info, I can help :P
edit: forget those links, I should've known to just seek out the Android Police article - most details including AVCHR or whatever it is: http://www.androidpolice.com/2013/05/15/bluetooth-low-energy...
The way Google is currently updating their core apps is the right way to do it, and should have been done from the beginning. Honestly, it seems counter-intuitive that it isn't that way on iOS. I realize why, Apple does stuff that requires tight OS-level integration that they don't expose to others. But the fact that Google and BlackBerry do this means to me that Apple made an architectural choice that will ultimately slow their speed of deployment of key updates. BlackBerry and Google can update their maps apps whenever they want, and regularly do. Apple had to wait for an OS release.
With all that said, I am tremendously disappointed that we didn't see another Android point release. I understand why to an extent, but there are glaring omissions in the OS that make it exceedingly difficult to build an app that has significant features that interface with hardware and peripherals. The Camera API is lackluster, and the Bluetooth support (Or lack thereof ) is just shameful.
The only saving grace of Android is that you can fix these problems yourself, if you know what you're doing. But it isn't easy, and is beyond they capabilities of most devs.
Here's hoping Apple announces something awesome at WWDC. I still love Android for what it is, but they do need to catch up in a few key areas.