KSU Mobile
Past, Present, and Future
Jason Dunfee
Distant Past...
Outside Vendor
The Good:
- Very Minimal resources from our end
- Presence in the App Store
The Bad:
- No real control over the app
- Data was often wrong or incorrect
- slow to get fixed
Past...
Ellucian Mobile the first time around.
The Good:
- Open Source Rhomobile
- Develop once deploy across multiple platforms
- Web Developer could catch on very quickly
- Ability to develop custom modules
- Presence in the app store
The Bad:
- Did not run as smooth as a native application
- Page transitions were jerky depending on phone hardware
- No real access to core phone features
- Interface was not specific to the device
Present...
Ellucian Mobile Going Native.
The Good:
- Native Applications
- Smooth running applications
- Access core phone features
- Ability to develop custom modules
- Presence on the App Stores
- User interfaces followed native guidelines
The Bad:
- Now developing two applications at the same time
- Any custom modules would need developed twice
- Larger programming learning curve (iOS, Android)
Present...
Custom Features
- Me @ KSU
- Dining
- Ticket Tracker
- TV Channel Guide
How Do We Monitor KSU Mobile...
- Students
- Google Analytics
- Crashlytics
Now that we have all this data what
do we do?
- Bug Fixes
- Add a new custom module
- Upgrade an existing module
Usability Testing.. usabilityhub.com
A.
B.
Usability Testing..
Card Sorting
Soon to be released....
What’s the future look like...
-Targeted Notifications
-Location based notifications
-Personalized Alerts
Any Questions?
Jason Dunfee
jdunfee@kent.edu