I think it's more of an issue where developers know they can't ignore the customer experience anymore.
You stressed the difference between developers and users earlier, but I think you're overestimating this gap. These days developers know that if the platform is great for them but sucks for users... it's not actually great for them unless they are building apps for a dedicated client. That's very rarely what mobile development looks like: If the user base just isn't there or you're going to end up with a lot of customer support headaches because the very platform engenders confusion, then it's _NOT_ actually all that great a platform for you the developer after all. I'm also worried about API quality. The Android API is quite good. There are a few points where personally I can come up with a few improvements (hard to apply now, backwards compatibility being what it is), but on the whole it's an extremely positive surprise for such a gigantic undertaking. This is by no means a common occurrence. With that many APIs to build, in such a short time period, by guys who don't have a name for keeping things simple, well, let's be nice and say I'm skeptical and leave it at that. Speaking of, is the API online someplace? On Friday, March 25, 2011 9:47:46 PM UTC+1, Chris Koerner wrote: > > I'm surprised that the fact that the Playbook will support Java doesn't > garner it any preferences when it comes to the *Java*Posse group. > > Maybe Android really has taken over. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
