hillel

Or maybe just nuanced communication doesn't work with most people independent of scale.

@MBCook you are correct. I have no problem with being able to make a choice. I have a problem having to make that choice out of the box between two pieces of software shipped by the same company. It's like they couldn't be bothered to settle it so they just punted the decision to me.

I would have thought this experience to be anachronistic as well as I thought Android had plenty of time to polish their experience since those stories 2-3 years ago. That's part of the reason I jumped into trying Android. I thought it would be a good experience - just different from iOS, which I welcomed.

As for doing good UX for apps on Android, i think that's almost no different than doing good UX for apps on any smartphone platform. Aside from dealing with the back button and a few other platform specific issues, it's the same set of challenges around touch-based devices and limited screen real estate.

Voicemail shouldn't be a carrier specific experience. Is there something so differentiated about the t-mobile voicemail experience vs. the verizon voice mail experience? Shouldn't there just bean android voice mail experience that the carrier can direct at their back end as appropriate?

I don't think it's unreasonable to expect that a core feature (like voice mail) should work out of the box with no additional installations on my part.

My issue is not that I abhor choice. Choice is fine and sometimes good. My issue was that I was confronted with these choices out of the box. And the impetus for this was Google's business choices at the expense of a seamless user experience.