With the proliferation of smartphones and mobile apps, startup companies are emerging with the dream of building a successful app. While having a mobile mindset and developing a mobile strategy is good with no question, misconceptions about mobile app development are here, there, and everywhere. For businesses, especially small market players, these misconceptions can result in any consequences – from complicating the developing process of wasting hundreds of thousands of money and losing customers.
So, what are these myths? The myth list could be very long, but we are going to focus on the top 5 myths we have seen when it comes to mobile app testing.
Myth 1: Testing on emulators will suffice.
Emulators might be useful in the early stages of app development, but they will not bring any valuable information regarding the quality of your apps in the long run. As emulators do not contain any hardware (like chipsets and memory), developers will not get the whole picture of app performance on device models with different chipsets. If you are building a million-download app, keep in mind that only real devices will give you the testing results you expect.
Truth: Not a single user plays mobile apps/games on an emulator. So what is the sense of testing apps on emulators?
Myth 2: 10-20 devices can represent the whole Android market.
The diversity of Android market is rather big – different OEMs, chipsets, resolutions, screen size, etc. Testing apps on only a few popular devices are no longer enough. The same device model carrying Android OS 4.2 and 4.3 gives users quite different experiences. As a matter of fact, much of the quality in a mobile app is wrapped up at the end user experiences. Suppose your app does not work on a single model, the end user experiences for that model is totally missing. As a result, more ‘thumbs down’ will appear and your app ratings and revenue generation will suffer.
Truth: Testing apps on as many diverse devices as possible to secure the largest market coverage.
Myth 3: Mobile security is not our priority thing.
Last month, Gartner says more than 75 percent of mobile applications will fail basic security tests through 2015. “Most enterprises are inexperienced in mobile application security. Even when application security testing is undertaken, it is often done casually by developers who are mostly concerned with the functionality of applications, not their security,” says Dionisio Zumerle, principal research analyst at Gartner. If you still remember the damage of the Heartbleed bug half a year ago, you would certainly take mobile app security as seriously as you can.
Truth: Mobile security is as important as great features
Myth 4: Testing always comes after development.
Forget about the old way that development goes first, and testing comes later. When companies incorporate testing during the development, QA team can quickly find out and report the errors to Dev team and get these bugs fixed. Even if 10% code changes or is added to the app, the whole app/feature needs to be tested thoroughly. If there is no testing involved in the development phase, the whole development-testing cycle will be extended, which leads to a high cost to the company. In turn, it slows down the app’s time-to-market and leads to a loss of customers as well as revenue.
Myth 5: Our mobile app is only for internal use, so we don’t need to test it as well as commercial apps.
Mobile apps are built for a variety of purposes. They can be internal use for organizations/teams or commercialized for business growth, like mobile games. As QA experts, the major responsibility is to ensure the applications working perfectly as it was planned and desired. The main users of internal apps should be able to work efficiently and effectively with the help of the apps, instead of complaining the bugs holding them back every day.
Truth: For any mobile apps, the quality is utmost important regardless of the purposes of the apps.
There may be more myths to talk about. But these 5 myths are what we have heard most often when we are solving the problems for the mobile ecosystem. To create a mobile app to meet your goal, be sure that the quality is what you really need to take seriously. Any bugs or security issues detected by your end users do only harm to your business.