Hacker News Reader

Comment by IgorPartola | Hacker News Reader

I wonder if an Android device as a service would work. No, I don't mean loaning devices. I mean by the hour remote control of an Android device you can take over. Your end looks like the simulator, my end is a farm of Android devices which get a factory reset between every client connecting. You reserve it for as long as you want, or just do one-off testing.

Edit: I suppose I should ask a more concrete question: would you pay for a service like this? If not, what would you use instead?

View on HN

"I wonder if an Android device as a service would work"

Doubtful it would work any better than the custom VM solution that Genymotion (mentioned in the article) does (for this specific pain-point).

I would still need to adb deploy my apk to the device (which is a process that really drags development even when doing it to local devices) and now its even worse because it is remote. Also this remoteness would add all sorts of new issues like that fact that if I'm developing a server in tandem with the client app, now I have to jump through hoops to make the server remotely accessible (so your service devices can see it) whereas otherwise I might just be running it locally in a non-publicly accessible way for development purposes (solvable problem, but still a lot of friction and this request for a simulator is all about removing such friction).

Android devices as a service is still a good idea for other things like testing & QA because while Android fragmentation isn't as bad as it used to be, you still do see device-specific bugs (or at least platform-specific, like TouchWiz bugs on Samsung devices that don't impact other versions of Android) quite often when developing and having access to specific devices would help in such situations, but I don't think it addresses any of the main problems that are driving this request for iOS-style simulation (which, FWIW, I totally agree with Jake Wharton on).

Genymotion has one problem for me, which is that things that rely on the device having an ARM processor cannot be tested, so I do like the idea and the suggestions for existing services by other people in this thread. Shall check some of them out.

The Samsung Remote Test Lab[1] provides this for free (with limits)— they have a range of real devices (S5—S2, Notes, Tabs, even Gears) that you remote into and can install APKs, screenshot, and otherwise have full control over.

Somewhat unfortunately, I've found the connection fairly unstable, and they don't factory reset between uses (so unless you remove your APK, it'll stay on the device and configurations persist).

[1]: http://developer.samsung.com/remotetestlab/rtlDeviceList.act...

There have been several attempts at device testing as a service. I don't know of any that have really thrived. To be interesting, some have tried offering testing in diverse locations. In theory, they could also move their testing rigs, heat and cool them, pressurize the room, and/or rotate them in order to test sensors.

There are some kinds of sensors with variable quality that some developers claim leads to a need for testing every device. I would write code that characterizes performance instead, and possibly blacklist some known bad devices.

This exists: http://www.keynote.com/solutions/testing/mobile-testing

I've used it fairly extensively, it can be a bit buggy and slow, but it was instrumental in tracking down a bug just after launching an Android app.

People were leaving 1-star reviews, saying the app simply hard crashed at launch. We couldn't replicate the issue in any way on any of our ~10 physical devices we used for testing, or in any VM, but, with the service, we were able to isolate it exclusively to a handful of Android 2.3.3 devices with less than 512mb of memory. After that it was much easier to track down the source of the bug, fix it, and stem the flow of bad reviews.

Android is so fragmented among versions and devices that in the future I'd always want to use a service like this to at the very least make sure the app opens and runs across a slew of devices before launching.

There are a few of these out there including http://developer.samsung.com/remotetestlab/rtlDeviceList.act...

I like this idea as well, it seems fruitful enough that at least one organisation is providing it [0]. I would have thought overheads of getting new devices might cut into revenue though. I'd be interested to see what the difference in experience is for something on an emulated device (with HAXM) and a remote real device though, and if it's substantial enough to be worth paying for.

[0] : http://www.keynote.com/solutions/testing/mobile-testing

How would you avoid/handle abuses like using it as a proxy to access extremely illegal things?

How does AWS do that with their remote desktop in the cloud service? If you use this service, I have your name and credit card number.

You have a name and credit card number which may or may not belong to the person using the service.

Nothing is 100% in this world, its a good enough filter.

You can do this with almost any service now where you can execute arbitrary code, and a lot easier than running it through an android board.

You might like Manymo -- our company -- it's Android emulators as a service. Every recent OS and screen size combo; launches in a couple of second. Accessible from a browser, or in ADB.

https://www.manymo.com/

Reply on news.ycombinator.com