2. Mobile at Bond

3. Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group, therefore, is that Bond University should begin a steady investment that develops mLearning initiatives. The initiatives should cover both the flexible delivery of administrative information to students and the delivery of educational content. The aim must be to improve the student experience by making content and services available to our students in a way that enhances, but does not replace on- campus engagement.

4. Drivers Students BUSA meeting Election platform Why isn’t Bond in the app store? Office of Student Experience Push from developers selling services

5. Drivers Staff Use in class Ipads Enriched ebooks New buildings Paperless meetings Operation plan requirement

6. Issues Data security on mobile devices Pressure from BYOD to integrate with corporate environment Apple TV on the wifi Ad hoc development

7. Initiatives Blackboard Mobile Learn – 1 st site in Australia Emerging Technology Committee Procurement policy changes Data security policy M.bond.edu.au Computer availability

8. Projects Bond on iTunes U Bond Mobile project Student/staff projects Bus timetable Career development Games 3D mapping Enriched ebooks

9. Bond Mobile User stakeholder group Requirements – 6 services Technical Reference Group Academics, marketing, researchers, students, developers Issues Web v. native app In-house v. outsourced

10. Bond Mobile Recommendation: A mobile application development framework should be selected on the basis of the following requirements: –Cost –User experience (Social, easy, fun) –Future development options based a native Software Development Kit (SDK) –Delivered services

11. Bond Mobile Stage 1 –Implement delivered services (modules) Stage 2 –Develop missing required services (modules) Stage 3 –Develop mobile framework –Look for creative/innovative ideas, especially for Teaching and Learning