Pankaj, I'm in the same boat as you are: I'm an independent developer that doesn't have funding to buy 20 phones.
The emulator comes with a lot of options, so that could be used to some extent to simulate different devices. You can simulate slower devices with -cpu-delay, set the resolution with -dpi-device and - scale, etc.: http://developer.android.com/intl/fr/guide/developing/tools/emulator.html#startup-options But, it's impossible to test for everything. When I published my first app, I found out the hard way that for Hero phone users, the soft keyboard wouldn't pop out for them. I got some bad reviews and I had to publish a quick fix. Neverthelss (I'm pre-empting the Android haters), I'd much rather an app work on 80% of 20 different Android devices than 100% of a handful of Apple devices. No open platform is perfect, but Android rocks in my book. On Nov 10, 11:07 pm, Pankaj Godbole <[email protected]> wrote: > I agree that quality is priceless. I know this first-hand from > spending several years in testing and quality assurance. > > It might be possible for an institution to purchase 20 different phone > models to test on. But how is an independent individual developer like > me supposed to purchase so many phones, when perhaps all of them would > be locked to a carrier and most would come with a 2yr service > agreement? I am also not based in the US. > > Is there a more feasible way without compromising on quality? > > Eric's spreadsheet is awesome! Here's another one I found pertaining > to US > carriers:http://spreadsheets.google.com/pub?key=tIuLv6KThktwpCyNu5lbrWQ&gid=0 > > - Pankaj. > > On Nov 11, 9:13 am, PJ <[email protected]> wrote: > > > > > I can't agree more with Eric. Why get 20 phones that are all > > identical? Get some variety so that you write apps that work as > > expected for multiple devices. You can't put a price tag on quality. > > It's not worth saving $50 per phone if you end up writing an app that > > breaks on a particular device and you get a bunch of upset customers > > and bad ratings/image. > > > You definitely want to vary things like: > > * hard keyboard vs soft keyboard > > * high-res screens vs low-res screens > > * fast vs slow cpus > > > And Eric's link to that spreadsheet is freaking great. > > > -- PJ > > > On Nov 10, 5:42 pm, "Eric Wong (hdmp4.com)" <[email protected]> > > wrote: > > > > I would say get at least one unit for each Android models out there? > > > Since every unit seems to have slight variation of Android > > > implementation and apk tested on one may not work on the other. > > > > Hope this spreadsheet would > > > helphttp://spreadsheets.google.com/pub?key=rdm8c2ZfSDKd5l-dVy4SrnA&output... > > > > Cheers > > > Eric > > > > On Nov 10, 12:31 pm, Ash <[email protected]> wrote: > > > > > I'm new to android development. We need to buy around 20 phones for > > > > android development for our university. Please share your views and > > > > comments on the phone you think is good for Android development. > > > > > Thank You -- 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
