11

Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Embed Size (px)

Citation preview

Page 1: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,
Page 2: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Mobile at Bond

Page 3: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Drivers

• January 2010 mLearning@Bond Academic Discussion Group

• July 2010 mLearning report tabledThe 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.

Page 4: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Drivers

• Students• BUSA meeting• Election platform

• Why isn’t Bond in the app store?

• Office of Student Experience• Push from developers selling services

Page 5: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Drivers

• Staff• Use in class

• Ipads• Enriched ebooks

• New buildings• Paperless meetings• Operation plan requirement

Page 6: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Issues

• Data security on mobile devices• Pressure from BYOD to integrate with

corporate environment• Apple TV on the wifi

• Ad hoc development

Page 7: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Initiatives

• Blackboard Mobile Learn – 1st site in Australia

• Emerging Technology Committee• Procurement policy changes• Data security policy• M.bond.edu.au• Computer availability

Page 8: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

Projects

• Bond on iTunes U• Bond Mobile project• Student/staff projects

• Bus timetable• Career development • Games• 3D mapping• Enriched ebooks

Page 9: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

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

Page 10: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

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

Page 11: Mobile at Bond Drivers January 2010 mLearning@Bond Academic Discussion Group July 2010 mLearning report tabled The advice of the mLearning@Bond Group,

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