Develop for Chrome first
Creating a new site for desktop users? Jonathan Smiley tells you why developing it in Chrome will give you the best overall experience
This article first appeared in issue 222 of .net magazine - the world's best-selling magazine for web designers and developers.
Chrome isn’t the most popular browser, and it doesn’t have the best developer tools, but it’s still the best overall development experience with the brightest future. Let’s talk a little about how and why we do it at ZURB, and why it’s better than everything else. Why develop for Chrome first? Speed, experience and mindset.
Prototype faster
You know what the best way to get things done is? Do them. Glib, but true – if you’ve got a problem in front of you, you don’t need barriers standing between you and getting something done. By developing in Chrome you can prototype faster and get a page, a site or an app built quickly so you can click around, get feedback and iterate.
Chrome not only has great standards support (so the pages you write show up as they should the first time), it supports advanced features that help you build quickly at a high level too. Ever made buttons with sliding doors? Want to do that again, ever? Of course not. Use Chrome and write some quick buttons with padding, border-radius and WebKit-gradients. Create navigation elements with a <nav> tag. Denote sections of the page with <section>. Your code is easier to read and iterate on, the page looks correct and it looks good.
Enjoy coding
We, as web designers, have a great job – we get to work on cool problems on a rapidly evolving medium and at the forefront of technology. The underlying implementation of the cool stuff we do should be fun, and when you develop in Chrome it is. Things work as they should. They look good. They’re fast and when they fail you can use powerful developer tools to find out why.
Other browsers have merit, don’t get me wrong. Firefox 4’s engine is very, very fast (even if the browser itself is still bloated and weighed down with more chrome than any app should reasonably have). Firebug is a great tool for developers and is better than the built-in Chrome tools, though that will change with some upcoming Chrome enhancements (check the nightly builds to see something amazing). Safari has better text rendering. Opera is still the best for standards. IE is ... Well, IE9 is alright, so that’s something I guess? Chrome doesn’t have it all, but it has the most, and you’ll enjoy working in it best.
Look forward
OK, this is the big one – and the least tactical reason to use Chrome. It’s the future. It has the brightest prospects, the most buzz and the fastest pace of any browser on the market. If you build for every cool thing that’s going to happen online, you’re ready. Building forward for the growing user base isn’t just more fun, it’s smart. Build backwards and your app is dated before it’s out of the door.
Sometimes we have to look back. Clients need IE7 support, Firefox still has more market share than Chrome and things need to work for more than just 16 per cent of the web. But don’t start by looking back – start by looking forward. Build for what’s hot, what’s new and what you enjoy working with. If you build for Chrome, you’re ready for the future and hey, bonus – 95 per cent of what works in Chrome works in Safari, Firefox, iOS, Android (which uses WebKit, the same engine as Chrome), and even newer IE. Deal with the remaining five per cent after you’ve prototyped, iterated and refined your site or app.
My love affair with Chrome didn’t start until a little over a year ago, when it stopped being a buggy (but fast) browser for nerds and became a robust, powerful browser for everyone. Since then, Chrome has advanced at breakneck speed, adding features and advanced HTML/CSS/JS capabilities that other browsers are barely keeping pace with (or failing to keep pace with at all).
I develop in Chrome first and I enjoy doing it. I’m not here to tell you Firefox is a bad browser (it’s not) or that supporting just Chrome is a viable plan (it’s usually not). It’s about staying scrappy, enjoying your work and looking forward. Try it out if you haven’t already – I think you’ll get a lot out of it.




