Around Q3, I was looking for way to test the HTML and CSS of an online application that was to be public-facing. At first, my office’s plan was to connect mobile devices to the network owned by federal employees on a volunteer basis for testing. All of a sudden, a new policy came down that stated, “devices that were not purchased by the agency could not be connected to the network.
In the sea of apps, users get choosey with which apps can take up space on their phone. With one uninstall click the user can decide to breakup with the app if they have a bad experience. To keep your app from being all alone, the MobileGov Community of Practice put together six Mobile User Experience Guidelines to help keep mobile users in love. DigitalGov University hosted a webinar in which the American Battle Monuments Commission (ABMC) highlighted two of these guidelines.
Let the mic drop! Mobile moments are created with the expectation that an app can stun the crowd. Do not let your audience down; they may never come back. Federal Student Aid (FSA), in an effort to provide better customer service, decided to build a mobile-responsive website. Kaegy Pabulos, a Borrower Experience Specialist and project manager for StudentAid.gov, described this as a challenge because of the need to combine over 12 different websites into one access center.
What is mobile-friendly? Mobile-friendly simply means your visitors can use phones and tablets to visit your website and have a user-friendly experience. Many of us get toward the end of mobile site development and really do not know if what we created is “mobile-friendly.” We think we have followed all of the mobile best practices and performed usability testing. However, do we have something concrete to quantitatively certify that we are mobile-friendly?
Every second counts, even those precious two or three seconds it takes your website to load. When it comes to mobile, users won’t wait. During a recent DigitalGov University webinar, Jeremy Vanderlan, Technical Deputy for AIDS.gov, explained how even fractions of a second can have a negative impact on a user’s impression of your website. Performance/load time for Web pages has become so important that Google now considers it one of three equal components to good user experience, along with design and functionality, he noted.
The more you test, the more you know. We recently highlighted lessons learned from the CrowdSource Mobile Testing Program, discussed the mobile emulator dilemma that many agencies face, and today we’re back with a few insights on native app testing. The Federal CrowdSource Mobile Testing Program yields a rich set of participant feedback that helps individual app creators improve their product. While the program primarily tests mobile websites created by federal agencies, the team tested early prototypes of the American Battle Monuments Commission’s Normandy App and the National Oceanic and Atmospheric Administration’s CrowdMag app as a pilot.
Government agencies have created a variety of apps to meet the needs of the public. As you join in on the mobile first trend and begin developing your shiny new mobile application, you will need to test it. There are a basic set of questions that must be answered: Does it function properly? Does it function properly on the different mobile devices your customers are using? Do all developers and testers need a collection of devices to physically test the application with?
Remember the Golden Age of Web development? A time long ago when there were only five desktop browsers to support, a few different screen sizes and every user connected via broadband? Well, those days are over. With the advent of mobile Web implementations like responsive Web design, there are three times the number of browsers working on many different-sized devices with varying operating systems and connection speeds. Trying to tackle all of these factors quickly becomes a testing nightmare.
Building quality mobile products is the greatest challenge for succeeding in the mobile space according to an infographic by SmartBear. One key to developing quality mobile products is testing, as “nearly 50% of consumers will delete an app if they encounter just a single bug.” As a result the following processes are used to ensure a quality mobile app: Manual Testing – 27.96% Automated Testing – 18.16% API Testing – 16.
What if Thomas Edison Didn’t Use Test Cases? “I have not failed. I’ve just found 10,000 ways that won’t work.” ~Thomas A. Edison Software testing is like a science experiment. The Tester must plan: methods, steps, and paths through the Application Under Test (AUT) to completely exercise the application and uncover undesirable issues before its release. If Thomas Edison did not document his 10,000 test cases, he may have wasted time by executing some tests multiple times, or he may have missed some combinations, thus making the development of the light bulb take even longer or not at all possible.
Security testing is used to ensure that a mobile product does not pose a threat to agency IT systems and databases. In addition, privacy testing ensures that an app does not put the user’s personally identifiable information into a compromisable position. This article was developed as part of the Mobile Application Development Program. See our general guidelines to testing article for more resources on mobile product testing. Government Guidance Please coordinate with your ISSO when creating mobile or digital products.