“Where to Draw the Line” is a clever post by Des Traynor of Intercom.
So much is written about the pursuit of simplicity these days but often there is a confusion. There is a fundamental difference between making a product simple, and making a simple product.
I like the advice to focus on user’s workflow in its entirety. It circles around the jobs-to-be-done approach of which I am more and more fan.
Via @jasonfried
Google’s doodly tribute to Moog synthesizer is really something. Here’s a guide for the UI in JPG.
Of course, what interests us is that it’s done with HTML5 technologies only. I hope someone digs through it and writes about it.
Well, “free” as in “give us an email for it”, but if you haven’t read it yet, you definitely should. Getting Real is one of the best books not just for anyone who wants to build a web application.
wysihtml5 is an open source rich text editor based on HTML5 technology and the progressive-enhancement approach. It uses a sophisticated security concept and aims to generate fully valid HTML5 markup by preventing unmaintainable tag soups and inline styles.
Via @ViliamKopecky
It seems very likely to me that there’s something simple and beautiful lurking inside the browser platform that will hit the greatest 80/20 point in software history. But I’ve been thinking that for a decade or more, now.
– Browsers and Apps in 2012, Tim Bray
Well, from my point of view, there will – in foreseeable future – be area of problems that only native apps could solve. In the same way, there is and – in foreseeable future – will be area of problems that web apps solve better than native apps. I personally think the latter area is bigger in terms of money to be made off but it does not matter much as both are huge and growing fast.
And that’s all not speaking about the “gray” area of mutant native apps using some form of browser integration or web apps using hardware API of the mobile device.
That’s at least Chris Coyier’s advice in article SASS vs. LESS.
“Which CSS preprocessor language should I choose?” is a hot topic lately. I’ve been asked in person several times and an online debate has been popping up every few days it seems. It’s nice that the conversation has largely turned from whether or not preprocessing is a good idea to which one language is best. Let’s do this thing.Really short answer: SASS
Don’t worry this is just the beginning, he does more reasoning than that ;-)
Via @zdenekkostal
Perfect set of tutorials by David DeSandro. A bit of theory and then great examples. Nicely presented too.
Source The Verge
What’s in the new ‘320 and Up’?Five CSS3 Media Query increments: 480, 600, 768, 992 and 1382px
Design ‘atmosphere’ (colour, texture and typography) separated from layout
Bootstrap styles for buttons, forms and tables
Font-based icons from Font Awesome
Modernizr, Selectivizr, responsive type tester and design tester
LESS mixins and variables
Horace Dediu is starting a blog post series worth following.
We need to understand how Google uses Android to make money and whether it is succeeding and if it’s not, why not.
— Android economics: An introduction
