Mobile technology and the humanities

April 20th, 2010 |

NCSU Libraries recently launched WolfWalk (m.lib.ncsu.edu/wolfwalk), a web-based self-guided tour of the NCSU Campus for advanced mobile devices such as Apple’s iPhone/iPod touch/iPad or devices running Google’s Android OS. The project makes use of a device’s location-awareness to display historic information and images of sites of interest in the user’s vicinity, thus creating an in situ learning experience. I would be interested in talking with others who are working on or thinking about similar projects, either related to exposing library/museum collections in new ways or using the capabilities of the mobile devices for studying and teaching the humanities (e.g., history). Also, how could concepts such as augmented reality be applied in this context?

Site note: We published WolfWalk as a mobile web site, but also plan on launching a “premium” iPhone application sometime this summer. ┬áThis application will be available free of charge, but will include some features that we could not implement in the mobile web version for technical reasons. I’d be interested in hearing what people think about the two approaches, i.e., the open, browser-based mobile web vs. the platform-focused and tightly controlled “There’s an app for that” approach.

Favorite 0 No users have favorited this post yet.

Comments Feed

5 Responses to “Mobile technology and the humanities”

  1. Mark Long Says:

    That sounds like an interesting project. If you are not aware of it already you may want to look at the program created by The University of West Florida entitled Next Exit History which the University of Central Florida (where I am located) has partnered with for the creation of content. The scope of the project is to generate historically-themed podcasts to be delivered to GPS-enabled devices for heritage tourists. I have students in two different classes this semester working to create podcasts, while using their efforts on specific sites or events to enhance their understanding the larger historiographical themes of the course (in theory, at least, as I have yet to receive their final essays to learn how that worked).

    I would love to offer what little I can about this project, bearing in mind that my role is not technical in any way, but focused on content generation.

  2. Jon Voss Says:

    This sounds like a great project, and I’m looking forward to hearing more about it in VA and will be happy to share what we’ve learned to the extent that it’s helpful to you. I’ve launched LookBackMaps as an iPhone app that’s now up on the App Store for free. We’ve got some work to do to manage scalability on the iPhone app that accesses all locations, but we’ve created a module-based app that makes it cheap and easy for smaller institutions to release their own apps (much more manageable to have images/audio/video etc bundled with the app rather than pulled from a DB and individual sites). The funnest part of our app is the AR-like feature which overlays historical photos over your camera view–and it sounds like something you’ve got in mind too. There will be more of that kind of development coming out of the team responsible for PhillyHistory.org, as they just got NEH funding to specifically develop AR features for mobile devices around their collection.

  3. dboyer Says:

    Sorry I missed this post until now. I’m the project manager for PhillyHistory.org, a website of 80,000 historic photographs of Philadelphia that Jon mentioned in his previous comment. We have a mobile app that works on iPhone/Droid. It’s location aware as well so people can easily view the historic photos around their location. We should begin work on adding augmented reality features to the site in the next few months.

    I’d be happy to talk to you about mobile tech and share stories about our project. WolfWalk sounds interesting and I’d love to learn more!

  4. John Murray Says:

    One project I’ve been a part of is TerpNav — an open source mapping program that unites OpenLayers with a custom-rendered backend that we host on our servers generated by Mapnik. (map.umd.edu). We’re investigating more mobile applications though — so very interested in storing map data on the device.

  5. wayne.graham Says:

    I’ve been playing around with different ways to interact with maps on mobile devices as well. We’ve had some success on mobile devises with WMS calls from Geoserver for our historic raster maps and vector maps with just OpenLayers. I’ve had some luck with a monkey-patched version of OpenLayers that responds to touch gestures on iPhone/iPad and Android.

    multitouchmap.heroku.com

Search

  • Recent Comments

    THATCampers can use the blog and comments to talk about session ideas. Follow along by subscribing to the comments feed and to the blog feed!

    • thuyanh: A friend and I have actually made a video response that defends the “dumbest generation” and we...
    • Steven Hayes: Hi, just read your “project retrain” description as part of my background reading for...
    • Peter: Just curious: Is there a version of the National Register Nomination Form in some kind of database format,...
    • Samuel Teshale Derbe: This is excactly what I have been looking for.I have been recently invited to contribute to a...
    • plr articles: Just added more knowledge to my “library-head” :D
  • Twitter

    Here's what others are saying about THATCamp on Twitter

    • No items

    All Posts

  • THATCamp Prime Collaborative Documents
  • THATCamp Prime evaluation
  • New session: The THATCamp Movement
  • THATCamp on Flickr
  • Visualizing Subjectivity
  • More Twitter Visualizations
  • Remixing Academia
  • What THATCampers have been tweeting about (pre-camp)
  • Late to the Stage: Performing Queries
  • Humanist Readable Documentation
  • Zen Scavenger Hunt
  • The (in)adequacies of markup
  • One Week, One Book: Hacking the Academy
  • Analogizing the Sciences
  • Digital Literacy for the Dumbest Generation
  • Teaching Students Transferable Skills
  • Modest Proposals from a Digital Novice
  • Creative data visualizations
  • OpenStreetMap for Mapping of Historical Sites
  • soft circuits
  • Mostly Hack…
  • A Contextual Engagement
  • ARGs, Archives, and Digital Scholarship
  • Playing With the Past: Pick One of Three
  • DH centers as hackerspaces
  • All Courseware Sucks
  • HTML5
  • Dude, I Just Colleagued My Dean
  • The Future of Interdisciplinary Digital Cultural Heritage Curriculum (oh yeah, and games as well)
  • Project "Develop Self-Paced Open Access DH Curriculum for Mid-Career Scholars Otherwise Untrained"
  • what have you done for us lately?
  • Digital Storytelling: Balancing Content and Skill
  • Visualizing text: theory and practice
  • Plays Well With Others
  • Citing a geospatial hootenanny
  • Reimagining the National Register Nomination Form
  • documentation: what's in it for us?
  • Sharing the work
  • Digital Humanities Now 2.0 and New Models for Journals
  • Finding a Successor to Paper and Print
  • "Writing Space"
  • From Scratch
  • Cultivating Digital Skills and New Learning Spaces
  • Surveying the Digital Landscape Once Again
  • Building and designing projects for long term preservation
  • Collecting the Digital Story: Omeka and the New Media Narrative
  • Design Patterns for DH Projects
  • Chronicling America: They gave us an API. What do we do now?
  • Social Media and the History Non-Profit
  • THATCamp-in-a-Box
  • Teaching Collaboration
  • Geolocation, Archives, and Emulators (not all at once)
  • The Sound of Drafting
  • The Schlegel Blitz ("Only connect…")
  • Text Mining Scarce Sources
  • Applying open source methodology and economics to academia
  • What I'd Most Like to Do or Discuss
  • Hacking ethics for edupunks
  • Mobile technology and the humanities
  • Audiences and Arguments for Digital History
  • Open Peer Review
  • Who Wants To Be A Hacker?
  • Please advise
  • Greetings from the new Regional THATCamp Coordinator!
  • 2010 Applications Open!