23 comments
Comment: 1
I recommend not doing this. Chances are you’ll forget the gradients for other browsers later. Write the code with all browser-specific prefixes right from the start!
“Firefox 4’s engine […]”
What Firefox version are you talking about? Did you mean Firefox 14? ;-)
“[…] and the least tactical reason to use Chrome. It’s the future.”
A monopoly of one single browser is not the future (I hope).
Comment: 2
This is an opinion post and nothing more. You havnt backed up at all why people should, in your opinion, use Chrome.
Comment: 3
I understand that you are not critizising other browsers or saying that Chrome is better than others. But after 12 years of developing web sites I would never ever try to develop for Chrome first. The reason is simple and you said it: It's not the best browser for developers.
Firefox is better than Chrome for developing, the list of reasons is so long that the admin of this web would have to censure me because it would take me hundreds of words to say it...
Comment: 4
Comment: 5
But the whole premise fails on the one line: "Firebug is a great tool for developers and is better than the built-in Chrome tools..." Um, well, that's like 90% of the reason why I build in Firefox first, and while I'll continue to do so for the foreseeable future.
Comment: 6
Plus, my fingers cramp up every time I have to type "-webkit-" while writing CSS. I rarely have need for tools such as Firebug, but in the event I do, Dragonfly satisfies that need quite nicely. And I still have some aversion to how Webkit used to mishandle a few very basic ECMA items.
Of course Opera has introduced a whole host of bugs recently, and it pains me every time I see a new release without fixes applied (non-sticky Ctrl-F is the most annoying). But as a dev tool, Opera and the F12 key are my best friends!
Each to their own, I guess :)
Comment: 7
Comment: 8
You say: "things look as I expect them to which cannot always be said for Firefox these days" and this is ABSOLUTELY WRONG, that means that you don't know Firefox at all.
Firefox is always one step far from Chrome. Opera also is one step far from Chrome.
Considering that a foundation of less than hundred people (Mozilla) can mantain a better browser than a billionary company (Google) means a lot of things. They care about Web Standards, semantic web, focus on user and also developer, etc.
Firebug is 1000 times better than the Chrome imitation of it (they only copied it).
Using Chrome for development it's like abandoning development itself.
Comment: 9
You think your life is constrained as a web developer, come sit in my chair. lol.
Even though I think he did a terrible job of backing up his reasoning, I def. stick with Chrome first and then adjust as necessary.
Comment: 10
-webkit- in not this... but ut seems a world that so much of us hated...
Comment: 11
I just don't want to imagine a world in which Chrome would be the most used browser, it's always the same rubbish... Apple and Google writing the rules. And you follow them like blind people...
Keep on giving them the power to decide, It doesn't surprise me...
Comment: 12
Comment: 13
I find that 99.9% of work I do in Firefox works on Chrome anyway, so it should be a win win.
Comment: 14
Your mileage may vary. Thanks everyone for chiming in, I understand my Twitter handle @smiley is not ideal for long-winded diatribes but feel free to ping me there anyways.
Comment: 15
Comment: 16
Recent "updates" to Chrome have broken the Developer Tools for me. Moving to newer nightly builds, same problem. No option to turn off automatic updates. Gay as hell. The main problem for me is editing CSS on the Developer Tools pane, and it not making any effect to the elements on the page (requiring a browser reboot for it to start working again). So - I've switched to Safari! Some things are not as great, i.e. I like to be able to open a tab and jump straight to searching Google OR typing a URL without having to click my mouse; 1 universal input box just makes sense to me. Apart from that - Safari is just as quick for developing, and is now (slightly reluctantly) my top choice for day to day front-end development.
Another annoying thing about Chrome is that for Mac OSX versions, text-shadow used to crisp up the fonts and actually make them look nice and sharp. With the latest version they removed that, so the fonts look just as bold and blurry as every other browser now. Thumbs down Google!
Comment: 17
Comment: 18
Granted Chrome's console isn't great when playing with DOM elements and outputting values to the console can prevent the Web Inspector from updating, but a quick reboot will fix that. The alternative is to load up firebug and debug as if you're on an old Cyrex 266 ;-)
Comment: 19
Comment: 20
Firefox might not be faster than Chrome, but has more tools for developing and it doesn't belong to a company that wants to rule the world.
What sucks me up about web and mobile developers and designers is the lack of ethics we have in general. We don't care about companies and it's behaviour, we don't consider if Mozilla is a foundation and Google is a fuckin' billionary company. We care about the market, the users, and the money, that's all.
I don't understand why, having Firefox I would have to use Chrome rubbish.
I don't understand why the fucking Steve Jobs has to be more famous than Wangari Matai or Masanobu Fukuoka.
This fucking guy (Steve Jobs) was responsible for exploiting milions of people all over the world and also responsible of exploiting Democratic Republic of Congo and mantaining the civil war by buying Coltan. And also a man obssessed in his job, is this the kind of person (model) we wanna follow? Not me...
This fucking web development world sucks me up, although I've been web dev and designer for more than 12 years I consider myself an stupid, like all web developers and designers.
We are simply brainwashed human beings.
Chrome will never ever be better than Firefox, I told you once, and I will repeat it again: MOZILLA is a FOUNDATION that cares about the user and the developer, NOT MONEY.
Comment: 21
Comment: 22
Anyway, I would say that the best browser to develop in would most likely be internet explorer. I don't use IE and I don't like it but if you can get stuff to work in IE then it will most likely work anywhere. Chrome is excellent and I love using it but the problem is it will run any old code! I suppose that is one of the things that makes it good to use. Masses of people still use IE though and this is most likely due to the fact that IE comes with windows.
I came to this conclusion because I was developing websites using Chrome to test them but then realised my error.
One of the most awkward things about website development is getting your site to function well in all browsers. So far I have found that IE is the most picky and awkward browser to get things to work in, so I would like to reiterate my earlier point... if it works in IE it will probably work in the others :).
I am always willing to see a different viewpoint though.
Comment: 23
Also, I mean't to say "develop for" as opposed to "develop in".