Hey. Actually i have a little problem with (let's say) Google engineers (and maybe a few of them are here on this group and could tell us something). You have started to build something huge, an open-source OS for ALL phones. 1) Let's focus on this world "ALL". Imagine that you produce some hardware component and now you have to build a driver for this hardware. You (as a builder) know everything about components capabilities, so the driver should come and stand just like a glove on it. How can you think that this software (Android OS) could work so good on every piece of hardware (phones of different companies). For this reason Apple has a plus: they design the hardware and build a mini MAC OS for this phone, and i am sorry to say that it works great. I am a little afraid that (let's say) Samsung will create a special phone for this Android OS (btw: Samsung's phone OS sucks).
2) At Google (i think) you have the top engineers of the world (the cherry on the cake) but why it's so hard to create something good this time. Google gmail, calender, reader are GREAT (i don't imagine my live without them) but WHY, why it's so hard to build a great sdk. You should focus on documentation / on creating good tools for Android App / and the most important thing: good features / good GUI / and GREAT support with as many sdk updates as possible. Google: imagine that Android OS has our support, use us, give us something to work with, put your mind of full power and put your engineers to work. Hire us ":D" if you want help and passionate people. 3) Another thing. I hate to admit it but: a) Yesterday at S. Jobs keynote, someone talked about a huge problem: if you don't know iPhone does not have something we know that it's could on Android "service". I mean that, you can not run your application on background; at first i was happy about it, but at this conference i heard the real reason for this: background applications slows down the cpu and battery life, and this is the reason for lot's of online hours with iPhone. They kinda solve this problem with "something", but on Android services are online, they really work, but is this a good thing ? will the OS work great on (our future) phones. And please, don't say that in the future we will have better batteries or super cpu on phones, because we live in present, and we must focus on the present. b) Android's GUI it's not that great. Android will be on our parents / old people / young people phones, so it must be simple but great. Right now ... let's say that: you should but your designers to work. c) Maybe something is wrong with Androids chief / coordonator / whatever. Maybe you don't look at this project like you should. In my eyes, this is the future, this is something i would work 24 hours a day to make it right; you are at Google and you should give us something good or nothing at all. Two thumbs up for Apple: they don't say "we will create the most / the biggest ", they say: "HERE IT IS, AND IT WORKS GREAT". Mihai --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
