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.
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
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
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 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 3 years ago.
Improve this question
I'm an iOS coder and have been asked to write some cross platform code with Phonegap or Titanium. There's plenty of information out there about setting up development environments, etc... except I'm missing one crucial piece of information.
What mobile hardware should I buy? Now that's a pretty lousy stackoverflow question, so let's rephrase it to be useful.
What criteria needs to be examined in choosing an Android tablet for iOS/Android cross platform development with PhoneGap or Titanium?
The corollary question is also useful, what criteria needs to be examined in choosing iOS hardware for cross platform development with PhoneGap or Titanium?
A good general approach is to pick high volume devices with an eye toward diversifying hardware- so for example if samsung has a really high res phone, don't buy another really high res phone from LG or if all the available Android phones are high res, try to sprinkle one in that has a slide out keyboard. Don't worry about trying to test everything on every device, test things that should work the same across a small number of devices and then test the things that could be very different on a larger number of devices. Depending on your app there are probably a few things that you know could behave differently on different devices- focus on this. For example, we test the camera on all devices but we would only test something like an alert message on one device.
If you are looking to build for iOS and Android I would also recommend checking out Brightcove App Cloud - http://appcloud.brightcove.com. There are good testing/debugging tools and plugins are well-documented and fully supported.
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.
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 11 years ago.
Improve this question
I would like to use my netbook for Android development, but when I try to run the SDK with Eclipse, nothing loads. Are netbooks generally powerful enough for Android development? Why or why not?
It's hard to see where the line for a netbook is drawn, but i'm do develop on my "netbook", but it does have 3Gig mem, and a dual core proc, so the only netbookish about it, is that it's a small, 12" thing.
The small screen is a bit of a problem sometimes, as a bigger-screen emulator sometimes doesn't really fit.
I'd not readily use something with even less memory, as eclipse, a VM and ofcourse various things like browsers and all, are a bit heavy on the mem.
Concuding: yes, you can develop on a netbook if you stretch the definition a bit. I'd not choose a low-end netbook, choose one with enough mem and you should be aware that a small screen is a limitation.
Possible? Yes.
Fun? No.
Worthwhile? When making any degree of progress right now is preferable until waiting until you are in front of a better machine.
Well, perhaps not what's really meant, but here's a link to a web based app creator for Android.
But I whine enough about having to develop on my "measly" 4 gig mem laptop.
YMMV
I develop on my MSI Wind U100 (with an 1gb of ram) every now and again, and it's perfectly fine for it.
(10" screen 1024x600)
Although I use Eclipse, I don't use the emu.