Posts tagged: user experience

Why iCloud Will be as Important as the iPod

By Adam Richardson

Apple’s World Wide Developers Conference keynote last week will be
remembered for two things: the bloodbath of disrupted developers and
apps it left in its wake, and that it was as important for cloud
services as the iPod was for digital music, and that the iPhone was for
smartphones.

The Developer Bloodbath

Despite the many cheers from the crowd of developers at the keynote, I
reckon there were several hundred third party developers and apps
collectively put on notice (and maybe put out of business) by the
various announcements. As the NY Times wryly put it, “How do you know if
you’ve created a really great, useful iPhone app? Apple tries to put
you out of business.” (The Times provides a handy list of apps now scrambling for a second act.)

In truth, quite a few of the things that Apple announced – such as a
basic to-do list app, and ways of storing web articles offline for later
reading – have become such fundamental needs for so many people that
they deserved to be part of the core OS. Unfortunately they are also the
bread and butter of many niches developers who saw the same need and
leapt to fill it in the intervening years. They will have to rethink and
improve what they do, and many of them will I’m sure.

Such is life in the shadow of an ecosystem behemoth. Apple giveth
(App Store to give independent developers more visibility and access)
and Apple taketh away (obviating the need for those apps in the first
place).

Apple has been pretty consistent in adopting good ideas from third
parties into its core offerings. Perhaps most famously, Apple introduced
the Dashboard feature (a precursor to the iconized app view on the
iPhone), to loud complaints of it ripping off a third party developer, Konfabulator who had created something very similar.

As problematic as this can be, it’s all part of Apple’s plan. Chetan Sharma put it succinctly: “Apple’s goal is to commoditize the software, Microsoft’s goal is to commoditize the hardware, Google – both”

Apple has high tolerance for making software free, even if it makes
life painful for its developers, because it makes almost all its profit
on hardware. For the time being at least, Apple has enough strength
and/or momentum relative to Google, Microsoft, media companies and
service providers that it can thrive with this approach.

The Mainstreaming of Cloud Services

The announcement of iCloud was met with both enthusiasm and incredulity.

Apple has been firing on all cylinders for years with hardware and
software, but has consistently stumbled with services, whether it be the
expensive and lackluster MobileMe (the launch of which even Jobs had to
admit at the keynote was “not our finest hour”), or the weak reception
to its music “social networking” service Ping. (This isn’t a new
phenomenon – anyone remember eWorld?) The only service area where Apple has really sung is with its retail stores.

With iCloud, Apple is cinching up the ecosystem it has painstakingly
built up, cinching it so tight that it will become increasingly
difficult for others – even ones as big as Google – to crack open.

MobileMe was an expensive, under-performing sideshow, but iCloud aims
to reach deep into all the other Apple devices and make them all work
together better. What was announced on Monday is surely only a hint of
what lies ahead in the next 18 months for iCloud, iOS, and OS X all
finally getting in sync.

Ironically, iCloud aims to improve on what was arguably the worst
part of MobileMe – iDisk, a basic cloud storage feature. Given Jobs’
obvious frustrations with MobileMe, I can’t believe he would let yet
another half-baked attempt out the door, especially not one that is now a
major strategic piece of the puzzle. Based on the massive data center Apple has invested in, they’re not joking around.

Since the iPad launched, its lack of a file system has meant it’s not
a true laptop replacement. One of the brilliant ideas about Dropbox is
that it essentially puts the file system in the cloud and moves it off
the device entirely. iCloud apparently opens the door for the same
thing, and with even superior integration. Today with near ubiquitous
broadband and 4G/LTE networks starting to roll out that offer home
broadband speeds while mobile, this suddenly becomes a workable
solution. (Bandwidth caps, tiered pricing, disappearance of
all-you-can-eat data plans? Yes, there are flies in the ointment, but
the longterm trend is clear.)

Linking Cloud, Apps, Devices, and OS’s

Consider two things that were discussed separately in the keynote:
journaling in the next rev of the OS, Lion (which means no more saving -
a file is continuously saved as it’s worked on), and continuous cloud
syncing. Voila – you have your most up-to-the-second work constantly
saved to the cloud, and made available on every other device.

My feeling is that iCloud will prove to be similar to IBM launching
its PC in 1983. Prior to that point, the PC market was highly fragmented
and dominated by niche players, and had little mainstream appeal. The
arrival of IBM on the scene gave PCs a stamp of credibility and
stability, and they gained sharply more acceptance. IBM made PC’s “easy”
to get into, made them relevant, and created the archetype which others
would mimic for decades.

Apple pulled off the same feat with mp3 players and smartphones, for
largely the same reasons. So it will be with iCloud. Cloud services are
not new (neither were mp3 players or smartphones), and the fact is that
much of our critical data already lives in the cloud, via various web
apps, service subscriptions, and email. But until now the various
services have been poorly integrated, and offered by startups that many
people don’t feel comfortable handing their data over to, whether for
security or long-term availability/stability reasons.

They haven’t been ready for the mainstream, and iCloud will come to
be seen as the turning point which changes that. For consumers who don’t
yet get the relevance of cloud, the media syncing across devices
provides the carrot to get into the concept.

MG Siegler looks at the different approaches to the cloud
being taken by Apple, Google and Amazon, and notes that “Apple’s belief
is clearly that users will not and should not care how the cloud
actually works.” Exactly. This is what Apple does best – take
complicated things that most people don’t care about, and makes them
easy and understandable for a mainstream audience.

An Event Apart: The Responsive Designer’s Workflow

by LukeW

