As we try to become more responsive with our designs, a lot of attention has been focused on providing “mobile” styles. We’ve all been adding viewport meta tags to our templates and @media screen and (max-device-width: 480px) to our stylesheets.
It’s very tempting (and scope-friendly) to tell a client that we can adjust their site for mobile users, when much of the time what we’re actually doing is simply adjusting a design for small screens.
…Simply adjusting a design for a smaller screen and calling it “mobile” does a disservice to both mobile users and developers. Making link targets bigger and image sizes smaller does help the mobile user, but it only addresses the surface issues of usability and readability. It doesn’t address their need to do things easily and quickly.
There’s a general agreement that the “mobile” user is not to be trifled with; give them the content they want as quickly as possible ‘cause they’re in a hurry. But the corollary does not hold true. Why do we think that the “desktop” user is more willing to put up with having unnecessary crap thrown at them?
Unnecessary page cruft is being interpreted as damage and routed around with tools like the Readability bookmarklet, Safari’s Reader functionality, and Instapaper. These services exist partly to free up content from having a single endpoint but they also serve to break content free from the shackles of stifling overwrought containers. This isn’t anything new, of course; we’ve been here before with RSS. But the existence of these new reader-empowering tools should be taken as a warning …and a challenge—how can we design for our content in such a way that the reader won’t need or want to reach for Readability or Instapaper?
The Big Web Show No. 46: Get Your Web Type on with FontDeck co-founder Richard Rutter
RICHARD RUTTER, designer, technologist, information architect, writer, and co-founder of Fontdeck and Clearleft, joins Dan Benjamin and me to discuss the technical, aesthetic, and business aspects of putting real type on the web in Big Web Show Episode No. 44, now at 5by5.tv and iTunes for your listening pleasure.
320 and up—a device agnostic stylesheet for responsible responsive design
“320 and Up prevents mobile devices from downloading desktop assets by using a tiny screen’s stylesheet as its starting point. … Inspired by Using Media Queries in the Real World by Peter Gasston, ‘320 and Up’ is a device agnostic, one web boilerplate.”
Webvanta Video: Jeffrey Zeldman on the State of Web Design
From the floor of An Event Apart Seattle 2011:
“Mobile is huge. The iPhone, iPad, and Android are huge. On the one hand, they are standards-facing, because they all support HTML5 and CSS3, so you can create great mobile experiences using web standards. You can create apps using web standards. On the other hand, there is also the temptation to go a proprietary route. In a strange way, although the browsers are much more standards compliant, it seems like we are redoing the browser war. Only now, it’s not the browser wars, it’s platform wars.”
LukeW | An Event Apart: Web 2.1 The Medium Comes of Age
“In his opening keynote at An Event Apart in Seattle, WA 2011 Jeffrey Zeldman provided a historic perspective on the development of the Internet, Web, and Web standards culminating in today’s exciting opportunities for Web designers and developers.”
Questions, Please: Jeffrey Zeldman’s Awesome Internet Design Panel today at SXSW Interactive
HEY, YOU WITH THE STARS in your eyes. Yes, you, the all too necessary SXSW Interactive attendee. Got questions about the present and future of web design and publishing for me or the illustrious panelists on Jeffrey Zeldman’s Awesome Internet Design Panel at SXSW Interactive 2011? You do? Bravo! Post them on Twitter using hashtag #jzsxsw and we’ll answer the good ones at 5:00 PM in Big Ballroom D of the Austin Convention Center.
Topics include platform wars (native, web, and hybrid, or welcome back to 1999), web fonts, mobile is the new widescreen, how to succeed in the new publishing, responsive design, HTML5, Flash, East Coast West Coast beefs, whatever happened to…?, and many, many more.
Comments are off here so you’ll post your questions on Twitter.
The panel will be live sketched and live recorded for later partial or full broadcast via sxsw.com. In-person attendees, arrive early for best seats. Don’t eat the brown acid.
Migrating from a conventional Facebook account to a public figure (“fan”) page – a report from the trenches
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.