Apropos of nothing in particular, I present my all-time listening (first 5.25 rows) and more recent listening:
Because I’m weird that way: Sometimes I’ll listen extensively to a particular artist from my collection whom I might not have played in a while, simply to bump them higher in the mosaic or reposition them for a more pleasing composition.
If Spotify exposes you to new music, Last.fm helps remind you of great music in your existing collection that may have slipped your mind. (Not an advertisement. I use last.fm and get great pleasure from how it helps me discover and fuss with my music, as I once spent hours in the old days stacking and rearranging my LPs and tapes.)
And that’s how I stay out of the pool halls.
Public Service P.S: If you do decide to try last.fm, please, by all means, pay the small monthly subscription fee if you can. Doing so supports the under-resourced team that keeps the service going. It also removes the ads, making the site usable (the ads are a nightmare), and gives you the option to view your music as a visual grid, like those shown in my screenshots. The grid-view makes the site. It gives you, not just a visual record collection, but a visual artist collection, if you’ll allow the conceit. I love it.
Like 90s hip-hop, The Web We Lost™ retains a near-mystical hold on the hearts and minds of those who were lucky enough to be part of it. Luke Dorny’s recent, lovingly hand-carved redesign of his personal site encompasses several generations of that pioneering creative web. As such, it will repay your curiosity.
Check Luke’s article page for textural, typographic, and interactive hat tips to great old sites from the likes of k10k, Cameron Moll, Jason Santa Maria, and more.
And don’t stop there; each section of the updated lukedorny.com offers its own little bonus delights. Like the floating titles (on first load) and touchable, complex thumbnail highlights on the “observer” (AKA home) page.
And by home page, I don’t mean the home page that loads when you first hit the site: that’s a narrow, fixed-width design that’s both a tribute and a goof.
No, I mean the home page that replaces that narrow initial home page once the cookies kick in. Want to see the initial, fixed-width home page again? I’m not sure that you can. Weird detail. Cool detail. Who thinks of such things? Some of us used to.
And don’t miss the subtle thrills of the silken pull threads (complete with shadows) and winking logo pull tab in the site’s footer. I could play with that all day.
Now, no site exactly needs those loving details. But danged if they don’t encourage you to spend time on the site and actually peruse its content.
There was a time when we thought about things like that. We knew people had a big choice in which websites they chose to visit. (Because people did have a big choice back in them days before social media consolidation.) And we worked to be worthy of their time and attention.
Days of future past
We can still strive to be worthy by sweating details and staying alive to the creative possibilities of the page. Not on every project, of course. But certainly on our personal sites. And we don’t have to limit our creative love and attention only to our personal sites. We pushed ourselves, back then; we can do it again.
In our products, we can remember to add delight as we subtract friction.
And just as an unexpected bouquet can brighten the day for someone we love, in the sites we design for partners, we can be on the lookout for opportunities to pleasantly surprise with unexpected, little, loving details.
Crafted with care doesn’t have to mean bespoke. But it’s remarkable what can happen when, in the early planning stage of a new project, we act as if we’re going to have to create each page from scratch.
In calling Luke Dorny’s site to your attention, I must disclaim a few things:
I haven’t run accessibility tests on lukedorny.com or even tried to navigate it with images off, or via the keyboard.
Using pixel fonts for body copy, headlines, labels, and so on—while entirely appropriate to the period Luke’s celebrating and conceptually necessary for the design to work as it should—isn’t the most readable choice and may cause difficulty for some readers.
I haven’t tested the site in every browser and on every known device. I haven’t checked its optimization. For all I know, the site may pass such tests with flying colors, but I tend to think all this beauty comes at a price in terms of assets and bandwidth.
Nevertheless, I do commend this fine website to your loving attention. Maybe spend time on it instead of Twitter next time you take a break?
I’ll be back soon with more examples of sites trying harder.
CAN design create a better user experience that engages readers and drives revenue? Can it fight fake news and help save real journalism at a time when news organizations large and small are underfinanced and under attack?
The challenge began October 17–18 in New York, with five pundits and five designers, of whom I was honored to be one, workshopping a project brief during a two-day conference event at the Columbia Journalism School. (You can watch videos of all these sessions courtesy of Fora.tv.)
The next phase took place yesterday in St. Petersburg, Florida, as the four other designers and I presented our work to a live audience. In this short piece, I’ll talk about the designs my colleagues presented; in the next, I’ll discuss my own.
Reconnecting with the people: the challenge for digital news
Roger Black described the difficulties facing digital news publications:
The challenge is serious. Fake news crowds real news. Numbers no longer add up for publishers. Readers jump from site to site without knowing where they are, or staying for long. You can see the brief for this project here.
Can design help? Well, as a I designer, I think it can. I mean, the design of most news pages is not what you’d call attractive. But the solutions proposed at Poynter will be much more strategic than cosmetic. And they’re strategies that can be combined.
—Five design answers that add up, Roger Black, January 20, 2017
“A news publication might think a bit more like Fitbit”
Between us, we designers had about a century of experience designing digital publications—internally, as consultants, or both. This means that, even though an open “design challenge” brief necessarily omits an unknown number of the specific requirements any actual publication design assignment would include, all of us were aware of, and to some degree addressed, typical news publication requirements not included in our brief.
Kat Downs Mulder, Graphics Director at The Washington Post, shared a prototype for a big-brand news site. Kat had just given birth to a healthy baby boy (congratulations!), so her work was presented by two of her colleagues from The Post. Kat did not design with the avid, committed news reader in mind (since those folks are not the problem for most publications). Instead, she pondered how to engage the typically fragmented attention of today’s distracted and passive news reader:
“A big-brand news site [should be] aware that people have a lot more to do in their lives than read the news,” Kat posited. Thus, “A news publication might think a bit more like Fitbit. That is, it should make you feel like it’s working for you. A reader should say, ‘I’m reading everything I need to know.’”
Keep that dopamine pumping
Kat presented a multi-paned prototype. The wider pane on the right contained news content; the narrower pane at left was navigation. As I’ve just described it, this isn’t much different from the current Post website, but Kat’s prototype was very different, because it prized reader control over editorial director control; kept track of what you read; encouraged extra reading the way Fitbit encourages extra steps, and rewarded it the same way Fitbit does, with an accumulation of points that give the reader dopamine hits and create the perception that the “news app” is working for her—as a rewarding part of her busy lifestyle.
An Operating System for your city
Mike Swartz, Partner at Upstatement, a design and engineering studio in Boston, took on the challenge to smaller publications (such as his original hometown paper, the Pittsburgh Post-Gazette) which lack the resources of a Washington Post or New York Times.
Mike’s presentation, “information OS for a city: redefining the opportunity for local media,” turned the journalistic prowess of a good local paper into a superpower, connecting readers to their city the way the “terrible towel” stunt concocted in desperation by radio announcer Myron Cope in 1975 reconnected Pittsburghers to their hometown football team, and helped the Steelers win Super Bowl X over the Dallas Cowboys.
There’s a potential for an operation like the [Post Gazette] to rebrand itself as more of an “informational operating system” for its city. With different types of products that are focused and useful and not necessarily bundled into a traditional news format, we can create more enjoyable experiences and more useful products readers will love.
Building reader interest and finding a way to pay for it all
Where the rest of us avoided the elephant in the room, in her design Lucie Lacava, president of Lacava Design Inc., boldly confronted the challenges of advertising and monetization. Algorithm-driven advertising frustrates users, who, in desperation, block it. Choked for income as a result, publications and advertisers create more and more intrusive forms of unwanted advertising. Nobody wins.
And while subscription models have worked, at least partly, for some of the very top news publications, such models are not likely to help most news publications in the near term.
Digital publication as digital application
Lucie’s design addressed these challenges by recasting the news as a hyper-customized application targeted at younger users, who get to choose news streams and ads that are relevant to them. “The elusive millennial” was Lucie’s target. I cannot do her idea justice with a couple of paragraphs and a single screen shot.
Affordable, immersive VR is here
Jared Cocken, brand and product designer for hire and co-founder of STYLSH.co., approached the “attention war” by showing how any size publication could create “video or VR driven stories that enrich a user’s understanding of the world around them.”
Because VR video is immersive, it holds viewer attention. Because it is reality-based, it fights fake news. (It’s hard to call bullshit on a scene you can explore from any angle.) VR also, potentially, builds compassion. It’s one thing to read about conditions in a Syrian refugee camp, another to visually experience them in VR.
Until now VR and video have been cost-prohibitive, but, working (and co-presenting) with VR startup founder Anna Rose and Hollywood producer/actor Banks Boutté, Jared showed how even woefully under-financed newsrooms can use newly designed, super-affordable tools to create “video or VR-driven stories that enrich a user’s understanding of the world around them.”
Blogging about a conference is like tweeting about a sexual experience. You had to be there. I wanted to record and share the outlines of what my fellow designers presented, but these few paragraphs should in no way be considered authentically representative of the deep thinking and work that went into every presentation.
You may see holes in some of the arguments presented here. In some cases, I might agree with you—some ideas, while dazzlingly creative, did not seem to me like the right way to save news. But in most cases, if an idea seems wrong, blame my telling. If you had been there and heard and seen everything, the value of the proposal would have far more apparent than it can be here.
I love that each of us took on a quite different aspect of the problem, and addressed it using very different tools. I’ll be back soon with a short write-up of the design approach I took. Meanwhile, I want to thank all the pundits, designers, and attendees in New York and St. Petersburg—and the Poynter Institute, Roger Black, and William R. Hearst III for making it all possible.
IN a world where newspapers are dying and half the public believes fake news, what online news experiences need is design that is branded, authoritative, and above all, readable:
Branded, because we need to convert the current hummingbird model (where readers flit from flower to flower) back to the idea that your news source matters—and that it is worth your time to return to a source you trust.
Brand helps the social-media-driven seeker notice that they’re returning time and again to a certain resource, facilitating a mental model shift back toward destination web browsing. When every site looks the same, it’s easy to see all content as equal—all spun from the same amorphous mass. A strong brand, which is individual to the given newspaper, can cut through that amorphousness, which is the first step in building (or rebuilding) loyalty.
Authoritative, because combating fake news means visually cueing the reliability of a particular source—one staffed by real journalists and editors, with real sources in real countries. In the coming years this will be more important than ever.
Readable, because an informed public needs to grasp stories that can’t always be reduced to headlines or sound bytes. Readability means even longer articles actually get read, sometimes even all the way through. Readability requires a combination of typeface, type size, leading, measure, hierarchy, contrast, etc.—as well as the introduction of visual information, both to break up the flow of text, and to further illuminate what is being said.
Related news keeps readers reading
Additionally, this branded, authoritative, readable content needs to become (to use an ancient word) sticky: through a combination of editing and algorithms, related content must be presented at the appropriate time in the reading experience, to engage the visitor in continued reading.
Currently two publications—nytimes.com and medium.com—achieve all these goals better than any other publications on the web. One is the newspaper of record; the other is a vehicle for anyone’s content. Yet both really do the job all newspapers will need to do to survive—and to help the Republic survive these next years. I particularly admire the way both publications surface related content in a way that practically demands additional reading.
Design won’t solve all the problems facing newspapers, but it will help. And unlike more “immersive” approaches such as WebVR, original full-screen imagery, and original embedded video, the basics of solid, readable design should not be out of budgetary reach for even the most cash-strapped news publisher—budget being a problem for any business at any time, but especially for newspapers now.
In my studio, we’ve been pondering these problems for content sites of all types (not only newspapers). At the Poynter Digital Design Challenge next month, I hope to share designs that nudge the conversation along just a bit further.
12 LESSONS from An Event Apart San Francisco – ? 4: Jason Grigsby was the 10th speaker at An Event Apart San Francisco last week. Jason’s session, Adapting to Input, presented designers and developers with a conundrum many of us hadn’t yet considered when designing for our new spectrum of web-capable devices.
Responsive web design forced us to accept that we don’t know the size of our canvas, and we’ve learned to embrace the squishiness of the web. Well, input, it turns out, is every bit as challenging as screen size! We have tablets with keyboards, laptops that become tablets, laptops with touch screens, phones with physical keyboards, and even phones that become desktop computers. What’s a design mother to do?
During his session, Jason guided us through the input landscape, showing us new forms of input (such as sensors and voice control) and sharing new lessons about old input standbys. We learned the design principles needed to build websites that respond and adapt to whichever inputs people choose to use.
Four truths about web inputs
Jason began by sharing four truths about input in 2016:
Input is exploding — The last decade has seen everything from accelerometers to GPS to 3D touch.
Input is a continuum — Phones have keyboards and cursors; desktop computers have touchscreens.
Input is undetectable — Browser detection of touch‚ and nearly every other input type, is unreliable.
Input is transient — Knowing what input someone uses one moment tells you little about what will be used next.
A Golden Rule of Inputs
Just as many of us screwed up our early approach to multi-device design by consigning the “mobile web” to a non-existent “mobile context,” we now risk making a similar blunder by believing that certain tasks are “only for the keyboard”—forgetting that by choice or of necessity, the people who engage with our websites use a variety of devices, and our work must be available to them all.
One of my principal takeaways from Jason’s presentation was that every desktop design must go “finger-friendly.” Or, as Josh Clark put it back in 2012, “When any desktop machine could have a touch interface, we have to proceed as if they all do.”
For more illuminations on input, read Jason Grigsby’s “Adapting to Input” in A List Apart, and check out these amazing demos and articles:
Tomorrow I’ll be back with another top takeaway from another AEA San Francisco 2016 speaker. The next AEA event, An Event Apart St. Louis, takes place January 30-February 1, 2017 in the shadow of Mr Sarrinenen’s fabulous arch. See you there!
I DREAMED that my friend Jason Santa Maria took a job at a popular new startup that had exploded onto the world scene seemingly overnight. A fascinating visual interface was largely responsible for the popularity of the company’s new social software product. It was like a Hypercard stack that came toward you. A post full of exciting social significance just for you would appear in a self-contained deck with rounded corners. The next post would pop up on top of the first. The next, on top of that one. And so on. In my dream, people found this back-to-front pop-up effect thrilling for some reason.
Having imagined the interface, I next dreamed that I went to visit the startup. There were so many cubicles, so many shiny people running around, holding morning standups and singing a strange company song, that I could not locate my friend Jason’s desk. Someone grabbed me and told me the founder wanted to see me.
THE FOUNDER was an ordinary looking white guy in his late twenties. I was surprised that he wore beige chinos with a permapress crease. With all the TV and newspaper hubub around his product, I guess I’d expected a more stylish and charismatic presence.
The founder told me he was concerned because his mother, apparently a cofounder or at least an officer of the company, was of the belief that I had contempt for their product and disliked her personally. I assured him that I liked the product. Further, I had never met his mother, never read or heard a word about her, and felt only goodwill toward her, as I bear toward all people in the abstract. I don’t hate people I don’t know.
“It would be cool if you told mom that yourself,” he said. And suddenly two assistants were whisking me off to speak to her directly.
THE AUDITORIUM-SIZED waiting room outside the founder’s mother’s office was filled with at least a thousand people who had come to talk to her before me. They seemed to have been waiting for hours. There was an air of boredom and rapidly thinning patience, mixed with excitement and the kind of carnival atmosphere that surrounds things that blow up suddenly in the press. It felt like the jury selection room for a celebrity murder case. Only much, much bigger.
The two assistants escorted me to the very front of the auditorium, to an empty row of seats abutting the door to the founder’s mother’s private office. “Special treatment,” I thought. I was thrilled to be cutting to the front of the line, apparently as a result of the founder’s directive to his assistants. The front row chairs were reversed, facing back to the rest of the auditorium, so I was put in the somewhat uneasy position of staring out at the mass of people who had been waiting to see the founder’s mother since long before I arrived.
After a while, Ian Jacobs of the W3C was brought to the front of the room and seated near me.
We waited as other people were shown into the founder’s mother’s presence.
AFTER FIVE or six hours of drowsy waiting, I realized that the room was set up to mirror the software’s interface: people from the very back of the auditorium were first in line, and were shown into the founder’s mother’s presence first. Gradually, the hall of applicants emptied from the back to the front. Those of us in the very front of the line were actually the last people of all who would be admitted to the holy presence. It was a smart marketing touch that apparently permeated the company: everything real people did in the building in some way echoed the characteristics of the software interface — from the end of the line coming first, to the way the rounded conference tables echoed the shapes of individual news posts in the software’s back-to-front news deck.
What a smart company, I thought. And what a good joke on me, as I continued to sit there forever, waiting to see someone I’d never met, who held a baseless grudge against me, which it would one day be my task to talk her out of.
YOU FIND ME ENSCONCED in the fabulous Buckhead, Atlanta Intercontinental Hotel, preparing to unleash An Event Apart Atlanta 2011, three days of design, code, and content strategy for people who make websites. Eric Meyer and I co-founded our traveling web conference in December, 2005; in 2006 we chose Atlanta for our second event, and it was the worst show we’ve ever done. We hosted at Turner Field, not realizing that half the audience would be forced to crane their necks around pillars if they wanted to see our speakers or the screen on which slides were projected.
Also not realizing that Turner Field’s promised contractual ability to deliver Wi-Fi was more theoretical than factual: the venue’s A/V guy spent the entire show trying to get an internet connection going. You could watch audience members twitchily check their laptops for email every fourteen seconds, then make the “no internet” face that is not unlike the face addicts make when the crack dealer is late, then check their laptops again.
The food was good, our speakers (including local hero Todd Dominey) had wise lessons to impart, and most attendees had a pretty good time, but Eric and I still shudder to remember everything that went wrong with that gig.
Not to jinx anything, but times have changed. We are now a major three-day event, thanks to a kick-ass staff and the wonderful community that has made this show its home. We thank you from the bottoms of our big grateful hearts.
I will see several hundred of you for the next three days. Those not attending may follow along:
BECAUSE FACEBOOK LIMITS USERS to 5,000 contacts, I had to migrate from a conventional user account to what used to be called a “fan” page and is now called an “Artist, Band or Public Figure” page. (Page, not account, notice.)
There’s a page on Facebook called “Create a Page” that is supposed to seamlessly migrate from a conventional user account to a public figure (aka “fan”) page.
The page says it will only migrate your connections—it will lose all your content, photos, apps, and so on—and Facebook means it. After migrating, all my stuff is gone. Years of photos, wall posts, blog posts, tweets, you name it. Even the “help” page link is gone once you’ve migrated, so you can’t refer to any help documentation to find out where all your stuff went and if any of it can be saved.
Custom URL breaks on migration
Because of an idiocy in the database, you can’t keep your existing custom URL, since, when you request it, Facebook tells you it is “taken.” My Facebook page was “jzeldman,” but that URL is “taken” by a fellow named “Jeffrey Zeldman,” so I can’t use it on my Jeffrey Zeldman page. So I had to change to a new URL (“JeffreyZeldman”) and now all my admin links (for instance at facebook.com/happycog) are broken, as they point to the old user page instead of the new fan page. At the very least, Facebook should seamlessly redirect from facebook.com/jzeldman (my old URL) to facebook.com/JeffreyZeldman (the new one), but it does not.
So all my other social media sites that point to the old Facebook account need to be updated by hand, and any third-party links will now be broken because Facebook doesn’t let you keep your custom URL during a migration.
Third-party apps disappear completely
Likewise, none of the third-party functionality (Twitter, Tumblr, Flickr, RSS, and so on) has migrated from the user page to the fan page, and there is no information explaining how to reconnect these apps.
No reasonable app like the ones I’ve mentioned appears in the “apps” section of the sidebar on my new page. When I look for additional apps, I get treated to a bloated browse of crappy apps nobody on earth uses, whose creators probably made deals with Facebook in hopes that newbies would be persuaded to hook up these contraptions. You can find “PhotoMyButt” but not Flickr.
I, however, use Flickr.
So, since I can’t find it in the big dull browse, I resort to Facebook’s Apps’ “Search” box. Typing Flickr in that box is exciting. Instead of being taken to the Flickr apps on Facebook, I’m treated to endless redirects courtesy of a broken PHP script that loops infinitely forever suffering like Christ on the cross world without end amen while never actually resolving. Each new partial page that loads for an instant before being replaced by the next is undesigned and unbranded and contains only the sentence fragment, “Please stand by, redirecting…”
The devil will see you now.
So much for content
My photos are gone. My existing writing is gone. Facebook does seem to be migrating human beings who were “friends” on my old page, but nothing else works.
Oh my God, I can’t Admin my own page
I can’t Admin my new Facebook page because the “Admin” is “jzeldman” (me at the old account, which Facebook deleted). Perhaps this is why it’s impossible to post content, no apps work, etc. Nice.
Kids, don’t try this at home
All these bugs are probably known to Facebook, and there are probably nice people at Facebook whose job is to execute known secret internal workarounds when helping an actual “celebrity” migrate his or her page. I’m just guessing of course, but it stands to reason that Ashton K or Lady Gaga, if they want a Facebook page, probably don’t have to deal with all this frustrating brokenness. They have people for that.
But I don’t. I’m a web guy. And web stuff should just work.
WHAT A YEAR 2010 has been. It was the year HTML5 and CSS3 broke wide; the year the iPad, iPhone, and Android led designers down the contradictory paths of proprietary application design and standards-based mobile web application design—in both cases focused on user needs, simplicity, and new ways of interacting thanks to small screens and touch-sensitive surfaces.
It was the third year in a row that everyone was talking about content strategy and designers refused to “just comp something up” without first conducting research and developing a user experience strategy.
Even outside the newest, best browsers, things were better than ever. Modernizr and eCSStender brought advanced selectors and @font-face to archaic browsers (not to mention HTML5 and SVG, in the case of Modernizr). Tim Murtaugh and Mike Pick’s HTML5 Reset and Paul Irish’s HTML5 Boilerplate gave us clean starting points for HTML5- and CSS3-powered sites.
Print continued its move to networked screens. iPhone found a worthy adversary in Android. Webkit was ubiquitous.
Insights into the new spirit of web design, from a wide variety of extremely smart people, can be seen and heard on The Big Web Show, which Dan Benjamin and I started this year (and which won Video Podcast of the Year in the 2010 .net Awards), on Dan’s other shows on the 5by5 network, on the Workers of the Web podcast by Alan Houser and Eric Anderson, and of course in A List Apart for people who make websites.
Zeldman.com: The Year in Review
A few things I wrote here at zeldman.com this year (some related to web standards and design, some not) may be worth reviewing:
Lack of Flash in the iPad (and before that, in the iPhone) is a win for accessible, standards-based design. Not because Flash is bad, but because the increasing popularity of devices that don’t support Flash is going to force recalcitrant web developers to build the semantic HTML layer first.
Love means never having to say you’re sorry, but client services means apologizing every five minutes. Give yourself one less thing to be sorry for. Take some free advice. Show up often, and show up early.
A few things I wrote elsewhere might repay your interest as well:
Cheap, complex devices such as the iPhone and the Droid have come along at precisely the moment when HTML5, CSS3 and web fonts are ready for action; when standards-based web development is no longer relegated to the fringe; and when web designers, no longer content to merely decorate screens, are crafting provocative, multi-platform experiences. Is this the dawn of a new web?
When Style is a fetish, sites confuse visitors, hurting users and the companies that paid for the sites. When designers don’t start by asking who will use the site, and what they will use it for, we get meaningless eye candy that gives beauty a bad name.
Now we have something else to be thankful for. Nathan Smith of Sonspring has created a library that gives designers and developers “some measure of control over form elements, without changing them so drastically as to appear foreign in a user’s operating system.” Smith calls his new library Formalize CSS:
I’ve attempted to bridge the gap between various browsers and OS’s, taking the best ideas from each, and implementing what is possible across the board. For the most part, this means most textual form elements have a slight inset, and all buttons look consistent, including the button tag.
For more, including demos, options, screenshots, thanks, and the library itself, read Smith’s write-up at SonSpring | Formalize CSS. Hat tip and happy Thanksgiving to my good friend Aaron Gustafson for sharing this gem.
IN THE TRADITION of “People who bought ‘Assmasters’ also bought ‘Assmasters II,'” Twitter has chosen four of my Twitter friends and is presenting them to me as being “Similar to You.” Pray what does this odd-in-this-context phrase, with its “Related Products” vibe, mean? Does it mean if I like myself, I would also like these people? Surely not, for I already know that, as demonstrated by the fact that I follow them. Were they chosen for discussing similar subjects (e.g. design, web design, CSS, semantic markup)? Unlikely, as that would imply Google-like keyword data mining and analysis bordering on artificial intelligence.
Then, what? It can’t mean people whose tweets resemble mine, as the Twitter writing style and frequency of the listed friends is purely their own. People with whom I have followers in common? That seems most likely, but it’s just a guess.
I’m curious to know what Twitter and its new CEO (hi, Dick!) mean by this. What is the marketing purpose of this feature? Am I to view Twitter as an informal “personal brand analysis” service? That could be cool for me and for the four people who are “Similar” to me. But surely most users would be uninterested in such a service, unless, unbeknownst to me, nearly everyone who uses Twitter is a marketer who views it primarily as a channel. And most companies don’t spend money developing long-tail features, of interest only to a tiny fraction of their users.
I love Twitter. I wish I’d invented it, and not primarily because if I’d invented it I’d be taking the Japanese women’s gymnastics team on a round-the-world cruise. I wish I’d invented it because it is something really new on the internet, like the web, and filled with potential, like the web. As a designer, I pay attention to Twitter same as I do Apple, Google, Flickr, and Facebook. The new feature intrigues me precisely because its language feels “off” and its purpose eludes me.
Also of interest, although less so: what data is being used, and how is it being analyzed?
A List Apart and .net magazine have long admired each other. So when .net editor Dan Oliver did me the great honor of asking if I wished to guest edit an issue, I saluted smartly. The result is now arriving in subscriber post boxes and will soon flood Her Majesty’s newsstands.
In .net magazine Issue No. 206, on sale 17th August in UK (and next month in the US, where it goes by the name “Practical Web Design”), we examine how new standards like CSS3 and HTML5, new devices like iPhone and Droid, and maturing UX disciplines like content strategy are converging to create new opportunities for web designers and the web users we serve:
Exult as Luke Wroblewski shows how the explosive growth of mobile lets us stop bowing to committees and refocus on features customers need.
Marvel as Ethan Marcotte explains how fluid grids, flexible images, and CSS3 media queries help us create precise yet context-sensitive layouts that change to fit the device and screen on which they’re viewed.
Delight as Kristina Halvorson tells how to achieve better design through coherent content wrangling.
Thrill as Andy Hume shows how to sell wary clients on cutting-edge design methods never before possible.
Geek out as Tim Van Damme shows how progressive enhancement and CSS3 make for sexy experiences in today’s most capable browsers—and damned fine experiences in those that are less web-standards-savvy.
You can also read my article, which asks the musical question:
Cheap, complex devices such as the iPhone and the Droid have come along at precisely the moment when HTML5, CSS3 and web fonts are ready for action; when standards-based web development is no longer relegated to the fringe; and when web designers, no longer content to merely decorate screens, are crafting provocative, multi-platform experiences. Is this the dawn of a newer, more mature, more ubiquitous web?
Today’s web is about interacting with your users wherever they are, whenever they have a minute to spare. New code and new ideas for a new time are what the new issue of .net magazine captures. There has never been a better time to create websites. Enjoy!
Photo by Daniel Byrne for .net magazine. All rights reserved.
Most of us web folk are hybrids of one sort or another, but Todd Dominey was one of the first web designers to combine exceptional graphic design talent with serious mastery of code.
Being so good at both design and development that you could easily earn a fine living doing just one of them is still rare, although it looks like the future of our profession. One of the first serious designers to embrace web standards, Todd was also one of the few who did so while continuing to achieve recognition for his work in Flash. (Daniel Mall, who came later, is another.)
Finally, Todd was one of the first—along with 37signals and Coudal Partners—to abandon an enviably successful client services career in favor of full-time product development, inspiring a generation to do likewise, and helping bring us to our current world of web apps and startups.
A personal project that became an empire
In Todd’s case, the product was SlideShowPro, a project he designed for himself, which has grown to become the web’s most popular photo and video slideshow and gallery viewer. When you visit a photographer’s portfolio website, there’s an excellent chance that SlideShowPro powers its dynamic photo viewing experience. The same is true for the photo and video gallery features of many major newspaper and magazine sites, quite possibly including your favorites.
But deliberate lack of Flash support in the iPad and iPhone, while lauded here on February 1, 2010 as a win for accessible, standards-based design (“Not because Flash is bad, but because the increasing popularity of devices that don’t support Flash is going to force recalcitrant web developers to build the semantic HTML layer first”), presented a serious problem for developers who use SlideShowPro and readers who enjoy browsing dynamic photo and video galleries.
SlideShowPro Mobile is an entirely new media player built using HTML5 that doesn’t require the Flash Player plugin and can serve as a fallback for users accessing your web sites using these devices. But it’s not just any fallback — it’s specially designed for touch interfaces and smaller screen sizes. So it looks nothing like the SlideShowPro player and more like a native application that’s intuitive, easy to use, and just feels right.
The best part though is that because SlideShowPro Director (which will be required) publishes the mobile content, you’ll be able to provide the mobile alternative by simply updating the Flash Player embed code in your HTML documents. And just like when using the SlideShowPro player, because Director is behind the scenes, all your photos will be published for the target dimensions of these devices — which gives your users top quality, first generation images. The mobile player will automatically load whatever content is assigned to the Flash version, so the same content will be accessible to any browser accessing your web site.
A public beta will be released in the next weeks. Meanwhile, there is a video demo. There’s also an excellent Question and Answer page that answers questions you may have, whether you’re a SlideShow Pro customer or not. For instance:
Why mobile? Why not desktop?
We believe that (on the desktop) Flash is still the best delivery method for photo/video galleries and slideshows for it provides the most consistent user experience across all browsers and the broadest range of playback and customization options. As HTML5 support matures across all desktop browsers, we’ll continue to look into alternate presentation options.
I have known 37signals CEO Jason Fried since he was a young copywriter who reminded me of me, only smarter and more confident. Like many of you, with a mixture of awe and pleasure, I have watched him change our industry, along with book publishing and business generally. Dan Benjamin and I are delighted to announce the mercurial Mr Fried as our guest on The Big Web Show. Join us today, 1 July 2010, for the live taping at 1:00 PM ET.
Jason’s official bio is brief, but he can write at length when he wishes: see Rework, Getting Real, and Defensive Web Design, each a classic, and to each of which he was principal co-writer and guiding force. Besides saying no to meetings, contracts, and VC money, Jason and 37signals are famous for godfathering a speedy, iterative form of web application design; for gifting the industry with Ruby on Rails; for creating a suite of beloved (yes, really) business productivity web apps; for mastering and then abandoning client services in favor of making stuff; for somehow, in the midst of all that busyness, churning out tons of fine content on their popular blog; and for being roommates with the equally fantastic Coudal Partners.
Can’t wait to interview Jason Fried in front of a live internet audience today. Hope you’ll join us.
The Big Web Show 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.
Join us for a lively discussion as we talk about designing and coding for the likes of the Sundance Film Festival and New York Magazine, and the joys of responsive web design, working remotely, and swearing profusely on Twitter. We may even get Ethan’s take on Microsoft’s dazzling new IE9.
As always, watch and participate in the live broadcast by tuning to live.5by5.tv at the appointed time.