[Web4lib] apps vs webpages?

[MJ Suhonos]

In my opinion, there is *absolutely* much wrong with creating an app — not the least of which is the now-common complaint of having to be reviewed and sanctioned by the distributor (ie. Apple).  For applications which are primarily off-line or make extensive use of the hardware (eg. games, GPS-backed apps, note/information-taking tools, etc.) there is a very strong use case for native apps.

But for resource ("catalogue") searches which inherently access an online database, you need to have an Internet connection anyway.  In that situation, you gain a host of benefits from building a web-based application, not the least of which is cross-platform (and cross-device) compatibility.  Web-based == server-based, which means upgrades, bug fixes, etc. can be done incrementally and immediately, rather than bundles up and pushed out as point releases (and reviewed each time).

Case in point: I was able to build mytpl.ca in a few evenings, based solely on some LAMP-based hacking on my personal computer, and using some open standards (namely Z39.50 and HTML5's geo-location support).  Building a dedicated iPhone app would've taken much longer, not including the fact that I'd have to learn a variant of C (the only languages Apple now allows).

A well-written web application (and mytpl is by no means an example of this), combined with some good cross-platform frameworks like IUI, and W3C-based support for hardware features, provides many of the advantages of a native app without many of the limitations.

MJ

On 2010-04-13, at 12:58 PM, Dobbs, Aaron wrote:

> Nothing wrong with creating an app if the local audience desires it 
> (and how does one know if the local audience desires it without creating one for them to try out?)
> 
> A different app for every vendor or each library's catalog doesn’t make much sense, to me, though. 
> An app which pulls from a large, multi-format index of authoritative, academically-focused stuff would be a killer app if it were tied to an authentication mechanism - until authentication is no longer needed. 
> A discovery layer (Summon, EBSCO Discovery Service, WorldCat, etc.) app would make the most sense - assuming the results were useable on the smart phone.
> 
> -Aaron
> :-)'
> 
>> -----Original Message-----
>> From: web4lib-bounces at webjunction.org [mailto:web4lib-
>> bounces at webjunction.org] On Behalf Of Wilfred Drew
>> Sent: Tuesday, April 13, 2010 12:47 PM
>> To: Web4lib at webjunction.org
>> Subject: [Web4lib] apps vs webpages?
>> 
>> I am beginning to wonder if libraries should even attempt to create
>> apps for smart phones.  We can't possible create what is needed for
>> even the most popular models of smart phones.  Why not use the cloud
>> and create web based apps or good mobile sites?  Is OCLC taking the
>> wrong approach by creating apps for WorldCat Local?  Are database
>> vendors making a mistake by creating apps?
>> 
>> The creation of apps for finding and processing information seem
>> counterproductive to me.
>> 
>> -----------------------------------------
>> Wilfred (Bill) Drew, M.S., B.S., A.S.
>> Assistant Professor
>> Librarian, Systems and Tech Services
>> Strengths: Ideation, Input, Learner, Command, Analytical
>> E-mail: dreww at tc3.edu
>> Follow the library: http://twitter.com/TC3Library
>> Please consider the environment before printing this e-mail or
>> document.
>> 
>> _______________________________________________
>> Web4lib mailing list
>> Web4lib at webjunction.org
>> http://lists.webjunction.org/web4lib/
> _______________________________________________
> Web4lib mailing list
> Web4lib at webjunction.org
> http://lists.webjunction.org/web4lib/