Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Lenovo a6000 is not able to run material design code .
First of all, a question like this will provoke opinionated, heavily biased answers and provoke flamewar like discussions between religiously fanatic fanboy groups. It is not very wise to ask a question like this.
Furthermore, one single phone is never enough to really get your app tested. It gets you the impression how your app works on one device, but how it will work on all the others, you will never know. You will always need a variety of devices, and I am not just writing about phones, phablets and tablets, but also of different vendors. Because each vendor introduces "his" own peculiarities and quirks and you will notice that while running fine on a Nexus, your app might crash on an HTC or Samsung. Or while running nicely on those, it might not on a Huawei.
Why?
Because.
Because the vendor did something the others did not, and no one expected it. But your customers will hold you responsible for it. Because your app is crashing. And you don't want this.
So bottom line: There is no best phone for testing. Get a number of different devices from different vendors and test on all of them. Yes, it is expensive and tedious work, but you asked for it...and your customers will be thankful for a stable app. :)
Google nexus series is the best. Just use nexus for tests
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Is having multiple phones of various screen sizes and model a must? Will it be more convenient, and would you recommend it to someone serious in developing for Android?
There is no single way of developing an Android app. These are nice reads for multiple screens support.
Multiple screen support
Supporting different screen sizes
For Android app development, you don't need to have multiple physical devices. Emulators would be enough. What I used to do is, testing it on multiple screen sizes and densities.
These are the emulators I use for testing. I think it's pretty much covering all the device screen sizes.
I have found that it is quite helpful to run on various different real devices. I only have a couple real devices myself though, so I have used AWS Device Farm a few times. It can be helpful to determine layout based issues that you may have on other phones, and it allows you to run a bunch of tests simultaneously. I don't have the time to test everything manually on all of the different device sizes.
https://aws.amazon.com/device-farm/
I think that it is helpful having a weak (out of memory errors, slower CPU, ...) and a powerful phone. It is also good to have a tablet because of the 4x3 display format.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am just wondering about Responsive Web Design and its necessity. Since new smartphones have resolutions similar to 1024x768 and the vast majority of web sites work well under this resolution, for what reason may we care about how mobile phones will show our design? Is the whole conversation about smaller resolutions or am I thinking the wrong way?
Thank you
It's not about resolution, it's about readability and usability on a small screen.
According to Andy Rubin there are about 600 different Android devices available in the market right now. Supporting all of them is impossible, right? At least that is what we see in tech blogs throughout the Internet. Funnily enough, fragmentation seems to be much bigger problem to people who don't work in Android development or have good understanding of the platform than to people who do.
That meaning, you could have more than 100 different resolutions for your app, maybe some are big like 7 inch, 4 inch, etc.
The responsive design, could be very good for the developer and designer, and if you need implement the portrait and landscape view.
Responsive design not is mandatory, but could be more easy for you in the moment to publish your app in tablets, phone devies, etc.
Android design cannot be approached the same way one would design for iOS. Android device categories are a continuum not tablet / phone steps. If we understand how to approach the problem of design from the beginning we endup building apps that suit most of the devices much better.
Don't build two separate versions! Build one scalable one!
You can read more here
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
New devices support at least Android 4.0 and many people started to change their phones. Do you still think that we should target Android version 2.x?
I ask this because it won't be that easy for me to support 2.x because of my native libraries. I also have to buy Android 2.2 froyo device for my tests. So, I am trying to find out if all of the effort is feasible or not.
Gingerbread 2.3.3 is on 1/3 of active android devices so I think it is something to care about.
I've has same issue too. Resolved restricting some functionality like above:
int sdkversion = 6; //or whatever
if (Build.VERSION.SDK_INT<sdkversion){
...DO NOTHING ABOUT THAT FUNCTIONALITY...
} else {
...DO IT...
}
This should help you out :) I always check it out before embarking on a new idea.
http://www.appbrain.com/stats/top-android-sdk-versions
As for your native libraries, there are plenty of apps out there that only support 4.x versions and still do very well. There are some really decent devices that run gingerbread (2.3 I believe) and are perfectly suitable to all recent apps, but due to manufacturers wont be receiving an update.
Of course, various folk root their phones and use custom roms, so maybe it's not that bad afterall. These stats, can't take that into account, obviously.
HTH.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I experienced something weird on my Android tablet. It had been turned off for several weeks and then when I turned it on, it rebooted. Previously, it was just in sleep (standby) mode. But after rebooting, I noticed that the entire device was reset to its factory defaults. All my apps were gone and everything wiped.
Then a few days later I rebooted the device and was surprised to see that all my apps were back again and everything restored as it was. I don't use any backup/restore software, so I am really curious to know how this could happen? Does Android support multiple user profiles? If multiple boot profiles is supported, can this be utilized by an app through some API?
Android does not currently support multiple (simultaneous) user profiles. If you do want to achieve this, there is an app that supports it (perhaps more than one), but it involves having a rooted device.
I have personally used this on my home tablet, and it works quite nicely, but requires a reboot to access the other profiles.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I had to accept a return on an Android app because the user told me it was not working on his Motorola Xoom. (The audio playback had some reverberation)
This is not a super high volume app, so I am not planning to go out and buy dozens of Androids to test it!
Also, it is an audio recorder app, so it does not work too well in an emulator.
How can I diagnose and correct the problem on the Xoom and in fact all other platforms, without investing a small fortune!
One thing you can do, if you're not averse to rooting, is installing different ROMs on your device. This will at least give you the chance to test on some different versions of Android and different UI skins (how many are available depends on your device).
I also read about services that test your app on different devices for you, but I'm not sure how much these cost.