Jarrod, I went from the iPhone to the myTouch this summer because I got tired of hacking and wanted to experience 3G outside of my house (I had a 1st gen iPhone).
It's not your imagination, it is slower when compared to the iPhone just doing basic things. The browser blows (and still blows). The scrolling issues you described are the first thing I noticed -- it was very frustrating, but I got use to it. But remember, Apple controls all aspects of the iPhone (hardware and software) so that's why things run so smooth and are so refined I think. That said, I think Android will get much better. The phones are constantly improving -- I don't think the G1 can even handle the same OS your Droid runs on -- and the shear number of people developing for Android is huge and growing and unfettered by the restrictions Apple imposes on their developers (and it's free to get into this unlike developing for the iPhone). Right now the Android Marketplace is where the iPhone App Store was a little over a year ago -- lots of trivial, redundant, applications because people are still learning. But that changed on the App Store and will change on the Marketplace. Honestly I think this will be a repeat of the PC vs. Mac wars of the '80s which the PC won and, I think, Android will win. My 2 cents. Ken On Dec 1, 11:26 am, Jarrod Overson <[email protected]> wrote: > I had been waiting to make the switch from the iphone to android until > both some nice hardware was released and it had been out for a while > for the initial usability issues to be resolved. TheDroidis what > made me take the plunge but I am *constantly* frustrated by what seems > to be surprisingly sub-par performance for the most basic UI > interaction. > > I started looking into the SDK and worked on a few apps in order to > resolve some issues i was having, but even the most basic example apps > in the sdk aren't nearly as fast as I would expect them to be on a > new, relatively high-end device. > > For example, something as simple as the sample 'home' app that comes > with the sdk can't even open the 'all programs' list smoothly. This > may seem trivial, but it is very telling if a basic application > written by programmers experienced in the SDK performs poorly on a > virgin device. > > There are a slew of problems that bother me and i am reaching out for > any expert insight as to whether or not they areDroidspecific, or > general to android 2.0 that may be addressed with future updates. My > primary frustrations: > > Delay between swiping gestures/clicks and visual response. > Scrolling is choppy in almost all cases, from lists, to home, to browser > pages. > Scrolls are frequently registered as clicks. > Occasionally clicks register as powerful downward scrolls, so a click > on a large list will throw me near the bottom of the list as if theDroidis > consciously mocking me. > > I could go on for pages, but as I write them all down I think the bulk > of my issues stem from the general feeling of sluggishness on theDroid. > Usability can be enhanced by other applications and by > workarounds, but poor performance at an OS or device level doesn't > seem easily fixable. > > I can't imagine it is inherent to theDroidbecause the specs seem > perfectly decent for a hand held device. Could it be the screen > resolution be requiring more processing power than theDroidcan > provide? Does the road forward look promising? > > "Works fine for me" is not a useful response, so please use restraint > when hovering over the 'Send' button. This is not device-specific, the > same problems occur on the 5 other droids i've compared against in my > company. Some people are OK with it, which is fine by me, but arguing > that opinion is not helpful. > > -- > Jarrod -- 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] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
