Category Archives: Web

It’s okay to do adaptive layout. Really.

Vasilis wrote yesterday about how he altered the layout of the Tropenmuseum website (English homepage) to adapt to different screen sizes.

Then came the comments. Nothing really wrong with any of them, but the whole “layout is not the only thing that should concern you; performance/context/content/blah is also (maybe even more important)” thing is getting very tired. Why? Because nobody is saying those things aren’t important.

Here’s a fact: If the homepage of site [x] is 100kB, then it’s 100kB. If I make that page look decent on several devices via adaptive layout—unless I go overboard—it is still going to be 100kB. Okay, maybe 101kB. It’s either zoom hell or not. So people can complain about that, but unless they’re willing to add to the client’s budget, the extra layout flexibility is (often, not always) a relatively quick readability and usability win. Device-agnosticism should be baked into the design approach anyway. There’s absolutely no harm in it.

So no, do not ignore content strategy and performance. And if you do content strategy, then you’d do well to be thinking about design. Device-agnostic design applies here as well.

Don’t feel bad about doing adaptive layout just because these other things are also important. It’s okay. Really.

Upcoming speaking engagements

When I left Cinnamon last October to focus more on strategy and device-agnostic design and development, I also had another goal in mind: more speaking. I also wanted to write more; you can see how well that’s working out for me :).

I love speaking. Except for a couple of hours beforehand, when I’m so nervous I feel like throwing up. The past few years I’ve done quite a bit of speaking at conferences and events for clients, and that initial nervousness is there every single time. Fortunately the feeling subsides after the first few minutes of the talk.

I tend to talk a lot, and speaking engagements are a way to channel that into something that might inspire someone, teach them something new, or start a discussion. At web design and development conferences, it’s no secret that the speakers learn from the audience in the same way the audience might learn from the speakers. It’s also no secret that the discussions outside of the sessions are at least as interesting and valuable as the sessions themselves.

I’m very excited to be speaking at two mobile-related events this first half of the year: Breaking Development in Dallas and Mobilism in Amsterdam.

Breaking Development Conference

Breaking Development will be my first conference talk outside of the Netherlands (and then in the US), which is somewhat ironic, considering that I’m an American expat. I’m absolutely thrilled to speak alongside some of the smartest and most inspiring people in web design and development today at both of these conferences. Just take a look at the lists of speakers:

If you’re interested in designing and developing websites and web apps for mobile (or for anywhere), you might consider attending one of these conferences. Or both, if you really love conferences.

If you do attend, please come over and say hi. Just remember that there’s some risk in doing that right before my talk.

Death to web services. Long live web services!

Yahoo! is apparently shutting down Delicious, which has people falling all over themselves backing up their own data from the site and putting their bookmarks onto lesser-known services, which I’m sure will all exist until the end of time. These moves are sometimes underscored by many on Twitter by claiming that these other services “are better than Delicious anyway”, which they very well may be, although these comments reek of justification. No need: if you want to move your bookmarks, they’re yours. Just move them.

But that’s the thing: we’re talking about bookmarks, the loss of which will hardly leave you living out of a cardboard box. And what happens when bad things happen to Flickr? GMail? Evernote? That site you do all your finances on? Project management and invoicing? Time tracking?

You may back up all your data, which makes the downfall of any of these services less painful. Unless you just keep your original photos on your own computer, but all of your photo metadata was entered on Flickr and you have no backup of that. Poof! But we all know Flickr’s not going anywhere, right? Too many users. Actively developed. Very popular. Cough. It’s the same reason we can depend on YQL (which I still find absolutely brilliant BTW). Yahoo! will give us all at least six months notice if they decide to pull the plug on YQL, which gives us the time to change all of the client work we made utilizing it. And of course our clients will have six months to get a budget to hire us to make the necessary changes.

But what are we complaining about? It’s all free. Having to move our bookmarks is not really a huge problem, but we all seem appalled that large companies care about money. Since when is this an anomaly? Company sees something cool, hopes to make money, buys it, doesn’t make enough money, poof. Here’s a truth for you: most companies only care about your data insofar as this data can help them make money. They have this site and you fill it. You fill it.

A couple of years ago I was on the fence about this. No longer. For a while we’ve posted our data all over the internet on all types of services. These services provide APIs so we can access the data we put into them, so that we can do things with that data. Read that again.

Richard Stallman, in his usual come-out-swinging way, has commented on this before. And I believe he has a point. Our data is our own, and it’s up to us to look after it. But how?

What if we flipped this all on its head? What if we hosted our own data, and provided APIs for all these webapps so that they can use our data? I can imagine that to be a substantially cool use of RDFa/Microformats and whatever metadata/semantic web technologies you prefer. Isn’t one of the points of the semantic web to make decentralized information meaningful, retrievable and mixable?

So instead of having our own websites aggregate our own data from other people’s websites, we’ll let other people use the data from our own websites. Photos, meaningfully tagged, can be pulled in by Flickr via our own personal API, if you will. We provide the structured data, Flickr provides the functionality. The sharing. The social. Why not?

Personal publishing platforms like WordPress, Drupal, [your favorite here] could be extended to make use of microformatting, RDF, etc. and provide tools for syndication, as we now do with simple blogposts. Services don’t need to host our data. They only need to do cool things with it. So when I quit service X, or service Y falls the Way of GeoCities, I don’t need to do anything but cancel my account. Or leave it and forget about it. If I change my information, it’s automatically changed on all the services using it. Storage space is up to me. Privacy settings? Totally up to me.

Awesome, providing the host doesn’t go *poof*.

Let’s get to it.

[Disclaimer: As some services die, some of the above links will rot. Make of that what you will.]

[UPDATE: Please also read Jeremy Keith’s related post from 2008.]