←back to thread

Android

(www.avc.com)
168 points okeumeni | 5 comments | 16 Oct 10 16:38 UTC | HN request time: 0.805s | source
Show context
Caligula ◴[16 Oct 10 18:06 UTC] No.1798435[source]▶
I have been debating fiddling wither win7 or android.

What is a good android phone to test/develop with? Is the nexus still the best choice?

replies(4): >>1798512 #>>1798639 #>>1798853 #>>1799097 #
mahmud ◴[16 Oct 10 19:20 UTC] No.1798639[source]▶
You can start hacking Android without a phone. The emulator is just cool :-)
replies(1): >>1798695 #
jawngee ◴[16 Oct 10 19:43 UTC] No.1798695[source]▶
The emulator is a dog. Compared to the iPhone anyways.

It's useless for web development.

replies(1): >>1798785 #
mahmud ◴[16 Oct 10 20:24 UTC] No.1798785[source]▶
How many platforms does the iPhone emulator run on? Is it instrumentable and controllable by user applications using nothing but sockets and octets? Didn't think so :-)

Android emulator is slow to start, but it's cross-platform, and allows for hot-updating.

replies(1): >>1799063 #
billjings ◴[16 Oct 10 22:46 UTC] No.1799063[source]▶
I have just about completely ditched the android emulator because it is irritatingly slow and I'm constantly finding it with its pants down trying to talk to eclipse. At our company we've also found that it doesn't give an accurate idea of how readable the text is in your interface, or how easy it is to interact with, partly because it's just too big on the screen and partly because it's sluggish.

It is at its most useful when I want to pull a file from internal storage, which often isn't possible on a device, or when I don't have a device handy, in which case it is a passable solution. It's never, ever my first choice, though.

replies(2): >>1799101 #>>1808817 #
1. biafra ◴[16 Oct 10 23:09 UTC] No.1799101[source]▶
I use the emulator for continuous integration. Its really helpful for unit- and integration-testing. Combine it with Robotium and you can thoroughly test you application across screen sizes and Android OS Versions.
replies(2): >>1800392 #>>1800495 #
2. stakent ◴[17 Oct 10 14:27 UTC] No.1800392[source]▶
Thank you for pointing out Robotium.

Can you elaborate more about your test setup?

TIA

replies(1): >>1803019 #
3. billjings ◴[17 Oct 10 15:13 UTC] No.1800495[source]▶
I'd like to second a thank you for pointing out Robotium, since I was trashing the emulator in the first place. I will definitely be checking that out for my next project.
4. biafra ◴[18 Oct 10 11:31 UTC] No.1803019[source]▶
I use the maven-android-plugin to build the dependencies in seperate modules. I have a patched version of bouncycastles crypto implementation (to have openpgp in android). Then there is the network code which also contains no android dependencies so it can be tested without the emulator.

Another module is the App itself. The last module is the TestApp. This is the recommended Test Setup: http://developer.android.com/guide/developing/testing/testin...

The testapp and the app are copied to the emulator or a real device. Then the instrumentation is started. The maven build fails if any error or failure occurs while building, installing or testing.

The continuous integration is done by hudson. The emulator can be started "headless" (-no-window) so it doesn't need to connect to the running XWindow-Server. Currently I am starting the emulator from maven with a special profile that is only used in hudson. When testing locally I usually have my phone already connected. It seems to be possible to have hudson start the emulator. With that setup logcat-output would be captured by hudson. Thats were I want to go.

Also missing in my setup is an multi environment build with all screen resolutions, locales and OS-Versions.

replies(1): >>1803092 #
5. stakent ◴[18 Oct 10 12:02 UTC] No.1803092{3}[source]▶
Thank you again.

Btw. I've upvoted your response, but still see one point next to it. Strange.