Six Questions You Should Ask Before You Ship Your Next Mobile App


When you are building a high-quality mobile app, you are committed to both time and money Inadequate testing, however, can rob you of your investment. Forrester’s checklist for mobile testing identifies 38 errors that can be easily ignored. Here are 6 of them that many mobile application developers forget about:

1. Have you tested your UI with all kinds of gestures? What happens when your user swipes: Does it bring up a menu or dismiss the app? As devices evolve, the gestures we use to manage them change. If you use gestures in your app, you need to experiment with different OS versions.

2. Do you create regression tests while updating the app? You fixed that bug and now it’s back from the dead. To avoid, report and correct any errors that you think are buried, add them to the test case so you can be sure they are fixed.

3. Have you checked what happens if you don’t have permission? Many devices restrict access to sensors that can provide data about the user. Users may refuse to grant you permission – or may later revoke it. Make sure your app is behaving well in both cases.

4. Did you check your app when network was not available? Your infrastructure team ensures that your development lab network is strong. Your home may be a (or your car) a little flaky. Use the Virtual Network Testing tool to make sure your app does the right thing when your users are out of network range – and backs up when the network returns.

5. Does the app meet the standards of the App Store? Your app should be available on Google Play Store and Apple App Store. Make sure your app complies with Apple and Google standards Remember, user feedback is important: low scores or excessive crashes can lead to your app being pulled.

Tornado guard

Used with permission from xkcd.com.

6. Is your app updated properly from previous versions? Mobile apps are updated frequently. Libraries change below, features are added, and the app stores are forced to upgrade to the lowest platform level. Older versions may include triggers (such as ACTION_MY_PACKAGE_REPLACED for Android) that run unexpectedly with the new library. Automatic tests for upgrades to versions installed by previous users.

To learn more, get the complete Forrester Mobile Testing checklist.

Written with Zachary Stone



Source link

Leave a Reply

Your email address will not be published.