In his presentation at An Event Apart in Atlanta, GA 2011 Ethan Marcotte talked about applying responsive web design principles and workflows to the redesign of a major newspaper Web site. Here’s my notes from his talk on The Responsive Designer’s Workflow:

  • Storytelling and crafting an object are intertwined. We create objects that can tell our stories whether they are physical journals or a series of tweets.
  • Physical newspapers contain the most important information for a day then their value is lessened over time. And increasingly they have less relevance as nearly half of all American results get their news through a mobile phone or tablet. The industry is trying to catch up through iPad apps, mobile sites, and more. Responsive Web design is another strategy to consider.
  • What makes a design responsive? Three ingredients: flexible grids, flexible images/media, and media queries. But these three elements are just focused on layout. Layout is not design. “Design is putting form and content together.” Design is the means. The process of how we get there. How do we become more responsive designers? This is the start of a conversation.

Working Responsively

  • Ethan recently got to go beyond layout and apply responsive design principles to a lot of the redesign process for the Boston Globe Web site.
  • Creative process is often managed as tasks. Our thinking is often linear. We finish one task before moving on to the next. We have hand-off points where tasks move between different skill sets like visual design and front-end development.
  • But the design process of a responsive site is not done at any one point. How do you convey how a design will adapt itself in a single comp? You can’t. Process needs to change.
  • Our tools are also stuck in the old model of building Web pages. So new forms of sharing and collaboration need to be figured out.
  • To create a responsive site for Boston Globe, there was unified collaborative design and development team.
  • Designers “introduced” a comp, developers asked lots of questions about why the page is designed as it is, especially the big one: how will the content adapt? How will the interface adapt to touch, mouse, keyboard? Don’t need to have final answers to these questions but want to understand the process and the decisions made.
  • The developers also ask a specific question of every element on the page: what value does this provide for users on mobile? This question help force a mobile first approach to design.

Mobile First

  • Why Mobile first: traffic has exploded, new capabilities, and narrow screens force us to focus. In many cases our mobile experiences are focused while our desktop experiences are cluttered. Going mobile first pushes focus everywhere.
  • A question of context: what are the different goals of people on mobile & the desktop. We can be focused when using mobile and focused as well. We should leave the mind reading to the professionals. Context doesn’t necessarily dictate people’s intent.
  • People click the desktop link because they feel they are missing out.
  • When going mobile first you are making a commitment to the content on the page. Everything needs to be there. What is the value of every element on the page? This applies to all device experiences.
  • Content first allows you to determine what needs to be in the design. Mobile can be used as a forcing function for simplifying things on all device experiences.

Prototyping

  • You need to move past comps quickly then prototype like the wind to explore responsive designs.
  • Figure out the proportions of a flexible grid using: target divided by context equals result.
  • Can use Scott Jehl’s responsive images code can serve appropriately sized images to the Web browser by swapping out img src attributes. It defaults to the smallest image. Or you can use img max-width 100% if appropriate.
  • Media queries: first look at the devices you are trying to support. Then identify common breakpoints. Small screens, portrait & landscape, tablets portrait & landscape, and widescreen.
  • Media queries are like conditional comments for CSS. Allow us to serve up different code for different device attributes. Media queries support different break points and define adaptation points.
  • Designing in the browser allows the developers to make recommendations for how things adapt and doesn’t require a design comp for very single resolution point.
  • Web fonts are limited to desktop resolutions due to files sizes and readability concerns
  • Verify your work live on different devices in an interactive design review. How well does the layout adapt? Do individual modules still feel usable? Do any elements need additional design direction? Rinse, repeat, and refine as needed.

Flexible Foundation

  • A flexible foundation is really key for responsive design. A flexible foundation allows you to quickly refine new breakpoints. It also means less code to write. And better adaptability.
  • The mobile Web allows us to revisit the talk of inclusion, progressive enhancement for everyone.
  • A responsive layout meets mobile first. Default to a linear, small screen friendly design. Media queries based on min-width scale up, not down.
  • Media=”only-all” is a test to see if site supports media queries. Can create a reading experience that works on less capable devices.
  • Then use a few lightweight tests. Test to see if you have @media query support or IE. If so, take the basic stylesheet out of your document entirely. You can also adapt based on touch support and Javascript functionality.
  • A designer’s choices are a small limited form of tyranny. The philosophy of a responsive design might not be appropriate for the audience you are supporting. The decision to build a responsive or mobile site is often more about the team’s capabilities and decisions than anything specific to devices.

Elixir Displays System Information for Your Android Phone

THOUGHTS: I think this is appealing to me because I have always been one of the folks that wanted to know ‘roughly’ how things work and tweak them accordingly. 

by Alan Henry

Android: Many people who buy Android phones already know all about the device they choose, but for those that don’t or who forget, Elixir can help. The app will display your Android phone’s system status, internal components, available storage, and more. It’ll even add a widget to the home screen with more information inside.

When you open Elixir it displays current system status, including the battery level, CPU frequency, available and used memory, available and used storage, and more. Drill deeper and you can see serial and model numbers for your Android phone’s components, like the motherboard name or model and type of display.

Elixir also has a few widgets and controls that can come in handy if your phone doesn’t have them already. You can control the volume for individual alerts using the app, so if you want your alarm to ring loud but notifications to ring quietly, Elixir can modify the system settings for you from the one control screen. The app can even toggle your accelerometer on or off, and lock the screen orientation.

You can also add a widget to your home screen with those most often-used controls in it so you can toggle them without having to open the app first. Elixir is completely free, and worth a look if you like total control over your Android device.