Earlier quoted context omitted.
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.
Android Needs A Simulator, Not An Emulator
21–30 of 46 posts
Re: Android Needs A Simulator, Not An Emulator
#22I 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: woul…
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.
Re: Android Needs A Simulator, Not An Emulator
#23I 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: woul…
[0] : http://www.keynote.com/solutions/testing/mobile-testing
Re: Android Needs A Simulator, Not An Emulator
#24Re: Android Needs A Simulator, Not An Emulator
#25Earlier quoted context omitted.
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.
Re: Android Needs A Simulator, Not An Emulator
#26I 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: woul…
Re: Android Needs A Simulator, Not An Emulator
#27Have you guys heard of GennyMotion? It's way faster than the actual Android Emulator. My Professor for my Android Class in college recommended it to use for debugging for our assignments if we didn't have an Android Device. http://www.genymotion.com/
Wow, that page has a 2.5mb png as a background image on one of the elements.
Re: Android Needs A Simulator, Not An Emulator
#28The only thing I'd like is maybe a gradle build for ADT. I like my workflow I just hate placing required android libs on the path by hand, so time consuming. I only test on devices so the emulator thing to me is really a non issue. That said, I would love a "simulator" since it would probably mean that Google has wrapped the JDK with an Android interface which frees me from having to every use Swing/SWT/ any other ja…
Are you doing your integration and instrumentation tests on actual devices as well?
Re: Android Needs A Simulator, Not An Emulator
#29Re: Android Needs A Simulator, Not An Emulator
#30I 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: woul…