ADP1 is explicitly supposed to serve both purposes. Not having official system images available affects both groups (SDK users who can't test their code against newer versions of the platform, platform contributors who can't revert their devices to a known state).
The boundary between the two groups can be blurry anyway, since application developers who'd like to move beyond the SDK and try their code against unreleased work-in-progress versions of the platform also end up flashing unofficial images, and since it's likely that some people belong in fact in both groups (developing apps with the SDK and contributing to the platform) and use their ADP1 for both purposes. JBQ On Fri, Feb 27, 2009 at 7:43 AM, Mark Murphy <mmur...@commonsware.com> wrote: > > vendor.net wrote: >> People buy ADP1 to develop apps for G1. > > Not necessarily. In fact, one can argue that is of secondary importance. > > As I understand it, the primary intent of ADP1 was to provide a hardware > platform for firmware development. > > One can certainly debate whether the priority of the intended uses for > ADP1 should have been more loudly proclaimed at the time of its release. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 2.0 Available! > > > > -- Jean-Baptiste M. "JBQ" Queru Android Engineer, Google. Please don't contact me directly. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
