The Student/Library Collabora4ve: Toward Transforma4ve Mobile Library Service David Ward Jim Hahn Lori Mestre (2012, October 7) Student/library collabora1ons for mobile applica1on development. LITA Na(onal Forum, Columbus, OH, October 4-­‐7. Background Two year Na4onal Leadership Grant (IMLS) Document and share best prac4ces for working with student design teams Student collabora4on to develop mobile apps Increase Student Input Create Connec4ons Iden4fy Transferrable Best Prac4ces Partners Department of Computer Science Student Groups Department of Electrical and Computer Engineering Graduate School of Library and Informa1on Science Campus Informa1on Technology and Educa1onal Services Documenta1on on best prac1ces Project Deliverables APIs/Apps for providing common types of library data Student-­‐developed soKware applica1ons Produc1on and assessment of significant new knowledge and tools User research/usability studies Possible Apps Wayfinding Apps Recommenda1on service for items related to student’s major, courses, resources … Others Design Environment •  How grant-­‐based methodologies will leverage exis1ng design infrastructure •  Cumula1ve •  Modules •  Design pipeline Modular Architecture •  Looking for clip art of puzzle piece represen1ng Bib_ID, other unique ID… (Jim) Methodologies •  Class Collabora1ons (three CS classes) •  Contests •  Design Camps CS Class Design Process App Coding App Idea Genera1on Code Base User Tes1ng Code Clean-­‐up (In House) Methodologies – Class Collabora1ons •
•
•
•
•
•
CS Class – Senior Projects Library is “client” Students come up with app ideas Library supplies some codebase Students add to codebase and design apps Usability tes1ng at mul1ple stages Programming Studio •  CS Class Programming Studio •  Students work on por1ons of modules •  Students are new to programming, may need more mentoring and outlay of 1me and direc1on •  Code cleanup will require more work on our part Interface Class •  CS Class – User Interfaces: Students contacted librarian working on Augmented Reality apps •  Students want to design AR interfaces for wayfinding using CAD maps •  Students will leverage exis1ng codebase and contribute alterna1ve mobile app interfaces for exis1ng modules Contest Design Process Judging In House Coding of Winners App Idea and Presenta1on Genera1on Code Base User Tes1ng Code Clean-­‐
up (In House) Methodologies – Contest •  Based off of successful College of Business mobile design contest •  Recruit students and form teams •  Discuss library needs, mobile focus •  Challenge: “Design a mobile app to enhance student use of library resources and services” Methodologies – Contest •  Environments Sessions •  Tour campus spaces •  Teams log possible student mobile needs Methodologies -­‐ Contest Presenta4ons should include: –  Name of App –  Problem app is designed to solve, including evidence for the need for the app –  Descrip1on of app and how it will func1on –  Audience for the app –  Mock-­‐up of the App in ac1on –  Example use cases for the app –  How and why the app will improve student access to library collec1ons, services, and/or facili1es. Methodologies – Contest •  Teams design concepts and wireframes for apps •  Panel judges apps and presenta1ons, awards prizes •  Top app ideas are built by design lab aKer contest Camp Design Process App Coding + Group Presenta1on App Idea Genera1on Code Base Code Clean-­‐
Up (In House) User Tes1ng Methodologies – Design Camp •  Based on ARIS camp event –  (hcp://arisgames.org/) •  Weekend event •  Set up space and devices for design •  Students form loose teams to build as many apps as possible in 1meframe •  Students present apps •  Prizes awarded Ques1ons •  David Ward dh-­‐ward@illinois.edu •  Jim Hahn jimhahn@illinois.edu •  Lori Mestre lmestre@illinois.edu