For a few specific reasons at a sailboat race this week, I visited an ER to have a finger stitched up. As the Aussie Doc was shooting in the Novocain and scrubbing out the congealed blood, I asked, “How many stitches?”
He answered, “I count them when I’m done.” That statement kind of applies to the SDK date prediction requests… and it logically makes for a better outcome in that important goals don’t get confused with less important metrics. Other stuff that might be useful from this week is roles and role confusion, that might be causing some of the conflict that folks are struggling with. Here is my understanding of roles with the idea of clarification. Consider this a straw man and adjust as desired. The 50: Present an ordered set of applications. Customer’s need to understand how these can improve their lives so they can successfully relate to their friends what the phone does and why it is good. Google: Leverage their value add to obtain a low latency connection to the cloud from several carriers. Obtain ubiquitous location information including cell ID and tower triangulation for all applications. The 1725: Present the 50 in a positive light. Point out possible use models so Google can choose or not choose to accommodate them. Put food on the table by some other mechanism, until figuring out if Android will be more or less locked out than Apple. OHA: Managment leadership. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
