dcsimg

Wearable Apps: Ten Factors Developers and Testers Need to Know

  • Wearable Apps: Ten Factors Developers and Testers Need to Know-

    The Starting Line

    Since the new platform is going to introduce "noise" and affect known release schedules, it is important to start small, gain confidence, stabilize internal processes, and then grow device coverage and add more sophisticated use cases. Here's a good guide to follow:

    • Existing QA Program: This market is evolving, so start small. Choose the leaders similar to the smartphone area – Samsung, LG and Apple. Start by targeting their watches and grow. Get market feedback.
    • Implications: Not only is there a dependency on the app first with the smartphone, but there is a software release between the two platforms. This is why developers need to choose the leaders and make sure it works on both the phones and then the Apple Watches.
    • Test Plan Preparation Automation and CI: Extend what you already have for automation. Otherwise, it will be impossible to sustain these projects.
    • Adjustments: Keep going back and tweaking your strategy to make sure you're testing on all devices. Get feedback.
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12

Wearable Apps: Ten Factors Developers and Testers Need to Know

  • 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12
  • Wearable Apps: Ten Factors Developers and Testers Need to Know-7

    The Starting Line

    Since the new platform is going to introduce "noise" and affect known release schedules, it is important to start small, gain confidence, stabilize internal processes, and then grow device coverage and add more sophisticated use cases. Here's a good guide to follow:

    • Existing QA Program: This market is evolving, so start small. Choose the leaders similar to the smartphone area – Samsung, LG and Apple. Start by targeting their watches and grow. Get market feedback.
    • Implications: Not only is there a dependency on the app first with the smartphone, but there is a software release between the two platforms. This is why developers need to choose the leaders and make sure it works on both the phones and then the Apple Watches.
    • Test Plan Preparation Automation and CI: Extend what you already have for automation. Otherwise, it will be impossible to sustain these projects.
    • Adjustments: Keep going back and tweaking your strategy to make sure you're testing on all devices. Get feedback.

Apple's recent release of the Apple Watch has fueled excitement for owning the latest Apple device and the next wearable. While wearables are only a small slice of the greater Internet of Things (IoT) industry, the market is rapidly growing. With IDC forecasting 126.1 million units shipped by 2019 and the worldwide market for IoT solutions growing to $7.1 trillion by 2020, the focus on developing quality apps is now more important than ever.

However, dev/test teams are still struggling to embrace and incorporate IoT into existing development cycles. The biggest challenge for companies that want to develop for wearables is ensuring that quality matches user expectations. If a hotel chain says users can open their hotel room door using Apple Watch, it needs to happen.

How does the mobile app developer and tester combat the new challenges IoT brings to the forefront? By adopting continuous quality as a process to increase the speed of development, keep up with an increasing number of devices that apps should work on, and reduce the number of defects reaching production – ultimately cultivating higher end-user satisfaction.

By testing the application in all scenarios (across a variety of devices, under various network conditions and traffic, etc.) and throughout the entire mobile app development lifecycle, dev/test teams can ensure that they reach the level of quality they're aiming for (the app works where you said it would work, and the brand you represent is being seen as you wish it to be seen).

In this slideshow, Eran Kinsbruner, mobile technical evangelist at Perfecto Mobile, has identified 10 things that developers/testers need to be aware of when developing apps for wearables.