Overview of content related to 'mobile' http://live.ariadne.ac.uk/taxonomy/term/16/all?article-type=&term=&organisation=&project=&author=gary%20brewerton&issue= RSS feed with Ariadne content related to specified tag en Developing a Prototype Library WebApp for Mobile Devices http://live.ariadne.ac.uk/issue71/cooper-brewerton <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue71/cooper-brewerton#author1">Jason Cooper</a> and <a href="/issue71/cooper-brewerton#author2">Gary Brewerton</a> describe the development of a prototype WebApp to improve access to Library systems at Loughborough University for mobile devices.</p> </div> </div> </div> <p>Reviewing Loughborough University Library’s Web site statistics over a 12-month period (October 2011 – September 2012) showed a monthly average of 1,200 visits via mobile devices (eg smart phones and tablet computers). These visits account for 4% of the total monthly average visits; but plotting the percentage of visits per month from such mobile devices demonstrated over the period a steady increase, rising from 2% to 8%. These figures were supported by comparison with statistics from the Library’s blog, where, over the same period, there was also a steady increase in the percentage of visits from mobile devices.&nbsp; This increase was on a smaller scale than the Web site, rising from 0.5% up to 4%.</p> <p>Having identified this increase in the usage of mobile devices, it was decided to investigate ways to support mobile access more effectively.&nbsp; As part of this investigation, the Library's Systems Team undertook the development of a prototype mobile app.</p> <h2 id="Deciding_the_Prototype-s_Features">Deciding the Prototype's Features</h2> <p>The first task undertaken was to produce a list of functionality that could be included in the Library WebApp.&nbsp; The list was based upon current Library services and consisted of the following:</p> <ul> <li>Support library catalogue searching</li> <li>Display opening hours (pulled from the Library Web site so data can be maintained in one location)</li> <li>Display current item loans, requests and holds <ul> <li>Indicate overdue items</li> <li>Indicate recalled items</li> <li>Offer option to renew loaned items</li> <li>Offer option to cancel requests for items</li> </ul> </li> <li>Reading lists <ul> <li>Ensure module list displays all modules for which the user is registered</li> <li>Should handle multiple levels of reading lists</li> <li>Include thumbnails</li> <li>Include library holding information</li> </ul> </li> <li>Display current room/PC bookings <ul> <li>Display list of bookings including resource name, start time and end time for each booking.</li> <li>Offer option to cancel a room/PC booking</li> <li>Offer option to make a room/PC booking</li> </ul> </li> <li>Display upcoming library events (pulled from the Library Web site) <ul> <li>Include both upcoming workshops and events</li> </ul> </li> <li>Display library news (taken as a feed from our Library blog)</li> <li>Offer feedback option</li> </ul> <p>After reviewing this list, it was decided to leave out the searching of the Library Catalogue feature as the Library's discovery tool (Ex Libris’s Primo [<a href="#1">1</a>]) was scheduled for a number of updates that would improve the support of mobile devices. Therefore it was decided to wait and see how the improved mobile interface performed before deciding how to integrate it into the mobile app.</p> <p>Additionally it was decided not to implement a number of the other features, those that would either require new APIs to be created for other systems or those that would alter the information stored in the other systems.&nbsp; These features would be carried forward for implementation in a future version of the mobile app.&nbsp; Consequently features excluded from the pilot version were:</p> <ul> <li>library catalogue searching</li> <li>the option to renew loaned items and cancel requested items</li> <li>the option to make or cancel a room/PC booking</li> </ul> <h2 id="WebApp_versus_Native_Apps">WebApp versus Native Apps</h2> <p>An important early decision was whether to create the Mobile App as a WebApp or as a number of native apps?&nbsp; A native app is one that is developed in the native language for the platform (Objective-C for iPhone/iPad devices, Java for Android devices, etc) and usually delivered via an app-store (iTunes for Apple, Google Play for Android, etc).&nbsp; A WebApp is developed in HTML5 and JavaScript, being delivered to the mobile device via the World Wide Web.</p> <p>There are pros and cons to developing a mobile app as a native app or as a WebApp. Native apps have full access to a mobile device's resources but need to be developed as a separate app for each platform on which they are to be made available.&nbsp; Conversely developing a mobile app as a WebApp restricts the resources that can be accessed to those available to the device's Web browser, although a single developed WebApp can work on multiple platforms.</p> <p></p><p><a href="http://live.ariadne.ac.uk/issue71/cooper-brewerton" target="_blank">read more</a></p> issue71 tooled up gary brewerton jason cooper apple google loughborough university w3c adobe ajax android apache api authentication blog browser cache cataloguing content management cookie css data framework google books html html5 ipad iphone itunes java javascript jquery json library management systems local storage metadata mobile native app native apps open source passwords perl restful rss standards tablet computer url vocabularies web app web browser web development widget xhtml xml Mon, 10 Jun 2013 13:33:09 +0000 admin 2438 at http://live.ariadne.ac.uk