This week, we’ll be discussing mobility in your read & response. Briggs’ chapter for the week focuses on the subject, so that’s a good place to start. Even though this is a pretty current text, I’m curious how up-to-date you think he is on the subject – advances in mobile communication seem to be arriving faster and faster, making it more and more difficult to stay current on the subject.
Let’s start by discussing the iPad (or ALL tablet technology, really, but it’s difficult to deny Apple’s current prominence here). The new one – yes, another new one – comes out at the start of March. That means we’ll have had a new iPad drop every spring for three years running (and always, conveniently, during this class). One really current example of today’s trends is this: Smithsonian magazine, the old-and-crustiest of old and crusty magazines, has just come out with its own iPad app. Do you have a tablet? Do you read newspapers, magazines or books on it?
Aside from technology, we’ve got mobile apps to consider. Twitter can certainly be used from a landlocked workstation, but (as we experienced in our scavenger hunt), it really shines in how it lets you instantaneously publish from the field (a few death stories that jumped the gun notwithstanding). Check out this tandem of links from reportr.net: “Why journalists should break news on Twitter” and “What goes into a good tweet.” Useful information? Do you agree? How does it square with Briggs’ perspective and what we’ve discussed in class to date?
Location is another factor in mobile communication. If you haven’t already, give Foursquare a try (and if you have but it’s gone dormant, give it another chance for a few days). We’re still grappling with ways to effectively integrate location into mass communication, and one site I’ve recently been turned on to is Street Fight, a news source for all things hyperlocal (kind of like Mashable but for location-based stuff only). Have a look through.
Finally, here’s a tweet from @GeorgeBray that sums things up perhaps a little uncomfortably: