• How do we know when to stop testing?
• What type of testing should we perform—manual code inspections or unit, system-level, black-box, white-box, or integration testing—and in what combinations?
• What should we test—reliability, performance, security, or something else?
• What tools should we use use—commercial or open source?
• What defects should we fix and why?
• When should we retest?
• What types of testing would we use for apps, and how much testing is enough?
• Is it easier to vet the app vendor or test the app?
• What will we be able to say about an app's quality from inclusion in a particular app store?
• If app stores become software quality gatekeepers, will they be able to filter out lesser-quality apps quickly and in near real time?
• If app stores become the de facto filters for app quality and security, who will certify that the app stores are doing their task adequately—for example, disallowing counterfeit apps?
Federal and state regulators, along with privacy advocates, are pushing for more clarity and transparency in the way apps may use personal information, including your name, gender, and email address, as well as your hometown, family relationships, or religious and political affiliations. Various versions of a so-called 'privacy bill of rights' for mobile phone users are circulating and being adopted by some app developers.