Category: mobile

Mobile-First Journalism : a Top Ten list

This discussion originated at Poynter’s Mobile First workshop last week and is slightly edited from suggestions gathered on the Mobile Journalism group on Facebook. And yes, there are 12 items and probably a few good ones still left to be added:

  1. Your website is responsively designed with smartphones as the core case.
  2. Your executive editor/general manager/publisher uses your mobile site daily.
  3. Staffers have smartphones and both consume and report news with them.
  4. Special project planning starts with a discussion of mobile elements and presentation.
  5. Mobile performance is included in staff goals.
  6. You have newsroom and business leaders with ‘mobile’ in their title.
  7. When the mobile site/app breaks at 2 a.m. phone calls are made to get it fixed.
  8. Your advertising team is selling mobile-first and ads are targeted to devices and locations.
  9. Your CMS has multiple content channels allowing different headlines and summary text (etc.) on mobile and web.
  10. You have an API that allows ‘data first’ development for current and future devices and partners.
  11. “User Experience” and “User Centered Design” are key concepts in your product development process.
  12. Fifty percent of your traffic comes via touchscreen devices.

Using Google Forms on a smartphone

I did a fair amount of Google-ing on this looking for a simple answer – without much luck.

So, in case this comes in handy here is a simple-ish way to use Google Spreadsheet forms on an iPhone for data entry in the field.

My current project is an ethnographic survey of news habits among commuters – with a focus on mobile devices. I have been gathering anecdotal info for a while on the commuter rail and T.

For class, I needed to formalize the data a bit, and wanted to use Google Spreadsheets. There may be better survey solutions out there that are mobile-friendly, but I have a lot of other stuff in Google Docs, so there you go.

Creating a form to gather Google Spreadsheet data is dead simple. And (previously unknown to me) you can break a survey form into multiple pages and contextually customize questions. That is GREAT for mobile use as it reduces the amount of content on a single page, and eliminates non-applicable queries on-the-fly.

Unfortunately Google Forms does not include any mobile-specific or responsive themes. It does work on a smartphone, but only with some significant pinch-zooming. This is especially a pain when using tiny radio buttons or check boxes.

The solution I arrived at is pretty simple, especially if you have access to a web server.

1. Set the theme for your form to “Plain” in Google Docs.

2. Limit your survey pages to one question each with 4 – 5 answers – eliminating the need to scroll to find the continue/submit button.

3. Use page breaks, and multiple choice options (which allow a redirect to specific pages based on prior answers) to customize the order and questions offered.

4. Embed the survey code from Google into a web page you control. Doing this on your own server is preferable as you want a completely blank page aside from the embed code.

Screengrab of a simple mobile survey page5. Drop a meta tag in the <head> to set a viewport. Something like: <meta name=”viewport” content=”width=320, initial-scale=.9″> I have not touched HTML much recently but viewport is not tough to understand and works on Android as well.

6. Set the iFrame width to 320 (or etc for your phone) and the trim the height to make it as short as possible, without losing the bottom of any page.

7. Test and adjust the viewport width or scale as appropriate.

8. Keep in mind this approach is not the most elegant use of a viewport, but my goal was iPhone specific so I was satisfied to hard-code these settings into the page.

9. Once you finish tweaking, you should end up with a decent looking mobile form, as pictured here, without the need to pinch-zoom every page constantly.

10. Suggest to Google that mobile-friendly themes would be great.

Seven mobile trends to watch in 2012

Arguing Apple vs Android and apps vs web is fun, but so 2011. So, thinking about 2012, a handful of mobile trends are worth tracking:

  1. Transactions/Authentication (NFC , Square etc.)
  2. External sensors and connected devices (Bluetooth 4.0/Internet of Things)
  3. Voice (Siri vs Google)
  4. Presence (Moving beyond check-ins)
  5. Home Hub (Airplay, HDMI outputs, home controls)
  6. Connected cars (3G-enabled, streaming Internet replacing AM/FM etc.)
  7. 4G (Speed changes behavior)

I am collecting links on these and other mobile topics on Delicious.

Living in the cloud

I did not realize how much I loved the cloud until this week.

