A few weeks ago, Progressive Web Applications, Part 1: the New Pack Mule of the Internet _introduced PWAs and the technologies behind them. We shared that article to the MobileGov Community of Practice and asked about the pros and cons of this approach to winning mobile moments._ What Are Some Benefits of PWAs? PWAs bring a host of advantages over the traditional native mobile and Web methodologies including:
****A mule is the hybrid offspring of a male donkey and a horse. This new species is stronger and better equipped than the species from which it comes. Overall, mules tend to be healthier, more sound, and live longer than horses. They are favored over horses in mountainous terrain because the mule has a reputation for being more surefooted than their equine cousins. Finally, mules do not require expensive grains, eat less and don’t tend to overeat as horses do.
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?
With 14 test cycles under our belt, the Federal CrowdSource Mobile Testing Program has heard one recurring theme from our testers—”there’s too much information!” While both desktop monitor and smartphone screen sizes are growing, there is still no comparison. At our desks, many of us are using a 24 inch (or even bigger) monitor. How big is your smart phone? Way smaller than a desktop monitor. The user will have a radically different experience on a desktop, and they are usually expecting a different experience.
In most instances, your hardware and software are developed independently but are expected to function properly together. For example, when a Web application is developed in HTML, it is expected to function properly on an Apple computer using Safari as well as a Windows computer using Internet Explorer. This sounds simple, but there are thousands of combinations of browser types and versions as well as operating systems, and the number of combinations increases exponentially as we add in the multitude of mobile device makes and models.
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?
Practice makes perfect. But in the mobile world, it’s testing that makes products better. For federal agencies that have developed their own apps or mobile-friendly sites, the CrowdSource Mobile Testing Program offers a simple way to collect feedback on compatibility testing. Since the program’s inception in March 2013, eight federal mobile websites (including responsive design) have been tested by 65 federal employees from 41 agencies. The benefits are twofold: agencies receive actionable feedback about their mobile websites, and testers gain valuable knowledge about mobile websites that they can share with their own agencies.
Making tables, charts and graphs mobile friendly is like squeezing 10 pounds of sugar into a 5 pound bag. Mobile Gov Community of Practice member Debra Fiorrito from the Defense Accounting and Financing Service recently highlighted this challenge in her responsive Web design implementation. The challenge also came up during a call with the Federal Mobile Crowdsource Testing Program when discussing photo carousels. David Fern, from the Social Security Administration, Clair Koroma, from the Department of Health and Human Services, and Beth Martin, from the Federal Aviation Administration, researched the topic to see what current approaches there are and found eight ways organizations are making charts and graphs mobile friendly.