Don't ask questions we can answer ourselves. I am so tired of the "does it have wifi?" questions people ask when they could look at a spec sheet.
Multi-touch is dumb. It's supported in the platform. Why it's not supported on the default on-screen keyboard seems silly and might be a good question. Pinch zoom may or may not be covered by a patent. But we don't have to waste his interview time with that, people can search the USPTO on their own if they want to know. If there *IS* a patent issue HE WILL LOSE HIS JOB IF HE says so. On all the android groups they very blatantly say they will not discuss these issues because it leaves legal breadcrumbs which can come back to haunt them. So just leave it alone!
Here are some REAL questions you can ask:
- Why is Android still developed behind closed doors?
- Why is there no roadmap of future Android releases? When Andy Rubin casually leaks out that they are working on Apps-on-SD to answer a question, it must not be a huge secret. So why not just post a roadmap instead of requiring a million journalists asking "Is Y in the next X release?" until we have some kind of idea of what is going on.
- Without the above two there is really no participation from the community at the platform level in Android. Is he aware of that and does he think it is an issue or not. Is Android an open source project or OHA's baby that just donates source code to the community. How does this jive with google's latest blog post on "The Meaning of Open"?
- Is he aware that the public perception of Android's model of OEM-created carrier-distributed updates is failing miserably at delivering updates. Do they have any plans to help improve this situation?
- Why run into so many problems with 256 MB of ROM and only upgrade to 512 MB of ROM. Aren't they going to be running out of space for /system on 512 soon too?
the Nook Color proved it was an undercover tablet all along, Barnes and Noble has hit back with this latest Nook as proof of its focus on one thing: reading.
The most commented posts on Engadget over the past 24 hours.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
Don't ask questions we can answer ourselves. I am so tired of the "does it have wifi?" questions people ask when they could look at a spec sheet.
Multi-touch is dumb. It's supported in the platform. Why it's not supported on the default on-screen keyboard seems silly and might be a good question. Pinch zoom may or may not be covered by a patent. But we don't have to waste his interview time with that, people can search the USPTO on their own if they want to know. If there *IS* a patent issue HE WILL LOSE HIS JOB IF HE says so. On all the android groups they very blatantly say they will not discuss these issues because it leaves legal breadcrumbs which can come back to haunt them. So just leave it alone!
Here are some REAL questions you can ask:
- Why is Android still developed behind closed doors?
- Why is there no roadmap of future Android releases? When Andy Rubin casually leaks out that they are working on Apps-on-SD to answer a question, it must not be a huge secret. So why not just post a roadmap instead of requiring a million journalists asking "Is Y in the next X release?" until we have some kind of idea of what is going on.
- Without the above two there is really no participation from the community at the platform level in Android. Is he aware of that and does he think it is an issue or not. Is Android an open source project or OHA's baby that just donates source code to the community. How does this jive with google's latest blog post on "The Meaning of Open"?
- Is he aware that the public perception of Android's model of OEM-created carrier-distributed updates is failing miserably at delivering updates. Do they have any plans to help improve this situation?
- Why run into so many problems with 256 MB of ROM and only upgrade to 512 MB of ROM. Aren't they going to be running out of space for /system on 512 soon too?