Browsersync vs CodeKit

It is not constrained to a single device, it works across desktop and mobile devices at the same time. It will update code changes, synchronize scroll positions and form inputs automatically across all browsers and devices.

When filling out a form in one browser, same information will be repeated in other browsers.

Browser-Sync has been tested to work with desktop (Chrome, Firefox, IE 7-10, Safari, Opera) and mobile (Android, iOS, Windows Phone, Opera Mobile, Firefox Mobile) browsers.

Works on Windows, Linux and OS X.

Once the monitored .css file is saved, changes are implemented without a refresh.

Licensed under MIT.

Remembers scroll position and synchronize it across all browsers so you don't have to move to the appropriate part of the page after each reload.

To install as a standalone npm package

npm install -g browser-sync

To install as a grunt-plugin

npm install grunt-browser-sync

When navigating in one browser, other browsers will automatically follow to the same place.

BrowserSync does not require a browser plugin to be installed. This is because it serves the files directly itself, and uses a script which opens a socket between the browser and the server.

Browser-Sync works with all supported IE versions - IE7 and up.

Everything you need to get a project started is included with CodeKit. Thanks to the professional support, different components of the workflow pipeline are guaranteed to play nicely with each other without you needing to do the research on how to configure them.

More advanced features that may require extra configuration to set up with other workflow wrappers are set up out of the box in CodeKit, like automatic browser updating, linting, and source maps.

CodeKit has a clean and intuitive graphical user interface out of the box. Most other tools in this category run as command line utilities or require unsupported third-party plugins to run with a GUI.

The CodeKit GUI makes it easier to navigate and manage the various components of your project with helpful UIs like dropdowns, and views that provide extra details without having to run a separate command.

CodeKit has live updating built in and will update monitored files across multiple browsers and devices, and refresh CSS without a new page load. Other workflow wrappers have live updating, but they require extra configuration. With CodeKit, everything is set up for you so you can get it up and running in no time at all.

You can navigate your project directory, and use a menu form to set up how it gets compiled without needing to read configuration documentation, or deal with configuration errors. On top of that, file watching and recompilation is built in with no extra configuration needed.

At a one time cost of $29, it's a great deal considering how powerful and easy to use it is.

CodeKit provides a clean GUI for Bower that makes it easier to navigate and get information about modules without having to deal with a command line interface.

You can use it to, for example, live-update server-side PHP by establishing a connection with your local MAMP server.

Autoprefixer automagically adds vendor prefixes based on latest information.

CodeKit provides a powerful tool to automatically reduce the size of compressed images and production web code.

CodeKit supports live compilation of Less, Sass, Stylus, Jade, Haml, Slim, CoffeeScript, JavaScript and Compass including automatic debugging and minification.

Install 6,000+ Bower components with a single click: Bootstrap, jQuery, Modernizr, Zurb Foundation, even WordPress.