Make Sense of Mobile and Build an App Without Code
•
0 recomendaciones•535 vistas
The document appears to show annual totals for something increasing over time from 2000 to 2011, starting at 25,000 in 2000 and reaching 17,558,265 in 2011, with totals generally doubling or increasing by large amounts each year.
Recomendados
Recomendados
Más contenido relacionado
Último
Último (20)
Destacado
Destacado (20)
Make Sense of Mobile and Build an App Without Code
- 6. 0 0 25,000200,000 600,000 1,200,000 2,520,366 4,668,096 7,898,909 10,500,000 13,000,000 17,558,265 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011
Notas del editor
- http://images.alarabiya.net/27/79/640x392_6697_250168.jpg
- Expected to double in three years; took 16 years to reach 1 billionAndroid phones in the developing world are less than $100, expected to lower to $50 in 2013 (http://readwrite.com/2013/05/13/mobile-is-taking-over-the-world)
- Is any of this surprising? What are the implications?
- What does this mean for library services?
- Definition
- Available via app store, sometimes for a fee (monetization)Download and install on the deviceUpdate as wanted, needed
- Native features are specific to the operating system on the deviceGPS, camera, video, accelerometer
- Standardized SDK, development tools, user interface buttons
- Rich user experience which includes speed – native apps are fasterChange these slides – hand drawn plus and minus, page for each
- Other examples – mobile tours (NCSU)Other examples?
- The app is the browser, the code runs in the browser
- API examples – twitter feed to your library siteGoodreads to FacebookGoogle map of library branches
- Riche user experience which includes speed – native apps are faster
- Example tour - http://tour.library.oregonstate.edu/
- Mobile website is not an app – just your web contentThere is a default position
- Riche user experience which includes speed – native apps are faster
- Can look at analytics to see what people are more likely to use, talk to users, look at Pew data on handoutBe careful to also allow access to your full site in case info needed isn’t what you selected
- Riche user experience which includes speed – native apps are faster
- Responsive - https://biblio.ugent.be/m
- Responsive design – one site, many platforms
- EthanMarcotte article, two A List Apart books
- Riche user experience which includes speed – native apps are faster
- Summary of how to decide when to use each – questions?
- Pay attention to your own user experience – what you want, when you’re frustrated, when things workMe and DPL text a call #, can’t watch a 48 hours video on mobile, Kieran’s example of QR code linking to lengthy PDF
- 5. “I would have done more” - Stepping back from usability testing to actual use of mobile library sitesPresenters: Laurie Bridges, Instruction & Emerging Technologies Librarian and Hannah GaschoRempel, Graduate Student Services Coordinator & BioSciences Librarian (Oregon State University)
- LCD thinking – important to try things