Hi! I have a somewhat related question.
A lot of android powered phones will become available in the next months. And as I see manufacturers trying hard to customize their android versions, to make their products more appealing to the consumers. So how can Google (and the Android team) defend the platform from becoming fragmented ? I mean I'm pretty sure that no manufacturer can modify the base framework in a way which makes existing apps incompatible with it and still call it Android powered (am I right?). But what if they extend the framework with apis that I as a developer can use, and if I choose to use it, will I be out in the cold alone to sell it somehow outside the Market ? Or should I just use the base framework as it is and hope that my app will integrate well with the changes the manufacturer made ? Thanks for the answers. Zod. On Jul 3, 12:56 am, Dianne Hackborn <hack...@android.com> wrote: > On Thu, Jul 2, 2009 at 9:45 AM, Rangan <mjvran...@gmail.com> wrote: > > 1) Is it legal to install Greader as an application on the devices > > when it is shipped to customer? if yes, what is the best way to do it? > > Can we simply use the apk file of Greader and install it on device? > > Any other better ways? > > You had sure better talk with the application author and sign a contract > with them to have their app included. You can't just take it and put it on > your device. > > > 2) When the applications are built, it will also have lot of > > dependency on the hardware availability on device. If there is an > > application developed for T G1 Mobile using the GPS hardware then this > > application cannot work on another device which does not have GPS > > hardware. > > Currently to be an Android compatible phone, you are going to need to have a > GPS and the various other things that applications depend on. > > Since we have market place for Android today and mostly > > > targetting for T G1 mobile, how do we ensure that users must not able > > to install it on devices that does not support all the required > > hardware for device? There are few ways to deal with it. > > a) Have market place specific to each device > > No way. > > > b) The application developers has to clearly document what is > > the expected harwdare for the applications to work so that the users > > are aware of whether would work on the device or not. This is mostly > > manual then. > > And is already being done, for example an application can say that it > requires a physical keyboard. > > > c) Ideally we should ensure that the application installation > > must happen only if before installation, the compatibility check > > passes. This is possible only if we bring in a framework design for > > this structurally. > > Market already takes care of this, and won't display applications that > aren't compatibility with the target phone. Ideally, though, the platform > should take care of most of these things -- the introduction of soft > keyboards being a representative example, where the platform goes to a fair > amount of work to ensure that applications that were written for a hard > keyboard still work with the input method. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
