I've said this before a couple of times. It seems like their dev teams are all one group, so that the interface guys are the same programmers that do the auto-pilot software. From a proper dev standpoint, they really need to split these guys/gals into two groups. Either have a strictly auto-pilot group or do a driving dynamics group and then an infotainment group. But here is the truly evil plan that would allow: You restrict all the driving dynamic stuff in the SDK before you release it so that 3rd party developers can only touch all the stuff that wouldn't necessarily kill you if it went wrong. Then you shrink your infotainment group down to just a bug check/software verification team (maybe leave the weird guy with the crazy ideas and machine-like programming skills). You let all the 3rd party guys make the software, add the bells and whistles people want, track change-logs and progress, and you sit back with your coffee and make sure there aren't any glaring memory leaks or performance issues. Basically I've just described a app store. All that being said, I only have some inkling of the pressure/deadlines that the dev team is under. Despite a slow/weird release of features (who wants car naming before playlist support???), I think they've done a fantastic job checking off some big ticket items from the list or at least start to chip away at some of them. I'm looking at you TripPlanner and backup camera lines. I truly wish that as owners, you could email that department directly for kudos. I understand opening them up to the public for bug fixes and feature requests would be a terrible idea unless you only did it for a few owners who were beta-testers and had software dev experience.