This is my last week @Poynter, and I spent part of the day clearing off my work MacBook Pro to hand in.

The process is typically a major pain. Words docs, spreadsheets, presentations, photos, music, and email all need to be found and saved onto external hard drives or thumb drives and reconstructed on a new machine. I still have Zip disks, CD-ROMs, DVDs and even a Syquest disk laying around from previous migrations.

But this time: painless.

Most of my working documents are in DropBox. All of my email and calendars (personal and work) are stored in various Google Apps accounts. The majority of my news reading is done via RSS feeds stored in Google Reader. Firefox is syncing my bookmarks (somewhere) but I use Delicious and Instapaper in most cases anyway. All of my notes and to-dos are in Evernote. Almost every photo I have taken in the past year is still on my iPhone – a few are on Facebook, Flickr and Instagram. When traveling I watch movies on Netflix and TV via Slingbox. And, Twitter is what it is.

In fact music is the only real cloud hold-out for the moment, though I have that backed-up to Amazon’s Cloud Drive and an external drive at home just in case.

Scanning the laptop – the only files actually saved locally are applications and random downloads that could be deleted. The entire process took about 20 minutes, and I can walk away fairly confident I am not leaving behind anything I am going to need later.

And – bonus points – most of the apps I use on the laptop have iPhone/iPad equivalents. So despite being without a computer for the next few days I am barely going to notice. Actually, I would be much more distressed if I lost my phone for the weekend.

Sure Amazon’s cloud crashed for three days last week. So far – the risk is worth it.

Wired, we love it when you make up words. But stop!

My copy of Wired arrived in the mail today.

Page 040 Jargon Watch:

“Cybercase v. To scope out a joint using geotagged data written into digital photos posted online. By browsing images of luxury goods on sites like Flickr or craigslist, thieves can often glean the exact location of the loot and then plot a targeted break-in.”

OK – I know Wired takes credit for popularizing terms like crowdsourcing and Great Firewall of China (page 30, same issue) but c’mon.

First of all, this meme dates all the way back to May of this year when two researchers at the International Computer Science Institute and Lawrence Berkeley National Laboratory in Berkeley, Calif. created it. The pair, Gerald Friedland and Robin Sommer, wrote a paper titled: Cybercasing the Joint: On the Privacy Implications of Geo‐Tagging and presented it at the  Fifth USENIX Workshop on Hot Topics in Security (HotSec ’10) at the 19th USENIX Security Symposium in Washington, D.C.

See how boring all of that sounds in context?

The topic got a bit of a run after the paper was published. ReadWriteWeb and The Atlantic, probably among others. And yet, a Google search for cybercasing turns up fewer than five relevant references in the top 100 results. And those are all to the paper or to the RWW or Atlantic coverage. This is a word in search of a use case to apply itself to.

I really only noticed the term in the magazine today because a few weeks ago we had a potential “cybercase” which took place in a next door town. Police reported that some thieves had broken into homes based on people’s Facebook updates. It took about 2.5 seconds for that to go viral. Unfortunately for the sake of a good story, as Jeff Jarvis discovered, the thieves and the victims were known to each other – that’s why they could read their Facebook updates in the first place.

Of interest to me, the actual local paper (my former employer) reported, but never played up the Facebook angle possibly by luck, or just plain good judgment.

But, getting back to Wired: I love it when they “discover” words and it is always worth at least a chuckle, if not some further thought. But please, this is obviously a fake trend story so next time let’s try to couch the definition a bit more:

“Cybercase v. The potential threat, though never actually spotted in the wild, that really intelligent thieves (who apparently prefer crime to a career in IT) might spend their time scoping out a joint using geotagged data written into digital photos posted online, instead of just driving around to the nice parts of town and looking for homes with a week’s worth of mail on the front step. By browsing images of luxury goods on sites like Flickr or craigslist, thieves can often glean the exact location of the loot and then plot a targeted break-in, that is assuming the images were taken in your current home, and the item you put on craigslist did not sell that very afternoon. By the way, if the images were in fact taken at home, you might want to warn your neighbors since the GPS tags are probably going to drop the crooks in their swimming pool.”