I HIGHLIGHTED so many passages in this brief, well-focused design argument, it’s almost embarrassing. Read it (it takes about three minutes), and you’ll wear out your virtual highlighter, too:
Material Design is a design language introduced by Google a year ago, and represents the company’s bold attempt at creating a unified user experience across all devices and platforms. It’s marked with bold colours, a liberal but principled use of shadows to indicate UI layers, and smooth animations that provide a pretty pretty user experience on Android (and some Google apps on iOS).
One thing about Material Design, however, has bugged me ever since it was introduced last year: Floating Action Buttons.
FABs are circular buttons that float above the UI and are “used for a promoted action,” according to Google. They act as call to action buttons, meant to represent the single action users perform the most on that particular screen.
And because of the bold visual style of Material Design, FABs are strikingly hard to ignore and stand out?—?and herein lies the problem.
While FABs seem to provide good UX in ideal conditions, in actual practice, widespread adoption of FABs might be detrimental to the overall UX of the app. Here are some reasons why.
AN INSPIRING STORY of content creation, which is also, although this particular tale ends happily, a warning about the hazards of building in someone else’s sandbox.
Stampylongnose? makes wonderful videos about Minecraft? (among other things) and is the first independent content creator in my young daughter’s world. She follows him like you followed your first favorite blogger.
In “1 Million Subscribers Special – From Then To Now,” he shares how he became an independent video producer on the web—how he lost everything when Google arbitrarily pulled the plug—and how the community that loved him, and one great Google admin, fought to restore his work.
“The independent content producer refuses to die.”
A VIRUS spoofing my return email address has apparently been emailing many people. I know this because some of these viral email messages bounce back to my Gmail account as undeliverable. Mistaking these reports for actual messages sent by me, Gmail has decided I’m too active a user, and forbidden me to send any more mail today.
I’m a Google Apps user with a multi-gigabyte Gmail account and I’ve sent less than a dozen actual messages today because I am home sick with a cold. But Gmail doesn’t know that. And Gmail doesn’t care. Because Gmail isn’t real, not even in the David Sleight sense. It’s a set of equations programmed by fallible human beings, and it controls my life and yours.
There is no one to talk to at Google about my service problem because there is no there there. The services I pay for are delivered by robot magic in the cloud. When something goes wrong, it just goes wrong. There’s nobody to track down the virus’s origin and make it stop. There’s nobody to say, “This user hasn’t actually sent these messages.” (I keep marking the returned mails as “spam,” but Google hasn’t caught on, probably because customer service problems aren’t supposed to be reported by inference.)
My friend wears a shirt that says “The Cloud Is A Lie,” but that isn’t quite the truth. More like, the cloud is a customer service problem. One I just found myself on the wrong end of.
Google to customer: Go fuck yourself. In the cloud.
IN EPISODE 63 of Triangulation, Leo Laporte, a gracious and knowledgeable podcaster/broadcaster straight outta Petaluma, CA, interviews Your Humble Narrator about web standards history, responsive web design, content first, the state of standards in a multi-device world, and why communists sometimes make lousy band managers.
HI, [REDACTED]. Thanks for writing to express your concern about my failure to redeem my Google IO promo code. It’s kind of a funny story.
I received a Google IO invitation (copied and pasted below) but didn’t follow up on it because the invitation did not say anything about what Google IO is, who it is for, or why I would want to attend it (if it is an event) or use it (if it is software) or do something else with it (if it is something else).
The Google IO invitation merely gave me complicated directions to sign up for Google IO, no doubt on the assumption that I would gladly attend, download, or sign up for anything that comes from Google, even without knowing what it is; and that, as an unemployed millionaire, I would have plenty of free time to decipher and obey complicated sign-up directions without knowing anything about the product, service, or event.
One of the complexities Google mentions in their invitation letter which fails to explain anything about the product or service they want me to sign up for is that, to qualify for Google IO, I must start a Google+ account. They don’t explain what Google+ is, either, but as it happens, I already have a Google+ account.
My Google+ account is assigned to my Gmail address. But instead of writing to me there, Google wrote to me at my zeldman.com address. My zeldman.com address is actually managed via Gmail, so I should be able to log into my Google+ account whether I am signed in as my Gmail identity or my zeldman.com identity, but Google+ doesn’t work that way. Google+ only works for free Gmail accounts. It does not work for paid corporate accounts like mine. That has always seemed an odd decision to me: if you can only provide services to a subgroup of your users, why not choose the subgroup that pays? But I am not Google.
So Google wrote to my zeldman.com address, which they won’t allow me to associate with my Google+ address, to invite me to start a Google+ account (which I already have) on my zeldman.com account, which they won’t support. And if I do that (which I can’t), and some other complicated stuff, they promise that I will then be able to participate in Google IO, whatever that is.
And now they have written to warn me that my Google IO, whatever it is, will stop being offered if I don’t sign up (which I can’t) right away. And they even convinced you, my friend, to send a personal note ensuring that I don’t miss the opportunity to sign up for their unspecified product or service with the account they don’t support before the unexplained offer is terminated.
While I should be curious about Google IO and what I will miss if I fail to take advantage of the cumbersome offer, what I’m actually far more curious about is how an organization that can’t write an effective direct marketing email message has managed to become one of the most powerful corporations of the 21st century.
We recently sent you an invitation to register for Google I/O 2012 and noticed that you have not redeemed your promo code, which will expire at midnight PDT on March 25.
[ How to register ]
1. Make sure you have a Google+ account as it is required to register. Get Google+ at http://www.google.com/+
2. Visit the registration page at
3. Use Promo Code: [REDACTED]. This code can only be used once.
[ Tips to Ensure Successful Payment With Google Wallet ]
1. Make sure your Google Wallet account is tied to the same Google+ account you use to register.
2. In case your bank declines your purchase through Google Wallet, you may need to call the bank that issued your credit card and let them know that you want to make a large purchase. Some banks may decline large purchases that appear to be out of your normal purchase behavior.
3. If Google Wallet is not available in your country, please email email@example.com to have our support team process your payment.
[ Tips to Ensure Successful Registration With Google+ ]
1. Sign into your Google+ account before you try to redeem your code.
2. To ensure you have created a Google+ account, log into your Google account and go to https://plus.google.com/. If you land on a page asking you “To join, create a public Google profile.” then you don’t yet have a Google+ account and follow the instructions to create one.
3. If you have multiple Google accounts, be sure to sign out of all Google accounts and sign in with only your Google+ enabled account.
4. You can use a personal or company managed Google+ enabled account to complete your registration.
If you have any questions, please email firstname.lastname@example.org.
WHILE VIEWING STATS on TweetMeme, I noticed a banner ad that said, “New York—explore it again like you used to.” Intrigued, I clicked the ad. It took me to the web page shown above. (Click to view full size.) At the top was a message thanking me for subscribing. Ouch! I had not subscribed, I had merely clicked a link. Opt-in subscription without notice or warning is about as dark as a user experience pattern can get and still be legal.
Beneath the notice was an ad for a women’s strip tease class. I don’t think I’m the intended demographic. Facebook would know that. Why doesn’t Google?
The offer had a time limit; the script on the time limit froze my browser, prompting a force-quit and restart.
If “Don’t Be Evil” is still Google’s slogan, I wonder if folks who work there say it with a straight face.
Update! Episode 14 is now available for your listening and viewing pleasure at 5by5.tv.
Josh Williams, founder of Gowalla, is our guest at 1:00 PM ET today, July 29, in Episode 14 of The Big Web Show. Whether you’re a social media user/creator, an entrepreneur, an application developer, an iconist or illustrator, a freelancer with big dreams, an API wizard, a devotee of marketing 2.0, a web designer, a Gowalla fan, or what, you won’t want to miss this episode.
The Big Web Show is taped in front of a live internet audience, and you can be part of it. Join co-host Dan Benjamin and me at 1:00 PM ET today to participate in the live taping of Episode 14.
If you miss the live taping, you can watch the show on our website or via iTunes later tonight.
The Big Web Show (“Everything Web That Matters”) is taped live in front of an internet audience every Thursday at 1:00 PM ET on live.5by5.tv. Edited episodes can be watched afterwards (often within hours of taping) via iTunes (audio feed | video feed) and the web.
THE long-planned inevitable has now been announced. With open-source-licensed web fonts, web font hosting, and add-a-line-to-your-header ease of configuration, Google has joined Typekit, Font Squirrel, Ascender, Font Bureau and others in forever changing the meaning of the phrase, “typography on the web.”
The Google Font Directory lets you browse all the fonts available via the Google Font API. All fonts in the directory are available for use on your website under an open source license and served by Google servers.
Presumably in order to avoid having to pay the child model and secure a release, Google deliberately blurred the Gap Kid model’s face on the giant outdoor Gap Kids poster before uploading this photo (and hundreds of seamlessly interwoven related photos) to Google Maps Street View.
It’s hard to say if the human beings on the street have had their features blurred as well.
Does Google go to this kind of trouble with every poster on every block of every city in the world? They must.
I bet their arms get tired.
Related: Recently, some friends and I have noticed news photos, and TV news video, where people’s faces are perfectly clear, but corporate logos have been deliberately blurred or pixelated. This is the world we live in.
As an experiment in new new media thinking, I recently crowdsourced a new new literature version of Charles Dickens’s musty old old old lit chestnut, Great Expectations—the familiar tale of Pip, Ms Havisham, the convict Magwitch, et al.
Creative excellence and spin-worthy results required a pool of 10,000 people who had never read Great Expectations. Fortunately, I had access to 10,000 recent American college graduates, so that was no problem.
To add a dab of pseudoscience and appeal obliquely to the copyleft crowd, I remixed the new work’s leading literary themes with the top 20 Google search queries, using an algorithm I found in the mens room at Penn Station.
The result was a work of pure modern genius, coming soon to an iPad near you. (Profits from the sale will be used to support Smashing Magazine’s footer and sidebar elements.)
Gone was the fusty old title. Gone were the cobwebbed wedding cake and other dare I say emo images. It was goodbye to outdated characters like Joe the blacksmith and the beautiful Estella, farewell to the love story and the whole careful parallel between that thing and that other thing.
Gone too was the tired old indictment of the Victorian class system, and by implication of all economic and social systems that separate man from his brothers in Christ, yada yada. As more than one of my young test subjects volunteered in a follow-up survey, “Heard it.”
In place of these obsolete narrative elements, the students and the prioritized Google searches created, or dare I say curated, a tale as fresh as today’s algorithmically generated headlines.
The results are summarized in the table below.
Old Great Expectations
New Great Expectations
On Christmas Eve, Pip, an orphan being raised by his sister, encounters the convict Magwitch on the marshes.
The convict compels Pip to steal food from his sister’s table, and a file from her husband the blacksmith’s shop. Pip thereby shares the convict’s guilt and sin—but his kindness warms the convict’s heart.
Guy on girl
Pip’s sister, Mrs. Joe, abuses him. Her husband loves Pip but is unable to protect him or offer him a future beyond blacksmithing.
Girl on girl (multiple entries)
Pip meets Miss Havisham, an old woman abandoned on her wedding day, who sits in her decrepit house, wearing a yellowing wedding gown, her only companion the beautiful and mysterious girl Estella. Pip falls in love with Estella, but Miss Havisham has trained the girl to break men’s hearts.
Guy on guy
Pip visits Miss Havisham until his apprenticeship with Joe the blacksmith begins. Pip hates being a blacksmith and worries that Estella will see him as common.
Two girls, one guy
Mrs Joe suffers a heart attack that leaves her mute. A kind girl named Biddy comes to take care of Mrs Joe. After Mrs Joe’s death, Biddy and Joe will marry. Meanwhile, Pip comes into an unexpected inheritance and moves to London, where he studies with a tutor and lives with his friend Herbert.
Pip believes Miss Havisham is his benefactor and that she intends him to marry Estella, whom he still adores. Day by day, Estella grows more cruel. Pip never tells her of his love for her.
One stormy night, Pip discovers that his benefactor is not Miss Havisham but the convict Magwitch. The news crushes Pip, but he dutifully allows Magwitch to live with him—worrying, all the while, because Magwitch is a wanted man who will be hanged if discovered.
Miss Havisham repents having wasted her life and perverted Estella. She is caught in a fire. Pip heroically saves her but she later dies from her burns. Soon afterwards, Pip and Herbert try to help Magwitch escape, but Magwitch’s old enemy Compeyson—who happens to be the man who abandoned Miss Havisham at the altar—betrays Magwitch to the authorities. Magwitch and Compeyson struggle. Compeyson dies and Magwitch is taken to prison.
Pip now realizes that Magwitch is a decent man and tries to make Magwitch’s last years happy ones. He also discovers that Magwitch is Estella’s father. Magwitch dies in prison shortly before he was to be executed. Pip tells the dying Magwitch of his love for Estella.
Pip becomes ill and is nursed back to health by Joe, whom Pip recognizes as a good man in spite of his lack of education and “class.” Pip goes into business overseas with Herbert. Eventually he returns to England and visits Joe, who has married Biddy. They have a child named Pip. As the book ends, the middle-aged Pip makes one last visit to Miss Havisham’s house, where he discovers an older and wiser Estella. There is the implication that Pip and Estella may finally be together.
The first part of my post of 1 February was not an attack on Flash. It described a way of working with Flash that also supports users who don’t have access to Flash. I’ve followed and advocated that approach for 10 years. It has nothing to do with Apple’s recent decisions and everything to do with making content available to people and search engines.
My point was simply that if you’re an all-Flash shop that never creates a semantic HTML underpinning, it’s time to start creating HTML first—because an ever-larger number of your users are going to be accessing your site via devices that do not support Flash.
That’s not Apple “zealotry.” It’s not Flash hate. It’s a recommendation to my fellow professionals who aren’t already on the accessible, standards-based design train.
THE SECOND PART OF MY POST wasn’t Flash hate. It was a prediction based on the way computing is changing as more people at varying skill levels use computers and the internet, and as the nature of the computer changes.
There will probably always be “expert” computer systems for people like you and me who like to tinker and customize, just as there are still hundreds of thousands of people who hand-code their websites even though there are dozens of dead-simple web content publishing platforms out there these days.
But an increasing number of people will use simpler computers (just as we’ve seen millions of people blog who never wrote a line of HTML).
THE THIRD PART OF MY POST wasn’t Flash hate. It was an observation that Google and Apple, as companies, have more to gain from betting on HTML5 than from pinning their hopes to Adobe. That’s not a deep insight, it’s a statement of the obvious, and making the statement doesn’t equate to hating Adobe or swearing allegiance to Google and Apple—any more than stating that we’re having a cold winter makes me Al Gore’s best friend.
(Although I like Gore, don’t get me wrong. I also like Apple, Google, and Adobe. My admiration for these companies, however, does not impede my ability to make observations about them.)
THE THIRD PART OF MY POST ALSO WASN’T a blind assertion that HTML5, with VIDEO and CANVAS, is ready to replace Flash today, or more adept than Flash, or more accessible than Flash. Flash is currently more capable and it is far more accessible than CANVAS.
We have previously commented on HTML5’s strengths and weaknesses (Exhibit A, Exhibit B, Exhibit C) and are about to publish a book about HTML5 for web designers. HTML5 is rich with potential; Flash is rich with capability and can be made highly accessible.
That it is unstable on Mac and Linux is one reason Apple chose not to include it in its devices; that this omission will change the way some developers create web content is certain. If the first thing it does is encourage them to develop semantic HTML first, that’s a win for everyone who uses the web.
Thousands of … filmmakers and writers around the country are operating with the same loose standards, racing to produce the 4,000 videos and articles that Demand Media publishes every day. The company’s ambitions are so enormous as to be almost surreal: to predict any question anyone might ask and generate an answer that will show up at the top of Google’s search results. To get there, Demand is using an army of [impoverished filmmakers and writers] to feverishly crank out articles and videos. They shoot slapdash instructional videos with titles like “How To Draw a Greek Helmet” and “Dog Whistle Training Techniques.” They write guides about lunch meat safety and nonprofit administration. They pump out an endless stream of bulleted lists and tutorials about the most esoteric of subjects.
When Apple chose KHTML rather than Mozilla Gecko as the basis for its Safari browser, some of us in the web standards community scratched our heads. Sure, KHTML, the rendering engine in Konqueror, was open-source and standards-compliant. But, at the time, Gecko’s standards support was more advanced, and Gecko-based Mozilla, Camino, and even Netscape 6 felt more like browsers than Konqueror. Gecko browsers had the features, the comparative maturity, and the support of the standards community. Apple’s adoption of KHTML, and creation of a forked version called Webkit, seemed puzzling and wrong.
Yet, thanks largely to the success of the iPhone, Webkit (Apple’s open source version of KHTML) in the form of Safari, has been a surprising force for good on the web, raising people’s expectations about what a web browser can and should do, and what a web page should look like. Had Apple chosen Gecko, they might not have been able to so powerfully influence mainstream consumer opinion, because the fully formed, distinctly mature Gecko brand and experience could easily have overshadowed and constrained Apple’s contribution. (Not to mention, tolerating external constraint is not a game Apple plays.)
Just how has mobile Safari, a relative latecomer to the world of standards-based browsing, been able to make a difference, and what difference has it made?
The platform paradox
Firefox and Opera were wonderful before any Webkit-based browser reached maturity, but Firefox and Opera were and are non-mainstream tastes. Most people use Windows without thinking much about it, and most Windows users open the browser that comes with their operating system, again without too much thought. This doesn’t make them dumb and us smart. We are interaction designers; they are not.
Thus, the paradox: even though Firefox and Opera offered powerfully compelling visions of what could be accomplished with web standards back when IE6 offered a comparatively poor experience, Firefox and Opera, not unlike Linux and Mac OS, were platforms for the converted. If you knew enough to want Firefox and Opera, those browsers delivered features and experience that confirmed the wisdom of your choice. If you didn’t know to want them, you didn’t realize you were missing anything, because folks reading this page sweated like Egyptian pyramid builders to make sure you had a good experience despite your browser’s flaws.
The power to convert
Firefox and Opera are great browsers that have greatly advanced the cause of web standards, but because they are choices in a space where most people don’t make choices, their power to convert is necessarily somewhat truncated. The millions mostly don’t care what happens on their desktop. It’s mostly not in their control. They either don’t have a choice or don’t realize they have one, and their expectations have been systematically lowered by two decades of unexciting user experience.
By contrast, the iPhone functions in a hot realm where consumers do make choices, and where choices are badges. Of course many people are forced economically to choose the cheap or free phone that comes with their mobile service. But many others are in a position to select a device. And the iPhone is to today’s urban professional gym rat what cigarettes and martinis were to their 1950s predecessors. You and I may claim to choose a mobile device based on its features, but the upwardly mobile (pardon the pun), totally hot person standing next to us in the elevator may choose their phone the same way they choose their handbag. And now that the iPhone sells for $99, more people can afford to make a fashion decision about their phone—and they’ll do it.
Although there were great phones before the iPhone, and although the iPhone has its detractors, it is fair to say that we are now in a Mobile 2.0 phase where people expect more than a Lynx-like experience when they use their phone to access the internet. Mobile Safari in iPhone, along with the device’s superior text handling thanks to Apple and Adobe technologies, is changing perceptions about and expectations of the web in the same way social networking did, and just at the historical moment when social networking has gone totally mainstream.
Oprah’s on Twitter, your mom’s on Twitter, and they’re either using an iPhone or a recently vastly upgraded Palm or Blackberry that takes nearly all of its cues from the iPhone. Devices that copy the iPhone of course mostly end up selling the iPhone, the same way Bravo’s The Fashion Show would mostly make you miss Project Runway if you even watched The Fashion Show, which you probably haven’t.
Safari isn’t perfect, and Mobile Safari has bugs not evident in desktop Safari, but Webkit + Apple = secret sauce selling web standards to a new generation of consumers and developers.
Web Fonts, HTML 5 Roundup: Worthwhile reading on the hot new web font proposals, and on HTML 5/CSS 3 basics, plus a demo of advanced HTML 5 trickery. — 20 July 2009
HTML 5: Nav Ambiguity Resolved. An e-mail from Chairman Hickson resolves an ambiguity in the nav element of HTML 5. What does that mean in English? Glad you asked! — 13 July 2009
In Defense of Web Developers: Pushing back against the “XHTML is bullshit, man!” crowd’s using the cessation of XHTML 2.0 activity to condescend to—or even childishly glory in the “folly” of—web developers who build with XHTML 1.0, a stable W3C recommendation for nearly ten years, and one that will continue to work indefinitely. — 7 July 2009
XHTML DOA WTF: The web’s future isn’t what the web’s past cracked it up to be. — 2 July 2009
The new browser is based on Webkit, the advanced-standards-compliant, open source browser engine that powers Apple’s Safari for Mac and PC, but Chrome currently runs only in Windows. You figure that out.
To compete with Microsoft, the new browser must offer what other browsers do not. The risk inherent in that proposition is a return to proprietary browser code. It is not yet clear to me whether Chrome will compete the wrong way—offering Chrome-only features based on Chrome-only code, thus prompting Microsoft to rethink its commitment to standards—or the right way.
Competing by offering features other browsers do not (easier downloads, streamlined user interface) or by consolidating other browsers’ best features (Opera’s Speed Dial, Firefox’s auto-complete) avoids this risk, as improvements—or at any rate, changes—to the browser’s user interface have no bearing on the display of existing web content.
Competing by supporting web standards ahead of the pack, although not entirely without risk, would also be a reasonable and exciting way to compete. When one browser supports a standard, it goads other browser makers into also supporting it. Because Safari, for instance, supports @font-face, Firefox is not far behind in supporting that CSS spec. @font-face raises font licensing problems, but we’ll discuss those another time. The risk that concerns us here is when a browser supports an emerging specification before it is finalized, thus, essentially, freezing the spec before it is ready. But that is the traditional dance between spec authors and browser makers.
For web standards and web content, we once again live in interesting times. Welcome, Chrome!