Originally Posted by jbutewicz
I really hope Google starts stepping up and helping developers out. Xcode for iOS is really nice to work with when devloping for iOS. It would be nice if Google put that same effort into helping devs build for Android.
Why would they change to being more dev friendly ?
Why would they spend more money on "expenses" when Android is #1 in terms of penetration ?
I'd be happy to see it, but I don't see them changing, and I highly suspect their team of bean counter accountants continue to conclude their profits are best when their development teams are small.
I've been researching/learning everything I can about audio on Android. It's a big mess, though it works, more or less, as in "good enough". But high performance, low latency audio such as IOS has is extremely difficult, hardware/OEM HAL/kernel driver dependent, and effectively impossible to do without at least occasional glitches on many leading devices.
These audio issues have existed for years, along with MANY others. The Android issue tracker is full of such issues. Some improvements have been made, but it's never enough.
Low level stuff like audio is where Android really falls down. The Google perspective seems to be the user perspective, which is closer to higher level Java stuff and farther away from the nuts and bolts of kernels, HALs, C and assembly language. Most of this is left to the OEMs to figure out and many take major shortcuts to reduce time to market.