• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Apps Testing apk remote

You need to test on real devices only if you are using some hardware features or some native functions. This is a rear case and not a hobby project case.
Normally you can test your app on emulator and your device to check usability. It is usually enough. In manifest you specify features that your app is using. It is enough for Google Play to find out what devices will work well with your app.

So normally, you don't need to test on multiple devices and you will be fine.
 
Last edited:
You need to test on real devices only if you are using some hardware features or some native functions. This is a rear case and not a hobby project case.
Normally you can test your app on emulator and your device to check usability. It is usually enough. In manifest you specify features that your app is using. It is enough for Google Play to find out what devices will work well with your app.
prs.png

So normally, you don't need to test on multiple devices and you will be fine.
There are some cases where there we do not work directly on harware.
E.g. I have an app which should detect if the external SD is present, and what is the absolute path to access it. There is no standard way to do that. It heavily depends by Android version, and also by vendor (there are always surprises).

Other example: on devices with multiple SIMs , there is no standard way to find which contacts are on SIM1 and which on SIM2. Each vendor it's implementing it's own
RawContacts.ACCOUNT_TYPE in the database.
 
Back
Top Bottom