malinowski adams
TRANSCRIPT
-
7/28/2019 Malinowski Adams
1/24
Mobile ApplicationDevelopment at MSU
CIC CIO TechForum 2011
Brian Adams, Scott Schopieray College of Arts and Letters
Robert Malinowski
College of Veterinary Medicine
-
7/28/2019 Malinowski Adams
2/24
What are we talking about today?
Big Picture: Mobile Web vs. Native Apps Tools and frameworks for
developing mobile Issues and ideas we are working
with Primarily iOS
-
7/28/2019 Malinowski Adams
3/24
Mobile Web vs. Native
Mobile Web
Scripted to run inside themobile browser
Many distribution methods
Native
Compiled to run directly ondevice OS
Distributed in specific waysfor each platform
-
7/28/2019 Malinowski Adams
4/24
Native Applications
Pros
Native UI Execution Speed Access all device features
o Camera o Microphone o Speaker o Accelerometer o Compass o GPS o Local data stores
App Stores
Cons
Compiled Installation/Simulator to Test Device dependent builds App Stores
-
7/28/2019 Malinowski Adams
5/24
Mobile Web Applications(Before)Pros
Quicker release cycle No need to install Access to device features
o GPS o Local data stores
Device independent
No installation required AdHoc distribution No App Store
Cons
Non-native UI Running inside the
browser's resources Requires network
connection Very limited access to
device features No App Store
-
7/28/2019 Malinowski Adams
6/24
Mobile Web Applications(Now)Pros
Native looking UI o Jquery Mobile o JQTouch
Access to device features o Accelerometer o GPS o Local data storage o Animation o Touch events
Local caching
+ Everything we had before!
Cons
Running inside thebrowser's resources
No access to some devicefeatures
o Camera o Microphone
-
7/28/2019 Malinowski Adams
7/24
Mobile Web Applications(The Future)
HTML5 Draft Capture API o Access to Camera o Access to Microphone
Continued improvements in speed Mobile frameworks continue to improve Surge in desktop web applications is driving API features
-
7/28/2019 Malinowski Adams
8/24
Why Webapps?
Speed of development o Updating an application is a browser refresh o Technologies most of us already know
HTML/CSS JavaScript
Feature access isn't needed Leverage existing applications
o Web enabling current applications
-
7/28/2019 Malinowski Adams
9/24
Tourguide
Technology Requirements HTML/CSS/JavaScript web application Desktop & Mobile Off-line access (caching)
Development Requirements Developed primarily by student developers Extensibility & maintainability
Frameworks Jquery Mobile CakePHP
-
7/28/2019 Malinowski Adams
10/24
-
7/28/2019 Malinowski Adams
11/24
Priorities: 1. Free for educators
2. Accessible to students
3. Open content based 4. Non-3G based
-
7/28/2019 Malinowski Adams
12/24
JQuery Mobile and JQTouch Interface
-
7/28/2019 Malinowski Adams
13/24
Tours have images, video, textand audio
-
7/28/2019 Malinowski Adams
14/24
Obstacles, Challenges, and Lessons
UI Design, Implementation and Optimization o Fewer standards compared to desktop web o New design challenges o Increased need for UI testing
Designing for mobility o Offline access o Availability of navigation information
Frameworks, frameworks, frameworks! o Student focused development o Serving different content for different devices
Documentation o Framework documentation isn't always the best o BUT, it's at least documentation
-
7/28/2019 Malinowski Adams
15/24
Mobile Applications for Food Animal Education
Robert Malinowski, DVM, MA Director - Information Technology Center
College of Veterinary Medicine Michigan State University
-
7/28/2019 Malinowski Adams
16/24
Project Team
Dr. Ann Rashmir o Large Animal Clinical Sciences
Dr. Matt Raven o Community, Agriculture, Recreation and Resource Studies
Dr. Kent Ames o Large Animal Clinical Sciences
Dr. Art Currey o Large Animal Clinical Sciences
Dr. Michelle Kopcha
o Large Animal Clinical Sciences Dr. Jon Patterson
o Diagnostic Center for Population and Animal Health
-
7/28/2019 Malinowski Adams
17/24
Background
USDA grant funded project MSU, Ohio State, Mississippi State
Declining number of students interested inFood Animal medicine and surgery
Decreasing caseloads at academic sites
Limited student exposure
-
7/28/2019 Malinowski Adams
18/24
Goals
Increase interest in becoming Food Animal veterinarians Improve fundamental Food Animal knowledge Improve technical skills Improve critical thinking skills
Utilize technology students already use and understand o the iPod
-
7/28/2019 Malinowski Adams
19/24
Collaboration
Bringing Vets and Geeks together Clinical Faculty Programmers
o Mississippi programming team (iOS) Multimedia Developers
o Video, audio, animation Educational Research and Scholarship
o Health Sciences Reasoning Test (HSRT) o Pre and post-tests
-
7/28/2019 Malinowski Adams
20/24
The App
Develop a cow-side app Case studies
o Relevant diseases and situations o Guide students while working through cases
Reference Mode with videos, other resources
o Technique-oriented o Learn how to give IV injections, etc.
-
7/28/2019 Malinowski Adams
21/24
The App
Wireframe images:
-
7/28/2019 Malinowski Adams
22/24
Timeline
Currently in wire frame phase Summer/Fall prototype Continue to gather media and construct
additional cases Ready for Fall 2012 semester?
o iPods for students at all three sites o HSRT pre-test in Fall, post-test in Spring
-
7/28/2019 Malinowski Adams
23/24
Hurdles
Defining the structure of a Case o Neatly packaging the clinical environment
Difficult to coordinate three sites Deadlines
o What are those? Loading wireframes on devices
-
7/28/2019 Malinowski Adams
24/24
Benefits
Synergy between participants Unique talents at each site/department
o Clinical faculty o iOS developers at Mississippi o Media production at MSU
Faculty need to see it in action o Generate other clinically-relevant ideas?
IT beyond email and file servers Educational research component