I’m embedding this Joe Russo’s Almost Dead show (which comes very highly recommended from musicologist Jake Cohen) into my blog here to illustrate how “badging out” works as an open strategy for distributing content socially:
Because user experience, we are doing some research, including a survey. If you work with social interfaces, apps, websites, or experiences, please consider taking this survey to help inform the next edition of the book. Thanks!
When Apple brought the touch screen and the tablet together they kicked off a new revolution, one that moves us all one step closer to direct manipulation of the digital world at our hands.
As a writer, I suppose I have naturally gravitated toward the realm of writing and editing, where we’re still following “word processing” conventions developed in the late jurassic era, and a model of interaction with screen objects sometimes referred to as WIMP (windows, insertion point, mouse, pointer), revolutionary when first developed at PARC but increasingly feeling like a remote control apparatus in a world of immediate and direct manipulation using our senses and our hands.
So for the last couple of years I’ve been working at a startup called CloudOn where we make a document editor for mobile people that lets you store your stuff in the cloud, get to it from anywhere, and work on the devices you prefer.
We’ve learned a huge amount from the product we launched in 2012, a few months before I joined, and soon we’ll be rolling out an updated version of CloudOn that I honestly believe will change your mind about what is possible on an iPad. You’ll start to wonder why you can’t just reach out and touch, move, rotate, and position everything you work with.
So where am I writing from? Anywhere I want.
Our launch is coming up soon, so I wanted to share a sneak peek with friends, family, and well wishers. This little video gives a preview of what we’ve come up with.
You can watch it here or drop by our signup page to be notified when it’s available.
Still playing catch-up. I wrote this guest blog post for the Hightail blog about eleven months ago, before some of my pals, um… hightailed it to greener pastures. It’s the clearest statement I’ve made yet about both the “tablet first” and “holistic ubiquitous user experience” approach we’ve been taking at CloudOn, so I am going to reprint the whole thing here in my own space:
As smartphones have taken over the world, many product designers have embraced or experimented with a philosophy called “mobile first”. This approach involves embracing the constraints of small handheld devices to design a core, minimally valuable product that enables the user to accomplish the most important tasks. This mobile interface can then be selectively extended or scaled for traditional desk and laptop (or “desklap” as I like to call them) devices.
At CloudOn, where I’m Director of Product, we make an app that connects to cloud storage providers and enables users to access and edit Microsoft Office files on mobile devices and in web browsers. Our philosophy is a variation of the mobile-first concept that we call “tablet first”. Unlike the vast majority of digital products that started life in a web browser before taking tentative steps into the domain of mobile apps, CloudOn was born on a tablet. We saw an opportunity to take these newfangled tablet devices into the realm of productivity and ran with it.
In truth, our philosophy is more holistic than simply about starting with the tablet first. We approach user experience from a device-agnostic perspective, preferring to think conceptually about the user’s needs and the journey they take to get something done. We aim to understand people’s workflows, to see how and when they communicate with other people, before figuring out where and how we fit in. Only then do we apply our conceptual thinking to real-life devices.
The tablet-first approach fits with our holistic philosophy because tablets are blended devices. They are mobile but they have (relatively) big screens. They have the consumable qualities of a smartphone, but with the productivity potential of a desklap.
We have found that it can be a good idea to do your first device-specific design for the tablet, because solving the user’s problems on an iPad or a Nexus 7 lays a good foundation for extending the experience out across the full spectrum. As Google’s SVP of Ads and Commerce, Sridhar Ramaswamy says about tablet-first design:
“[It] brings into account things like swipe that are quite unique about how you think about an experience. Then if you start from there, then the mobile experience becomes a relatively simple space-constrained version of the design, while the desktop experience nicely generalizes this is what you do with the mouse. But the devil’s in the details.”
Indeed it is. When we first created the smartphone version of CloudOn (our second form factor), some aspects of the translation were easy(ish). Because of our initial attention to the overall concept design, most of our product flows crossed over well. But interpreting a holistic experience across multiple devices forced us to think more carefully about which aspects needed to be common to all devices and which were more tuned to a specific form factor.
For example, we decided to optimize the phone app for reading or consuming content, rather than working on it. After all, who wants to fiddle around with an Excel spreadsheet on their phone’s 3.3-inch display? Well, it turns out quite a lot of people do.
Once we launched the phone version of the CloudOn app, we were surprised to find many users were editing spreadsheets, slideshows and documents on those tiny screens. Sure, it’s nobody’s idea of the perfect experience, but sometimes it’s the only tool available and as photographers like to say: the best camera is the one you have on you. This century’s major shift in how we work means we’re all more willing to engage in tasks when we’re in a cafÃ©, at the airport, watching TV or in a meeting.
The tablet will have an increasingly big part to play in this. When the iPad was released it was initially regarded as a consumer device, best suited for browsing content and not particularly useful for creative or generative work. Indeed most reports show peak tablet use in evenings and on weekends. At CloudOn, however, our analytics show usage peaks that follow the contours of the workday and the workweek. Clearly people are using our app on their tablets as one of their main work devices and not just as a convenient option for the train or sofa.
Right now, tablet productivity is different to sitting in front of your desklap. For me, it’s when I’m in a meeting room or sitting on a couch. I’m working but often not as intently: maybe reviewing or making small edits to an existing doc. But, my tablet is definitely not just for consuming and with tools like CloudOn and Hightail I have the means to do a lot of the same type of work that I would do on my laptop.
Even these usage patterns may be changing. On average, 55% of CloudOn users just read files without changing them, 35% edit files and 10% create new files. These figures hold for both tablet and smartphone users, even though we expected a smaller percentage of users to edit on the latter devices. While the vast majority of our users are working in a business context, one exception to this pattern is our student users, who often use tablets to create and work on longer projects.
It’s unclear yet if this is because students are true digital natives – a new generation with new work habits who are comfortable creating on touchscreen devices. Or perhaps their usage is more circumstantial: students are naturally more mobile, as they don’t have a set desk but move from class to class. Either way, this is a sign that the next cohort to hit the workforce might view tablets as one of their primary productivity devices.
Designing for tablet-first is therefore not just a good way to create a product for a medium-scale device before extending to other platforms. It also means you’re designing with the future in mind and creating a user experience with a longer lifespan.
Of course, technology changes so fast that it’s often hard to predict what the next groundbreaking new device will be or even how people will change how they use existing tools. By starting with a holistic approach to creating elegant solutions to real user problems, regardless of device, you’re prepared for whatever digital revolution lies ahead.
Nearly a year ago, on my birthday, my contribution to the “why I…” series at the Code for America went live. I’m reprinting it here to keep a copy in my own storehouse, and because I am mentoring for the accelerator again this year:
I’m mentoring for America because I believe that a small-team startup-style approach to civic engagement can vastly improve the tools we collectively build for governing ourselves. From the day I first heard Jen Pahlka was launching this venture (can I call it that?) I’ve loved the idea and wished for ways to contribute. When the Accelerator program came along, I was given the opportunity to lend my background in user experience and product design to folks trying to refine how government and community work together.
Over the course of several afternoon or day-long mentoring sessions, I was delighted by the wide variety of solutions to nagging problems being demonstrated, tested, or turned into sustainable businesses.
In the past couple of years the value of design and user experience as a key ingredient to making great products â€” the type that differentiate themselves from their competitors â€” has become fairly well accepted in the Bay Area tech world. There are rockstar designer founders lurking around in thick glasses, and networks for matchmaking great UX and design talents with startup co-founders cropping up. Instead of being employee no. 39, the UX or design lead is often employee number 4, 3, or 2.
Product management has begun opening up to the value of the user experience designers often working under their own roof and a growing number of user experience designers have taken on product roles in their organizations. This has been my own recent path, as I took on product director roles first at AIM and more recently at CloudOn, a mobile productivity startup, where I’ve been learning a lot about “tablet first” design and holistic cross-device user experiences.
Sitting down on a couch looking at live sites, prototypes, and drawings of future interfaces, and talking to these founders about their goals, their methods, their secret sauce, and so on, I made suggestions about screen layouts, language of instructions, complexity, larger user flows and scenarios, of course, my real goal was to encourage them to spend a bit more time gut-checking their ideas with real people, putting themselves in other people’s shoes, and sketching more variations of their ideas.
Some folks just wanted to learn more about how a technology can be made into a product. Others were interested in engagement and on-boarding. Many had challenges around the online / offline interface or capturing and dealing with legacy content formats. There were many other fascinating puzzles.
I didn’t have all the answers. Far from it, but I’d like to think I helped them frame the problems and gave them some ideas and methods for how to solve them: how to come up with possible solutions, test them, and iterate rapidly. If any of them found my advice at all useful, I’ve gotten my reward.
I was super-pleased to be asked to mentor the accelerator companies this year again, and I’m enjoying working with the civic startups this year.
Note: I may have missed it at the time because the piece is credited to a different Christian at the moment. (UPDATE: Fixed! Thanks, Dharmishta!)
my old enterzone pal Martha Conway has been tweeting things lately with hashtags like #writeprompt and #10minprompt and #amwriting.
i love this! i want to play, so i just tweeted “The one thing I do know is…”