Please don't go off making assumptions and getting all disgruntled about them.
If nothing else, the new version of home does not yet support all apps in landscape (it wasn't needed for Nexus), so it is not generally usable yet. As far as "apps which interact with the Home screen (like widgets and wallpapers) can't be relied upon to behave the same in the emulator as on a real handset", I have no idea what you are talking about. Application interaction with the home screen is very limited, and most of the significant interactions (setting and showing wallpapers, widgets) are defined by the platform, not the home app. Is there some specific interaction issue you have had with the home screen that has varied across devices? Plus the new home screen is a fork of the standard one, and so doesn't have any different behavior that apps could be aware of. On Tue, Jan 12, 2010 at 1:11 AM, String <sterling.ud...@googlemail.com>wrote: > On Jan 12, 8:56 am, Kevin Duffey <andjar...@gmail.com> wrote: > > > Does that mean we wont see the new interface on Moto Droid when it's > > released with the 2.1 update? I thought it was all part of 2.1. > > It was mentioned in a different thread that the Home app is different > in the emulator than on hardware phones. Presumably the emulator has > the "stock" Android Home implementation? This difference wasn't > obvious in previous releases - e.g., the 2.0 emulator's Home was > visually indistinguishable from the Droid's - but it certainly is in > 2.1. IOW, the N1's Home screen is another custom UI, like Sense or > MotoBLUR. > > This is disappointing from two directions. First, it means that > devices which we took to be bone stock Android - like Droid, and now > the N1 - aren't really. They ALL have a custom Home UI, and apps which > interact with the Home screen (like widgets and wallpapers) can't be > relied upon to behave the same in the emulator as on a real handset. > > Second, it means that UI improvements (like the 3D effect in the N1's > Launcher) aren't part of the OS, and can't be used in other apps > without some serious hackery. This will unfortunately lead to a less > consistent user experience, and a perpetuation of the criticisms that > "Android apps aren't as pretty as iPhone's". Which doesn't bother me > per se, but it does seem to be important from a PR standpoint. > > String > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
