We’ve heard this conversation on mobile app design before, where well meaning coders will say to you: “don’t design native mobile apps, it isn’t worth your time, “ followed by the common refrain/rebuttal : “native apps take advantage of the hardware, like camera, and WiFi components of the phone…”
You might wonder — why make an app using the PhoneGap framework? Using this HTML5 + native tools approach allows you to get into the hardware of the phone; like camera data, to incorporate things like a barcode scanner into your hybrid app. A full list of API elements is available here: http://docs.phonegap.com/en/1.9.0/index.html. If you want a more basic rundown of how PhoneGap itself works in a library context, check out a past ALA presentation I did for the Mobile Computing Interest Group back in 2010: http://www.ideals.illinois.edu/handle/2142/16542
Mobile app stores like Google Play and the Apple iTunes App Store help to drive traffic to your services and sites, and they will result in increased use of your library services and collections –and make possible new services, by their sheer existence.
Here are a few examples of apps I’ve built this way:
What your users and library will need is, of course, entirely up to you, but to know the options available such as hybrid approaches is a way to make informed and intelligent decisions about your library’s mobile presence.
Full disclosure: I researched and wrote an iPhone development book unpacking a hybrid approach to mobile application design that advances ways for web developers to make their apps available from the iTunes app store (goo.gl/n3LUB). But you could also make your apps available from Google Play, using the Hybrid approach as well.