1. Mobile Apps & Mobile Web
Ivon Foster-McGowan, PhD
Assistant to the Provost for Special Projects & Academic Technology
The University of Alabama
SACRAO 2013
February 5th, 1:30pm
Session T3.1

2. NOTE: The majority of the session consisted of live demonstrations of the apps noted on each slide. This presentation is intended to provide an overview of the points made and the apps demonstrated. Please send questions to

3. The difference is narrowing
Native Apps vs Web Apps
The difference is narrowing
Native apps can only work on the platform they were built for, and take longer to develop
Native apps can take advantage of hardware: push notifications and smoother look and feel
Native apps can include links to web apps
Visibility increased thru app stores
Updates dependent on user
iOS & Blackberry reviewed prior to availability; delays updates
Cost is higher, vendor often involved, more time and effort even if built in house
Built with standard web technologies
Web apps easily used by most devices mobile devices
Can be designed to look like native apps
Less visibility, do your own marketing
No download required
Updates automatically
More efficient; in house web resources can typically pick up programming easily

6. Alabama Vendor partner: Blackboard Mobile
iOS launched 4/24/11; Android & Blackberry June 2011
Over 110,000 downloads to date
60% iOS 30% Android 10% Blackberry
Users in over 150 countries
#1 complaint: "Where's myBama & Blackboard?!"
Delivered portions of myBama & myTickets with web app and integrated Mobile Learn fall 2012
Future: web app for Places; native e-Accounts (one card); parking??; computer labs??

7. Caution: Student Developers
Brilliant minds with great ideas
Must have university involvement
Sustainability & enhancements: who develops it after graduation?
Who will handle updates & bug fixes
"UF Mobile no longer available" - see letter from student developer

8. Mobile Web
Most universities have mobile version of website, at least top tier sites
Most libraries have gone to mobile web
Giving cannot be done in native app, at least not iOS
Many university native apps have mobile web features
TransLoc - buses

9. Bridging Native Apps Accessing a native app from another app
Requires download of both apps
Stanford is the king of app bridging
North Dakota tours

10. Creative Design OU2GO & GA Tech coolest Texas & Arizona unique
West VA very sleek & simple
Samford & Seton Hall: no branding once in the app

11. Functional Design
Most univ apps have basics: directory, map, news, video, athletics, etc
Parking! OU2GO
Purdue & North Dakota - labs feature
myUCR (CA Riverside) - requires sign or create acct??? Didn't bother
Loyola - beautiful, but took a second to figure it out
Ole Miss - NEWS!! Hard to find app features

12. Maps & Buses
Apple iOS 6 - Killed Google Map Kit - see Alabama and Vanderbilt, no buildings or labels
Custom map - Arizona
None work without network!
TransLoc integration

13. Admissions Apps
Better to have independent admissions app or unified institution app?

14. Conclusion Benchmarking is essential
Involve more than IT, need user community
Consider your developer options: in house, vendor, students....in any case, there must be a responsible party
If vendor, don't hesitate to push the limits, get them out of their box
Always think about sustainability and enhancements
Unified app or independent apps

15. Thank You!