3

before publishing a new app on the market, on which devices would you suggest to check whether it runs fine or not? What are your experiences? How do you handle this?

Are there some empirical values, for example, do applications that run smoothly on a HTC Desire behave similar on all HTC devices? Are there some devices on which the app should definately be checked?

I like to picture myself releasing a high quality product instead of throwing some crap on the market. :) But I suppose I am not the only one who cannot buy like 5 or more devices just to ensure that the apps works fine on every kind of device. Well, at least not yet... ;)

Thanks for your help!

Best regards S.

BalusC
  • 1,082,665
  • 372
  • 3,610
  • 3,555
Dennis Winter
  • 2,027
  • 4
  • 32
  • 45

4 Answers4

2

The most problems in my app are freezes on droid... no other device reports freezes... just droid.

If you have access to different devices, very good. If not, test at least all possible screen sizes and densities with the emulator. Thats my advice.

WarrenFaith
  • 57,492
  • 25
  • 134
  • 150
  • 1
    One problem I've had with testing on droid is I keep using the fold out keyboard and forget that 90% of androids don't have one. I've annoyed many of my users by forgetting that they can't see half the screen when they type. – CodeFusionMobile Aug 18 '10 at 21:21
  • hm... good tip! Also I almost forget that things that are familiar for me, can be very tricky for the normal unexperienced user – WarrenFaith Aug 19 '10 at 08:35
2

I recommend testing on touchscreen and 5-way navigation in addition to varied densities. Testing screen orientations might be good, too, but I haven't figured out how to do that with an AVD.

Melody Horn
  • 778
  • 2
  • 6
  • 22
  • Matt, check this link: http://developer.android.com/guide/developing/tools/emulator.html#controlling Ctrl+F11 changes the orientation... – Dennis Winter Aug 18 '10 at 18:27
2

I would recommend getting phones that represent various tiers of hardware. Check for performance on low end devices like the droid (can't believe I'm already saying that after less than a year) to make sure that your app is not too demanding and will run smoothly. Also check on a high end device like the EVO to make sure it looks presentable on a fancy device with high def screens.

Another nice device for testing is Nexus One. It's middle of the road, has nice screen, decent hardware, and runs Froyo, without being the latest and greatest.

CodeFusionMobile
  • 14,812
  • 25
  • 102
  • 140
0

I test with a droid, and although my app runs flawless I still get comments and 1 star ratings for crashes on other phones like X10, EVO, etc.

I too focus on quality and dont want to put a half tested app on the marketplace. I spent TONS of time on testing. In the end, it didnt work on some phones and there's really nothing I can do about it.

Nick
  • 1,340
  • 1
  • 15
  • 23
  • Well, maybe some kind of a regular get-together of Android nerds bringing their devices might help; sounds like a "debugging-party"... ;) – Dennis Winter Aug 18 '10 at 21:41