You have the great app idea. You develop it and it works. You even get it to market, promote it , and it sells. But what’s the point if it’s fraught with annoying inconsistencies, crashes when a phone call comes in, or drains the user’s battery? You’ll get bad reviews, but isn’t that a bit too late?
Take one developer, one carrier, a test house and a couple of distribution channels. Put them together and what do you get? An agreement on the importance of the quality of a mobile app, but differing views on how to achieve it. What do *you* think?
The panel will explain their views, and examine the following:
- what to test when
- what tools can help
- how automated testing may or may not be useful
- emulator testing
- testing for battery life and network performance
… and when to stop!
Hear the views from the panel, and have your say too.
Moderator: Martin Wrigley, Chair, App Quality Alliance (AQuA)
Emil Bengtsson, Senior Project Manager, Sony Mobile Communications
Peter Rembiszewski, Senior-Product Development Engineer, AT&T
Stephen Peacock, Director of Sales MMO/Social at Babel Media
Rhodri Thomas, Chief Commercial Officer, SwiftKey
(Right-click & select "save link as" or "save target as"...)