The Journal of Extension - www.joe.org

December 2012 // Volume 50 // Number 6 // Tools of the Trade // 6TOT1

Tools for Creating Mobile Applications for Extension

Abstract
Considerations and tools for developing mobile applications for Extension include evaluating the topic, purpose, and audience. Different computing platforms may be used, and apps designed as modified Web pages or implicitly programmed for a particular platform. User privacy is another important consideration, especially for data collection apps. Several useful tools already exist for using mobile devices for data collection, as well as for mundane tasks like volunteer management and effort tracking.


Sabrina L. Drill
Natural Resources Advisor, Los Angeles and Ventura Counties
University of California Cooperative Extension
Los Angeles, California
sldrill@ucdavis.edu

This article is part 2 in a series on the use of mobile computing applications for Extension work. The first article discussed mobile applications for Extension, and an upcoming article will discuss mobile applications for participatory science.

Considerations for Developing Mobile Applications

The first step when building a mobile computing application (app) is identifying the topic, goal, and audience (LaBelle, 2011). The goal may be information delivery, data collection by professionals or volunteers, self-assessment and decision support, etc. (Drill, 2012). Identifying the audience will guide the sophistication of the interface. Another good exercise is to conduct market research by looking around the Apple App Store, the Google Play App Store, eXtension, state Extension services, and the Journal of Extension to see if similar apps already exist. Contact potential collaborators to see if existing apps could be built upon For example, perhaps an app for a local project could be expanded to become a multi-state collaboration by adding additional species. Several apps are listed at these websites:

http://ucanr.org/sites/ANR_Apps/

http://www.wec.ufl.edu/faculty/brunae/AppList.php

http://baegrisk.ddns.uark.edu/geospatial/smartPhoneSearch.aspx

Mobile Web vs. Native Apps

Another consideration when thinking about developing an app is the choice of whether to modify an existing Web page or develop a "native" app. This choice follows from an overall shift in the way users access the Internet, from Web pages to targeted applications used for a specific purpose (Anderson & Wolff, 2010; Anderson, 2012). Apps can be essentially mobile versions of websites accessed through a device's browser but modified for the smaller screen size and to enhance touch-screen navigation. These can be fairly easily programmed. There are more opportunities for enhancing the user experience with a native app, meaning one programmed for a particular mobile platform from the outset. The PhoneGap framework (distributed by Adobe©) bridges the gap to some degree, allowing developers to work with common Web programming languages then easily adapt the code for multiple mobile platforms. As this framework improves, nativity may become less important.

Platforms

Google's Android platform runs on 50% of U.S. smartphones, Apple's iOS on 30%, with most of the rest running the Blackberry or Windows platforms (Albanesius, 2012). While Apple may have less devices in the market, a recent assessment showed three times more apps in Apple's App store then in the Google Play Android Marketplace (Rothman, 2012). Designing apps for Android presents some challenges because the platform runs on a wide variety of devices with varying screen sizes and user interface devices (buttons and switches), but it's easier to gain access to the Google Play store. Over half of Android apps are available for free, while only a quarter of iApps are, and many apps developed for both platforms are free for Android and come with a small charge for the Apple version. This is in part because developers need to pay a small fee for an app to be sold through the App store and go through a review process.

Useful Tools

For data collection, there are some existing programs that are essentially survey data collection structures that researchers can modify to create there own mobile instrument. Epicollect and Episurvey, developed at the Imperial College of London, allow users to design a data collection instrument and project website, upload it to mobile phones, collect data onto their servers or the author's own, and view the data and perform simple analysis on the website or phone (Aanensen, Huntley, Feil, al-Own, & Spratt, 2009). User interfaces are fairly basic, and the projects are designed to be used by a team of trained participants. Open Data Kit is a similar tool developed at the University of Washington (Anokwa, Hartung, Brunette, Borriello, & Lerer, 2009). Both are designed to be used by researchers who have familiarity with survey design and programming but are not professional computer programmers or app developers. These and similar tools have been utilized for several years for social science research in the developing world, where local data collectors can bring a mobile phone to use with survey respondents who themselves may have very limited experience with technology. In addition to survey questions, on-line mapping tools such as the free app Geopaparazzi can be used to upload locations and photos of specific observations.

