Recently in R685 we did a week on mobile learning, or m-learning. As a companion activity to that week, I decided I would limit myself to participating in class only via my smartphone. This is the first of a series of blog posts I’ll be doing on my experiences that week; this post will focus on my motivations for choosing to do so, and then the device I used. You can view the entirety of the series here. Additionally, since time in the semester is running out, I’ll be skipping the rest of my weekly topical reflections, with the exception of discussing my m-learning experiment and one final post reflecting on the blogging I did this semester. I also plan on sharing the reflection I wrote on my final project.
I understand from my class readings this week that in a lot of areas, mobile phones are people’s only access to the internet. Even though the digital divide is shrinking, the numbers of people worldwide who do not own a desktop or notebook computer is staggering. Given that I come from a relatively privileged background, and have had at least one computer at all times for the last decade, I couldn’t imagine what it would be like to be constrained by relatively inefficient technology.
Dr. Bonk’s class is set up very well for the online learning format. I have had no real difficulty accessing the readings for a given week, or participating in class synchronous sessions, or the discussions on the class forums in Oncourse either. I had already been participating in a less-constrained form of m-learning all semester; my job provides me with a laptop, a recent-model Macbook Pro, which I used to access the entirety of the class this semester up until I began using my smartphone. I believed that this pre-optimized setup would make my objective easier to accomplish (whereas it would not have been nearly as easy to do an entire week’s worth of homework for my Web Programming class using a smartphone). This meant that I had a set of conditions that were ideal to fostering the success of my experiment, rather than ones that would frustrate me on the first day of attempting it.
Additionally driving my decision to try this experiment was the knowledge that we would not be having a synchronous session in Adobe Connect that week. Though I have a lot of faith in my little smartphone, I shudder to even think about what a nightmare getting Connect to work would be – if it could, in fact, be gotten to work at all. This meant that my restrictions would not prevent me from participating in any major way in the class (something I found important because my grades are important to me; I didn’t want to harm myself with this experiment).
Also motivating my decision to give the experiment a shot was the fact that I have just recently upgraded my cell phone. Previously I was using the Apple iPhone 3G, which was sufficient as a smartphone, but I have serious doubts as to its ability to handle the sorts of use cases I would be exploring.
The phone to which I upgraded is a Samsung Galaxy S, known in the United States and Canada as the Captivate. You can get a full breakdown of the device’s specs here, but I’ll give you the run-down on some of the basics.
First, this thing is huge. You could just about fit the entire iPhone into the display area on the Captivate. Second, it’s running on the popular Android firmware by Google. Third, it’s about twice as powerful as the first computer I ever got, in 2001, which came with Windows XP. The Captivate boasts 512MB of RAM, an internal 16GB SD card, and an expansion slot that can handle up to an additional 32GB, in micro-SD format. Its processor is one of the more modern mobile processors, the ARM Cortex Hummingbird, at a speed of 1000 mHz. I was using the most recent version of Android, 2.2 (colloquially known as FroYo), though I’m pretty sure anyone using a Captivate with the previous version, 2.1, would be able to duplicate my results using this particular class.
Furthermore, this thing is even more usable than I ever found the iPhone to be. Where the iPhone still reminds me more of a PDA than it does a computer with a touch-screen interface, there’s no mistaking the Captivate for anything less than a full, mobile computer. Having had it for all of maybe two weeks before we got to m-learning, I had already found myself surprised over and over again by the Captivate’s capabilities; it was this fact that convinced me that success with my experiment was possible.
And so, I pushed on. Look for blog posts later talking about the software I used and the experience I had.