Leaving A Data Legacy

I would love to know how my grandparents lived their lives half a century ago. Now that all but one have passed, I’m left with only a few pictures and stories. While there may be a Big Fish fantasy charm to the finite amount of information I have, my curiosity endures.

FoursquareI finally adopted Foursquare in January and checked in nearly a hundred times since. To this day, I struggle to find direct utility in the service (beyond specials, which I have never successfully used). That said, I am a data nut. I appreciate the value of collecting information on my life, whether I do anything with it or not. I’m too lazy to keep a journal, so social and location services help a lot. Despite the fact that my data may be used to serve the gains of others, I (perhaps naively) trust that these services will evolve to capture and interpret the nodes of my life back to me and all who follow.

I am of the camp that sees big data not as a violation of personal privacy, but as a path to building a data legacy. I don’t presume to become wildly famous and expect the world to care what I ate for breakfast yesterday. No, I mean to say that I want to leave slices of history for my children and children’s children to better understand me and the times I live in. Does anybody really care that I had Pad Thai for lunch yesterday? Fuck no. But the next generation might appreciate a rich data set on American dining habits and dietary evolution. My grandchildren might appreciate that Pad Thai is one of my favorite dishes.

Like donating your body to science, I want to donate the computed history of my life to the next generation of sociologists, historians and nostalgics. I want my grandchildren to have access to anything they could possibly want to know about me and learn from my mistakes. We all have an opportunity like never before to contribute to the nuance of our generation’s history books.

So, in spite of all this privacy hooplah, I will continue to check in and contribute to big data through applications and organizations that lend to a long shelf life and value for greater societal context.

Advertisements

Mobile Should Not Port Web (Or Vice Versa)

Cramming the web experience into a smartphone is naïve. Any person with a shred of user interface appreciation should understand that we interact with desktop or laptop computers in very different ways than our phones or tablets. The devices are not directly interchangeable. It amazes me how many designers and companies forget it. Many hop on the mobile bandwagon and try to squeeze every feature into a claustrophobic mess. What’s the point?

I loath Facebook’s latest mobile app. It overwhelms the user with every possible feature from the suite (a collection of nonsense that makes it the slowest and most cumbersome app on my Galaxy Nexus). I do not need access to my pages or Facebook apps; I do not want to curate user groups or manage my friend list. Even events should live outside of the app – preferably in my calendar where they belong. I just need my messages, wall and news feed while I’m on the go. That’s it. Save my processing for something else.

While by no means an elegant app, Wells Fargo keeps things focused by opening with only two options – mobile banking or find an ATM. No offers for loans. No investing or insurance. Just simple tools to manage my money on the go. That’s it. Straightforward, simple and relevant.

On the flip, many mobile-first applications forget that they can approach their mission from a completely different angle via the browser. Instagram, with the mission to “share your life with friends through a series of pictures,” has an irrefutable opportunity to expand photo consumption onto a larger palette. Right now, their website is an embarrassing static splash page. Imagine a stunning and immersive fullscreen browser magazine ripe with friends’ photos, updating live as their world evolves around you. A powerful experience you will never have on a 3.5 inch screen.

Mobile and web can help you approach your core mission from two different angles. The mobile experience should feel immediate, focused, actionable and succinct. The web experience should feel expansive, explorable, comprehensive and open.

Before you port your experience to one device or another, first ask yourself two (rather obvious) questions: (1) What tools do people absolutely need on their phones versus their computers and (2) how would user interaction differ with the same tools on different devices?

Mobile could let you explore all the comprehensive offerings of a cross-platform application if you want to, but the unique-to-mobile (U2M) experience should come first. The Foursquare check-in is a perfect example of a U2M tool that adds to the unique-to-browser (U2B) experience of exploring a map of your data.

More platforms should debate U2M versus U2B and not try to cram a square block into a round hole.