For more complex user interfaces, Extension professionals may prefer to work with professional Web developers or at least with technology-savvy students. In these cases, tools like Mock App can help those interested in having apps developed communicate their preferences for information and look and feel with the developers. iPhone Mockup is a free online tool that can guide the development of user interfaces. AppSketchbook sells actual paper notebooks designed to guide the development of iPhone/iPad apps.

Privacy

Privacy concerns are a potential drawback to the use of mobile devices for data collection. Privacy is an important issue for apps that track location or automatically capture sounds or images(Shilton et al., 2009). Tools for privacy protection can include notification and choice about data sharing, encryption, statistical anonymization, and protocols for data retention (Shilton et al., 2009). Exact locations can be generalized to a larger area and faces automatically blurred in photos that are uploaded (Goldman et al., 2009). Data collection mechanisms should be designed with privacy concerns in mind and data access managed to protect information where desired. Decisions about data resolution need to balance the needs of individual observers and the research goals. Privacy issues should be clearly considered at the early stages of research and design.

Unfortunately, developers are limited by the intrinsic structure of each platform. For example, the What's Invasive Android app requires users to allow the app to "read sensitive log data." The Android-sensitive data log includes geographic location information that the app needs along with other information it does not require, creating additional programming complexity to "dump" the non-necessary information. Data mining has raised concerns, and app developers should be aware of these inherent issues.

Apps to Help Extension Personnel

While the above discusses how to create apps to use with clientele, there are also apps that can help with other aspects of Extension work. Several states have developed Web-based or mobile systems for volunteer management. Another use is to help personnel collect data for the preparation of reports for USDA and other funders.

References

Aanensen, D. M., Huntley, D. M., Feil, E. J., al-Own, F., & Spratt, B. G. (2009). EpiCollect: Linking smartphones to Web applications for epidemiology, ecology and community data collection. Plos One, 4(9). doi: 10.1371/journal.pone.0006968

Albanesius, C. (2012). Android on 50 Percent of U.S. smartphones for first time. Retrieved from: www.pcmag.com/article/print/296239

Anderson, C., & Wolff, M. (2010, September). The Web is dead. Long live the Internet. Wired.

Anderson, J. Q. (2012). The future of apps and web Pew Internet and American Life Project (pp. 27): Pew Research Center.

Anokwa, Y., Hartung, C., Brunette, W., Borriello, G., & Lerer, A. (2009). Open source data collection in the developing world. [Editorial Material]. Computer, 42(10), 97-99.

Drill, S. (2012). Mobile applications for Extension. Journal of Extension [On-line] 50(5) Article 5TOT1. Available at: http://www.joe.org/joe/2012october/tt1.php

Goldman, J., Shilton, K., Burke, J., Estrin, D., Hansen, M., Ramanathan, N., . . . West, R. (2009). Participatory sensing: A citizen powered approach to illuminating the patterns that shape our world (F. a. G. Project, Trans.) White Paper (pp. 20). Washington, D.C.: Woodrow Wilson International Center for Scholars.

LaBelle, C. (2011). Place-based learning and mobile technology. Journal of Extension [On-line] 49(6). Available at: http://www.joe.org/joe/2011december/iw1.php

Rothman, W. (2012). App showdown: Android vs. iPhone. Retrieved from: http://www.msnbc.msn.com/id/38382217/ns/technology_and_sciencewireless/t/app-showdown-android-vs-iphone/

Shilton, K., Burke, J. A., Estrin, D., Govindan, R., Hansen, M., Kang, J., & Mun, M. (2009). Designing the personal data stream: Enabling participatory privacy in mobile personal sensing. Paper presented at the 37th Research Conference on Communication, Information, and Internet Policy, Arlington, VA.