Showing posts with label apps. Show all posts
Showing posts with label apps. Show all posts

Friday, July 12, 2013

Mobytes Instructional Design App

English: This is Juniper Hall at Humboldt Stat...
Juniper Hall at Humboldt State University.
(Photo credit: Wikipedia)
One of our technologically ever-vigilant instructional designers here at Humboldt State (Kim Vincent-Layton) shared an interesting Android app with us the other day - Mobytes Instructional Design App. The app is a handy collection of articles and templates on instructional design. What is a "mobyte"? A mobyte is a "just-in-time chunk of learning designed for just-enough knowledge to learn or apply while performing a task. It can be used for learning from scratch, refreshing and updating knowledge while on the move." I like this app because it covers, at a basic level, the current understanding and definition of instructional design that any student of education would find in a instructional design class. I would like to share this app with administrators and teachers to help promote a deeper understanding of instructional design and its possibilities. The author, Madhuri Dubey, has distilled five topics into the app:
  • Instructional Design (ID) basics 
  • Evolution and application 
  • Learning theory and styles 
  • Instructional theory 
  • Getting started with ID 
This reference would be useful for instructional design teams to all get on the same page as well as for instructors who would find it useful for a better understanding how teaching and learning work. It covers Gagne, ADDIE, Clark, Merrill, Bloom's and the usual suspects.

If you are not an Android phone person, much of the information here is available on Madhuri Dubey's blog.
Enhanced by Zemanta

Friday, June 03, 2011

Google Music: Bask in the market socialist sunshine!

Ludwig van Beethoven in 1820Image via WikipediaAs you are probably aware, I am a big fan of Google. I have been using and writing about their products from very early on. In fact, this blog was acquired by Google way back when. They are a real conundrum for me at times; they represent the best of what I think companies should be and yet they are still corporate; they are not a foundation or an open source organization, but they have open source projects, products, and contribute to the open source community. Tonight I am loading Google Music on my computer. Interestingly enough, Google's Music Manager relies on about 26 open source projects to do what it does. I recommend reading the licensing documentation because that will really tell you what you can expect from this new tool/service. What Google Music is meant to do is to upload all of your music from all of your devices and host them in one spot which you can then access from any device (phone, computer, etc.). And yes, this means iTunes. I am not sure how Apple is going to take this. This means the iTunes at my work PC, my iTunes on my home computer can now be combined in one service. It all goes from the locked down silos at Apple into the socialist free market sunshine of the cloud. How does this effect the digital rights? If I bought something from Apple to be played in an Apple platform did I also buy the right to reproduce that where ever I want? I am really curious to know how this is going to play out legally.

For now, Google's Music Manager is churning through my 21 days of music and has uploaded most of Beethoven and rejected nearly 350 songs. I am not sure what that is about yet, but I will post updates to my installation and cloudification of my music on Twitter - I am at geoffcain in the Twittersphere. If you have already installed Google Music and are using it, post your insights to the comments below or email me - I am interested to know how it worked for you too.

Enhanced by Zemanta