It's a good idea to keep an eye on techniques we can use in the (near) future. Chris Coyier shows us how we could use CSS Regions to somehow fold content on a more clever way that our current techniques allow us to.
One of the absolute highlights during the excellent Mobilism conference was this talk by Jake Archibald about Application Cache. Hilarious but also extremely well researched. Be sure to read the accompanying article (you'll need it when you start working with AppChache) and the AppCache Diagram (and be sure to attend a conference where he's giving this talk).
There's a group of people who think the web should try to catch up with native, and one of the things you hear most is that it should be possible to access the camera and do cool stuff with it. Well, you can, and here's a simple tutorial (with lots of links to more info).
I'm not sure what the weather is like at your place but right here in The Netherlands winter has not ended yet. It's not snowing but it feels like it might. In that case I'll try to make one of these snowdecahedrons. And if the weather turns out to be good I'll just cut down a tree and copy this beautiful idea.
Testing your responsive site on smartphones is pretty easy, most of them have a fairly decent browser on them so usually things just work as you expect. That's not the case on feature phones though. Martin Sutherland argues that this simple observation should be an important part of your startegy when you're thinking about what test devices to buy.
In this lengthy article Baldur Bjarnason explains how hard it is to test the design of your ebook: there is little or no documentation (some documentation is even secret), and the documentation that exists is not good enough. On top of that it's impossible to get hold of some ebook readers outside of the US and even if you have one it is very hard to test books on them. If you ever start complaining again about how hard it is to test your site on all these different browsers just think of this article.
There was a row in responsive-image-land yesterday and I linked to it in the heat of the moment, something I usually try to avoid. If you wait a while things get much clearer. In this case Jeremy Keith published an excellent braindump which clearly explains the situation, the ideas and the (current) solution. You should read it if you build web sites.
Type on the web is mostly awful. It can be beautiful though. Elliot Jay Stocks started this new series about future-facing techniques to do with typography on the web
. This first article is about ligatures (a character consisting of two or more letters). If you care about type you should definitely read these articles.
One of the things I love most about our industry is the fact that everybody shares their knowledge freely. Now imagine if every link I post here would direct you to a shop where you could buy a paper, that wouldn't help you much, you wouldn't gain knowledge as fast as you do right now. In academics this is a common problem: articles get published exclusively in expensive magazines and are not freely available, which means that it's harder to gain knowledge. This is of course contradictory to what universities are all about and it clashes with the idea that publicly funded research should be freely available.
Douchebags, ebooks and decahedrons. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
Horace Dediu started the conference with a talk about David and Goliath: it’s always small, seemingly harmless newcomers that beat old established giants. By looking at the past he tried to predict the future. The most spectacular prediction he made was that Siri might be the next revolution on ways we get things into our devices after keyboard, mouse, and touch. I actually don’t believe that, it’s way too noisy and thus way too obtrusive. I don’t want to work in an office where people are constantly talking to their phone. I found Scott Jenson‘s prediction about input and behaviour based on nearby things much more appealing, but more on that on day two.
Peter-Paul Koch gave us a very clear overview of the mobile OS and browser landscape, a necessary talk, it is important to understand what’s happening around us. This was actually the first rather depressing talk: all decisions on mobile (web) seem to be made on the one hand by companies who don’t seem to give a fuck about their users and on the other hand by organizations that are rather slow. Yes, that’s depressing for an audience of 350 eager developers and designers who want to make great stuff. But the thing I found most depressing started with the talk that James Pearce gave.
This was actually an excellent talk, James Pearce is a great presenter and a pleasure to listen to, I really enjoyed his talk. This somehow surprised me because in writing he can be quite annoying. He very much wants web technologies to be able to do the same great stuff that native technologies can do. At first he distinguished some practical disadvantages the web has: discovery, distribution and monetization of which in my opinion only monetization is a somehow valid point. A good point he made was that distribution and discovery are much easier for apps that give an answer to the question What apps do my friends use? Another interesting position he takes is that we should not support older browsers at all, that things like progressive enhancement and graceful degradation (two terms he spoke with patronizing disgust) are actually bad things and that they are holding back the web, stopping innovation. And in a way, of course, he’s right: the reason we still have to support IE7 and IE8 is because we support them. Users won’t upgrade if the web is not broken. But his main message is that we should try to make stuff that’s as great as the things we see in native apps. And that’s the biggest flaw in his story I think: the web is more than just apps, it can do things that apps can’t. But still, a great talk, but rather depressing to see that some things are still impossible, and will be impossible for a while.
The organization decided there should be room for inexperienced speakers so there were some fast tracks. I saw an informative talk about Youtube and how they made sure that videos can be played on all devices out there and a talk where someone was selling his product. I think the fast tracks were an unnecessary interruption of an otherwise excellent conference.
Jason Grigsby gave a very interesting presentation about smart TV’s. Interesting but depressing. The TV’s suck, their interfaces are crappy, resolutions are a mess. The browsers are rather good but there’s no way to detect that it’s a browser on a TV, so actually it is almost impossible to build a responsive website that also responds to the TV. As you can see, there’s a trend here: we want to build great stuff but it is all just so hard. That’s also the feeling I had after Heiko Behrens‘ talk about different platforms for using web technology on mobile: they all are good at some things but never really good enough for what they’re trying to achieve: emulating native apps. The first day was closed with a long panel discussion with mobile browser vendors. Boring, predictable answers by the panelists but nevertheless one of the highlights of the day thanks to the superb moderator Jeremy Keith who did a truly amazing job.
The feeling I had before the start of the first talk on day two was not too positive, and no, it had nothing to do with the beers I drank the night before. The talks and the ideas I had seen left me slightly depressed. Another day like this would probably result in me trying to find another job. But luckily the day started with a fantastic presentation by Scott Jenson who emphasized the things the web can do but native apps can’t do. One of the most important lessons in his talk was that we shouldn’t try to emulate native, we must focus on the things that make the web unique. There are two important things that make the web as powerful as it is: URLs and the fact that it works everywhere, on all devices. And especially that last fact, that the web can just work everywhere, wherever we are, on whatever device we have with us, is the core of Scott‘s thinking. All things will be connected and you can interact with all those things. He showed us concepts of notifications on the home screen of your phone of things that are near by instead of random messages by random apps that probably have nothing to do with where you are right now. A great and inspiring talk, I immediately wanted to start playing with these ideas (I need a Boot To Gecko phone now!). This talk left people inspired, the dip of the day before vanished right away, it was striking to see that even native focused people I spoke to were excited by this talk.
Right after this talk Stephen Hay presented his thoughts on the new web designers workflow, a subject many agencies are struggling with today. I’ve seen many talks by Stephen Hay, they’re all good, but this one was simply amazing. What he showed us are the ten steps he takes to create a design and he told us to just pick and choose whatever we need from it. Not all his steps are useful in all agencies but some of his lessons should be mandatory material for all designers: design from the content out, structure it first, don’t make wireframes, use the talent of the people in your organization (not just the talent of the interaction designer), start designing in the browser as soon as possible, manage the expectations of your clients and document everything.
The next three talks had one thing in common, the people who presented them are from Brighton. It’s incredible, the amount of talent that lives in that town. Remy Sharp gave a some tips on how to test your websites on mobile, he showed some different emulators and some very promising tools he’s developing. For those of us who have been developing sites for mobile phones, yes, it is slowly getting easier. Seb Lee-Deslisle presented his incredible PixelPhones project where he turns the entire audience into a huge screen by using their telephones. Highly entertaining and above all unbelievable, the man is a genius. Jeremy Keith moderated a second panel, this time about APIs and he tried to find the answer to the question why it takes so long to get access to some features of some devices. The answers were slightly less boring than the answers in the browser panel but Jeremy Keith was right when he warned me during the break that it would not be as entertaining.
Up until now all talks were good, some were even amazing but the best talks, in my opinion, were still to come. Jake Archibald stole the show with his instant classic talk about AppCache. A subject that at first seems to be pretty easy but which is extremely hard to get right. Unfortunately the only mistake the organization made was to give Jake just half an hour for his presentation, it should have been the full fifty minutes, it was incredibly funny, intelligent and most important: understandable: we can now start using AppCache, thanks to his talk and his article.
After such an amazing talk it’s hard to keep the audience’s attention. Brad Frost gave a decent talk about a future friendly web which would have been OK on last years Mobilism but which felt a bit outdated. It was a good summary of the articles that have been published about responsive design but I assume that by now this is common knowledge for this specific audience.
One of the highlights was the talk Lyza D. Gardner gave about content. In a beautiful and intelligent presentation she taught us some important lessons about textual content, about the future of content and about what we should do with it. The most important lesson I learned was that we should probably be publishing our articles in Markdown (doing it right now) instead of in HTML. Yes, HTML will be around for a long time but there are other important formats that should be supported and a language like Markdown can easily be ported to (most of) those. Let’s keep our content accessible for future visitors.
Brian Fling had the honour to close the conference with an inspiring and practical talk about the ethos of mobile design. He actually gave away the secrets to what makes a successful app successful: anthropology, technology and design. If you invest enough in those, chances are high your app is successful. If you don’t chances are high your app disappears into the dungeons of the app stores. He gave some beautiful examples of great apps for different Desknot devices. Inspiring but not specifically a mobile web talk.
Mobilism 2012 was again an important conference and it managed to keep up the high standard it set for itself last year, and that’s a good thing. The over all message was not as exuberant as last year, there were definitely some dark messages, but that might indicate that this specific profession, The Mobile Web, is growing up and that answers are being found.
Mobilism 2012 is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
I believe there are many good reasons to use skip links but there are definitely other ways to make content accessible for keyboard users. Here's a nice proof of concept by Thierry Koblentz that uses that tab-key to tab from section to section and the arrow keys to navigate to links inside those sections. Feels intuitive once you find out how it works (yes, I know, that's somewhat, but not entirely contradictionary) and it clearly shows the importance of styling :focus states.
accessibility css html keyboard
The next time a designer ask you to create a pixel perfect design just tell them that you will, only if they can explain what the px unit in CSS is exactly. Just be sure your designer's name is not Sean B. Palmer.
What happens with your data if a service closes down? Can you actually entrust your precious online presence to third party services? Geri Coady writes about the closing down of Gowalla and links to some very interesting articles and video's about the subject of shutdowns.
You don't want to serve a 1024px wide image to a 320px wide screen, that's a silly waste of bandwidth. There is no easy way to do this so a group of web developers tried to work on a new HTML element to solve this issue. A few days ago a different solution was added to the spec without consulting these developers or without considereing the work they had already done. You can understand that not everybody is happy about this. If you're interested in this subject (it actually is very interesting, it's about the future of the web) you should definitely read this article, read about the beautiful HTML design principles mentioned and after that be sure to read this thread too.
Yes, all these new webtechnologies like canvas look absolutely great, but can you actually make something useful with it? Two years ago Simon Willison created this extremely handy canvas tool, I can't wait till we finally see it implemented everywhereM.
This is not just an excellent explanation of the difference between a geek and a CEO (or between a true pioneer and a douchebag), it's also a beautiful essay about one of the greatest inventors ever, Nikola Tesla, lovingly created by Matthew Inman.
One of the hardest parts of responsive design is the fact that we have to change the way we work, we have to change our workflow drastically, the deliverables we've been delivering in the past ten years just don't work anymore. More and more clever people start thinking about this new workflow and Stephen Hay is one of them. On Mobilism he gave this excellent presentation. Just pick and choose the ideas you think will serve you, your team and your clients well. I'll link to the video once it's published, you should definitely see it.
People like to use apps and people don't really care with what technology these apps are built. There are good reasons to use so called native technology for an app on a desktop or desknot computer, there are many good reasons why you'd want to use HTML. Mozilla is working on a Web Run-Time which lets you create launcher-apps for web-pages, here's an in depth explanation on how it works.
No that we finally accepted that we web does not have a fixed width we need to find a new workflow, the Photoshop centered way we used to work is not good enough anymore. People start thinking and publishing about this new responsive workflow, and that's a good thing. Here's an article by Luke Brooker about his new workflow, centered around the idea of style guides.
Here's a handy tool to fix those broken unicode characters like café. In the comments below the accompanying blog post Mathias Bynens scores a few Internet Points by pointing out how you can easily do this yourself with some simple JavaScript.
Keyboard, pixels and goats. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
People obviously find it inspiring to look at the offices of famous web people. What strikes me is that most of these offices are rather small. Bruce Lawson realized there are more small rooms that might inspire you and launched this next successful tumblrblog.
Here's a nice tool that suggests a font stack based on your font. It knows fonts served by Typekit, it doesn't seem to know too many Google Fonts though. Still, a very handy tool.
If you, for whatever reason, don't like any of the other tools and sites out there that tell you what browsers support what CSS feature then this tool might be the one you were looking for. I still prefer When Can I Use… though.
One of the only reasons to keep supporting IE6 is when you work for a company that does a lot of business in China, marketshare of IE6 was always very high over there. This graph shows us that something significant happened a few weeks ago. On the positive side: IE6 usage has suddenly dropped below 20%. On the negative side: IE8 usage is close to 50% now. A long, long way to go.
A while ago a study was presented about the impact of WCAG on user problems which caused a bit of a roar in the accessibility world. According to the study the accessibility guidelines had no significant effect for blind users. Now, before you all start builing your sites with tables again, please first read this article in which Detlev Fischer debunks the study.
Your app needs a map but you want something else than good old boring Google Maps? You could try OpenStreetMap with one of these beautiful map tiles.
Wondering which toolkit to use for your HTML based presentation? Louis Lazaris collects them right here. Do you know another one? Let him know in the comments.
What does browser support mean exactly? Some think it means pixel perfection for a predefined set of browsers. According to David Bushell it means something else. A good read for people (or clients) struggling with the ever expanding browser landscape.
One of the easy ways to get a somewhat unique ID is by using the UNIX epoch time. The problem with an ID like that is that in HTML an ID had to start with a letter. Mathias Bynens tells us if this is still the case in HTML5.
Filling out forms is a pain in the ass and especially on devices without a classic keyborad you should ask your users to fill in as little information as possible. So if there's a way to make things easier you should probably use it. For instance, parts of an address can be prefilled if the user enters her zip code. Chris Coyier shows us what a flow like that could look like.
Here's the true story behind the -tag by the guy who came up with the idea, Louis J. Montulli II. A nice anecdote in early browser history.
A thing we needed desperately before we could use box-sizing: border-box; was the ability to mix different CSS units. There are still some use cases though and luckily more and more browsers start supporting the calc() property. Here's how it works.
Here's a small post by Keith Houston with news and thoughts about unusual characters. Always a pleasure to read, like everything on his blog.
An important part of design and UX is performance so when you decide to use a webfont you should definitely understand what the negative impact of that choice might be for your users. Here's an excellent in depth article about font performance. Yes, you should definitely read it (and read the comments too, they're actually quite good).
My father always scribbles annotations in the margins of his paper books. He's probably been doing this for more than 50 years now and if somehow we could collect these annotations it would be an incredibly intersting and useful database. But as it is, it's pretty useless. Allen Tan writes about this and more in this article about modern, digital reading.
There are a few use cases where's we'd love to use physical units (like cm and in) but unfortunately these units don't work as expected in CSS. Boris Smus wrote an extensive article about these units, how they should work, why we want them and why they work the way they work.
Jeremy Keith started an open, local mobile device lab in Brighton and he urges you to do the same in your home town.
The BBC is working on a responsive news site and they share everything they find out, which is extremely useful. In this article Tom Maslen explains how they manage browser support. An absolute must read for everybody who is struggling with the growing complexity of browser support. This solution (or something similar) should be implemented everywhere.
Here's an overview of projects related to the HTML5 Boilerplate. There's some excellent stuff in there but before you start using everything in there, remember the excellent advice by Rachel Andrew: Stop solving problems you don’t yet have.
You should never just link to scripts hosted on other domains, the possible advantages – caching, gzip – are not always enabled. This gets explained in detail in this excellent article. Yes, you should definitely read it.
Holistic means something like complete. So Perry Chan argues that a complete user experience is the future of mobile payments. I actually think that right now, on the short run, whatever is the future: the things we have right now are just terrible, anything is less painful (at least here in the Netherlands). (I also think the future of UX on the web is bigger fonts, much bigger).
Loading an external JavaScript file can block loading of the rest of the page which, of course, can be a major performance and usability issue. The solution to this issue is to load the scripts asynchronically and Chris Coyier shows the ways to do that, extensively as always.
CSS selectors can be pretty hard to understand, especially the difference between nth-child and nth-of-type can be confusing. There are many tools to visualize the difference, here's another one by Ben Howdle.
Browsers, maps and books. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
I’m really looking forward to how this is going to work out, how it’s going to blend into Smashing Magazine and how this bigger (much bigger) audience will react. We’re still looking for a good name (Smashing Nerds sounds a bit aggressive, don’t you think?) so if you have any suggestions, let me know.
Elsewhere too. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
Jake Archibald wrote this definite article about Application Cache with all the info you need about appCache. Yes, AppCache is hard. But it's also easy to get thanks to Jake's pleasant style. (If you're offended by the word douchebag in the title and refuse to read it because of it, tough shit, you're missing out on some crucial information for modern webdevelopers). An absolute must read.
Here's a great presentation about polyfills by Jason Johnston, filled with links to extra information, links to polyfills, examples and an important section about the pros and cons of different polyfills. You should definitely read it.
Luke Wroblewski collected some possible solutions for working with different screen densities on the web. To the point as always. Great summary.
This is how all apps should work when it comes to privacy and transparency about data collection.
A nice read by Brad Frost for people who think we don't need the web.
Bold and italic @font-face fonts can look ugly. Alan Stearns explains why this happens and he shows us the correct way to solve this issue (no, not by using font-face:normal;).
Cache, polyfills and privacy. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
Today is your last change to buy a ticket for Mobilism 2012, the mobile web development conference in Amsterdam. If you want to meet people like Scott Jenson, Seb Lee-Deslisle, Lyza Gardner, Stephen Hay, Jason Grigsby and many many more, this is your last change (this year). This link will give you a 10% discount.
Here's some (well, a lot actually) advice from Christian Heilmann for people who want to write technical blog posts.
The HTML5 spec tells us that we can use the definition list for any name/value pair. Jonathan Snook did some research and found the most accessible ways to markup these pairs (it's not a definition list).
Looking for a way to set up and maintain small and large projects in a big organisation with many, many developers? This might be the method you're looking for.
This title looks weird. Why would you ever want to use something else than an image for an image tag? A while ago I checked what happens when you use an image as the source of a video tag; it seemed like a handy hack to enable full-screen mode for images (no need to test it, it doesn't work). Apparently some people used the image source to preload scripts and stylesheets in the assumption that this will somehow speed up the page. Eric Law explains you why you shouldn't make that assumption.
Tickets, tips and tags. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
Google published a HTML and CSS Style Guide with some assumed best practices. Zoompf took a critical look at the tips that Google gives from a preformance prespective. A very good read this is! Good to see that Zoompf and Google disagree on some things (I disagree on others, of course).
I wanted to link to an article which – when I looked at the title – seemed to be about the collaboration between front-end development and UX teams. But it turned out to be an enormous pile of utter bullshit. Albert de Klein suggested me to link to this article by Howard Rheingold instead.
Sometimes you'd like your typography to be somewhat related to the viewport size. In the near future you could use some new units just for that. Chris Coyier explains – in depth as always – how they work and more. You should read this.
Performance makes your site feel great and as such it should be part of your design proces. Here's what Jeremy Keith did to make the dConstruct site as fast as it is. You should really read it, especially if you – for some weird reason – think it is OK to make a website bigger than 100K. I like the idea of using performance artefacts as an aestetic and I'd love to see some design centered articles about performance.
Kenneth Auchenberg explains what to do if you really want hyphenation in your webste and you want it to work on as many browsers as possible.
I agree with this title. I know from experience that some things are changing though, at least here in The Netherlands: some universities are actually bringing in professionals, I just finished a ten week course about modern web technologie for designers right here in Amsterdam and a colleague of mine is giving a course about maintainable CSS right now in Rotterdam.
Crap, speed and hyphenation. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
Style guides should be the core of every serious site. If you don't know what they should look like, here's some help: Anna Debenham collects style guides.
Drag and drop is a common interaction. It's actually pretty hard to do with a mouse or a trackpad but it's even harder to implement in a web app. But that's about to change and Mike Taylor explains.
This looks like a great tool for designing graphics, especially great for everybody who doesn't need all features in Illustrator and Photoshop (and be honest, who needs all of them?)
Books with pages were better than book rolls on many fronts but that doesn't mean that paging works better than scrolling. I've always been surprised by the fact that all ebook-readers use pages (and I'm flabbergasted by the fact that Opera is experimenting with some paging techniques in CSS). Here's an excellent article by Mike Swartz about this subject. Everybody (and especially ebook-people and Opera-people) should read it. (This study actually says that the card model works better on novels. Grmpf. Be sure to read it all though before you decide to build sites that look like books)
An excellent, rather eclectic list of links by Bruce Lawson with zombies, localStorage and a children's song.
Here's some excellent research by Jeremy Keith and others to find a way of detecting from JavaScript whether media queries have been executed in CSS without duplicating my breakpoints
. Absolutely usable.
Chris Coyier explains how to prevent CSS transitions to fire on page load.
Date pickers are hard to design. Here's a very nice try (although it doesn't seem to work with my keyboard)
An interesting site: a collection of common privacy problems with some possible design solutions. Working with possibly private content? Be sure to take a look at this site.
The structural hierarchy of a page is not always the same as the visual hierarchy. The visual hierarchy can change on different screen sizes while the structural hierarchy stays the same. Here’s a nice example by Jordan Moore which uses flexbox to achieve that, a lot of this trickery can be done with positioning too and here’s the explanation. You should probably read it.
Harry Roberts explains the single responsibility principle applied to CSS, a must read for people who build big web sites.
The Link Dumps by Blair Millen are always amusing and informing at the same time. Highly recommended.
Creating data-uris can be a tedious task. My colleague Bran van der Meer created this data URI Generator. Just drag and drop all the images you need onto the screen and you're done. I know, there are more generators out there but I haven't seen any that are as fast, simple and functional as this one.
none
Sketching, scrolling and generating. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
Alper explains how you can get a full Twitter index, not just the last 3200 tweets that Twitter usually gives you access to. Only works if you live in the EU.
One of the harder issues to tackle in a responsive design is images: you don't want to serve a huge image if it's not needed. Right now there are no bullet proof solutions, they all have their draw backs. But people are working on a future proof solution and Mat Marquis explains what it is.
In case you missed it a while ago: Opera (and Firefox and IE) decided to support some -webkit-prefixes. Some are angry about it, others defend the decision. I've never seen any actual data about -webkit-specific bling that's not supported in other browsers so I'm a bit sceptical if this was really necessary.
Performance is not just about speed, it's also about battery life. Remy Sharp analyses a paper that's been published about battery performance on mobile devices and translates it to proper English.
Some interesting questions about responsive design answered by Ethan Marcotte. And yes, as you can guess, it's an interesting read.
Sara Wachter-Boettcher looks at ways to structure and reflow content on different screen sizes. A very interesting read.
This looks like a kick ass library for creating beautiful, interactive vector maps
.
Batteries, content and maps. is published on The Daily Nerd.
The Daily Nerd by Vasilis van Gemert is licensed under the Creative Commons Attribution 3.0 Unported license. Use it in another way? You can always ask.
Are you happy with the Daily Nerd? Buy an original Daily Nerd t-shirt!
]]>
]]>
]]>
via http://www.tugboatprintshop.com/onlineStore_DEEPSEA_all.htm
]]>
]]>
]]>
]]>
via http://butdoesitfloat.com/458001/All-the-things-an-artist-must-be-poet-explorer-of-nature
]]>
via http://butdoesitfloat.com/458001/All-the-things-an-artist-must-be-poet-explorer-of-nature
]]>
