A tale of two developers – one who uses Testdroid and the other who uses the current method, testing one phone at a time – the time and money that each one consumers is decided in one tool they choose to test their apps.
The school of hard knocks – a path without Testdroid
- Week 1: You have a great app idea and you are absolutely positive you are first one to have this idea – you just have to get into the market first!
- Weeks 2-4: You are furiously implementing your app, every now and then making sure that works works on Android emulator and your own Android phone, maybe your best friends phone too. Everything is going according to your master plan and you are sure you’ll be the first one to crack this market!
- Week 5: You release your app to beta testing through your favourite beta testing software (Hockey App, Zubhium, etc.) and the results from 10 first beta testers are crushing: the app won’t install, it crashes, where is the back button?!?. You are disappointed, ok maybe it’s just those stupid beta testers.
- Weeks 6-7: Back to drawing board and you are focused on fixing all the problems reported by your loyal (and loved) beta testers. In a span of two weeks you push out eight new releases, each of them fixing a critical bug on a specific device described by your beta testers. Some of your beta testers get tired of your daily releases and drop off. Now you have another problem, you have to – recruit more excited beta testers.
- Week 8: You publish your industry changing app on Google Play – 36 hours later your app’s rating is 1.5 stars and it has 15 comments, seven of which saying “does not work on Samsung Galaxy Y, Uninstalling”. You ask yourself why didn’t any of my beta testers didn’t have that device?!?
- Week 9: You pull your app from Google Play to do a complete overhaul. This time it will work on every device and you will get those five star ratings you say to yourself.
Turbo charged iterative development – Path with Testdroid
- Week 1: You have a great app idea and you’re 100% sure you are first one to have this idea – you just have to get into that market first! You know if you can build, test it and make a good user experience, they will come.
- Weeks 2-4: The first thing you think is how can I test on as many devices as I can? So you decide to be smart and set up your Testdroid account. By the end of the first day of coding, you were able to check that your first skeleton version of your app works on bunch of most common devices and event some tablets too. You don’t need any test scripts at this point – just upload your app and Testdroid Cloud’s InstaTest will install it on all devices, click through your screens and it then gives you back screenshots, logs and performance statistics. Your development is on solid ground, so now you can move forward.
Over the next few weeks you remember you can check your app any time you want on multiple devices in Testdroid Cloud. From the screenshots, you can see that your app’s layout is not like you want it to be on some tablets, so you are able to easily fix it without loosing time. But while you are doing this, you also learn there are small things that cause your app not to work on some devices, but by fixing those things on that one device, usually fixes it on several different models as well. Developing for maximum device coverage isn’t too difficult after all you say to yourself.
- Week 5: You publish your industry changing app on Google Play – 36 hours later your app’s rating is 4 stars and it has 15 comments, seven of which say, “nice app, a real game changer”. You congratulate yourself and get back to your desk to grind out a release of new cool features to your industry changing app. Life is good.