Skip to main content

Mobomo webinars-now on demand! | learn more.

UI Kits are commonly found in most designer's toolboxes. We use them to bootstrap visual elements of a product before diving into the harder work. They are not as common with developers though, and in the spirit of this weekend's Betascape event of joining Art *and* Technology, I'm here to advocate for UI kits as a simple bridge between the design world and the development world.

Typically, every project goes through three main phases: Discovery, Design and Development. Although each phase defines a distinct position in the process, they do intermix. Generally, development starts as early as the Discovery phase, design continues to happen throughout all phases, and new requirements from the client pop up long after the Discovery phase is complete. This three-phased process is natural and effective but could be kicked up a notch by integrating a UI kit to the discovery phase.

UI Kits are packed with features that enable stylized rapid development. Bootstrap, a UI kit that was recently released by Twitter, is an all-inclusive HTML and CSS style guide that includes forms, alerts, block messages, grid columns, and even flyout menus - many of the elements that are often put off during the initial design and development process of a web app.

Using a UI Kit will completely change and enhance your design and development experience. Here's how:

  • Product Aesthetics: During the initial phase the client usually receives a few rounds of prototypes before the final approach is decided upon. With the aid of a UI kit developers can work with styles before they've even begun to work with their models and controllers, leading to better looking iterations and proofs of concepts. Adding enhanced design elements to otherwise graphically sparse POCs gives the client a better feel for their product before it even becomes a product.
  • Survival: There's a half-serious theory that babies are cute so we won't eat them. Your application, even in its infancy should be something to behold. Applications that are visually pleasing will naturally inspire the creativity of those working on it. UI kits give you style guides that include typography, palette guides, and forms so you can quickly add visual organization and style even during the rapid prototyping stages. Pretty applications are just more fun to work on.
  • Cohesive Teams: Getting a base user interface in place at the beginning of a project opens up communication and collaboration channels between designers and developers. The development team will have an earlier idea of the UI approach and be able to align the engineering of the application more closely with the design vision. Disconnects between architecture and UI will be revealed earlier in the process, allowing greater flexibility for changes and tweaks.
  • Promotes Creativity: With a good UI kit designers can put layouts together with ease and then spend their time pushing the bounds of creativity rather than pushing pixels.

A UI kit is something that should be in every designer *and* developer's tool box; it should especially be a core part of your team's Discovery phase. It allows the product to take visual shape earlier in the process, aiding both designers, developers, and the client. Style guides take care of the heavy lifting on the front-end, enabling the artists and the scientists to collaborate more effectively.

Categories
Author

2010 was a big shift in work environment for me. I migrated from an office to a completely distributed and remote team at Outspokes and then to Intridea later in the same year. Many of my daily tools stayed the same, but there's been plenty of additions to streamline my work. Here's an overview of my most used tools for web development.

Chrome

I switched to Chrome as my personal use browser, but stuck with Firefox because of Firebug and other extensions. Chrome was snappy in daily use, consumed less resources, and just plain felt better than Firefox. Once I learned about the available "Web Inspector", the switch was complete. Nowadays, I only open other browsers briefly for testing.

Skype

Instead of holding meetings in person, Skype is now always open for conference calls. Meetings are scheduled in Google calendar, and if screen sharing is needed, then we pop open a GoToMeeting.

Presently

I used Yammer briefly while at Outspokes, but none of us got into it very much. At Intridea, there was so much more knowledge and information that needed to be shared between projects and team members that I saw the real value of micro-blogging for the first time. On a remote team, it's also a great way to share a virtual water cooler and hang out with your co-workers.

Propane

Campfire client for OSX. I don't use Campfire for all my projects, but when a client requests it, then I can keep separate tabs. The integrated file upload and download is nice too.

Textmate

I grew up on Emacs, and I still use it frequently, but Emacs and Vim are both kind of clunky and doesn't fit in with the rest of the Cocoa environment.

Gitx

Simple way to stage and unstage changes. I know there's fancier apps that integrate with Github, but for the time being, this app has just the right amount of features for me.

Cloudapp and Skitch

I use Cloudapp for ultra-quick screenshots and file uploads. When I need to draw a few arrows and text, I open up Skitch and drag the image up to the Cloudapp menulet. I know Skitch has built in sharing, but the Cloudapp one feels more polished to me. Both are great apps I use all the time.

Divvy

Divvy lets me quickly tile a bunch of windows. It's just a single feature, but it's an awesome single feature.

Pixelmator

I don't do very much graphics work, but it's nice to have an app that lets me whip up a quick background, or tweak an existing image asset.

HTTPClient

Great way to test APIs and inspect HTTP headers.

MultiFirefox

When I do need to test multiple versions of Firefox, MultiFirefox is a kickass simple utility for launching different versions with different profiles.

VirtualBox

For IE testing, I've tried Fusion, Parallel, and VirtualBox. Out of the 3, I think VirtualBox has been the least buggy and simplest. It might not have bells and whistles, but honestly, I just want to boot Windows and load shudder IE6 and 7. As an added bonus, there are libraries for controlling VirtualBox programmatically.

Do more with less

I'm open minded about trying new apps, but more tools doesn't always mean more productivity. These apps represent a greatest hits list for the past year. It's not a comprehensive list, but if any of these apps disappeared, I'd really be hurting.

Categories
Tags
Author

Try as I might to avoid it, there comes the inevitable point in a project when I have to start doing browser compatibility. Plenty of people use VMWare Fusion or Parallels to run Windows and OS X side by side, but I find them both slow and unreliable when it comes to real testing scenarios, which leaves me with the necessity of creating a Windows development stack for Rails. After some considerable looking, I’ve settled on what I consider to be the “best” tools for the job – though they still fall short of the OS X equivalents.

  • Ruby/Rails: I use the full recommended Ruby distribution as opposed to InstantRails or similar to provide maximum flexibility and customization. I also use the MySQL Community Server for the database portion of my development stack.
  • Version Control: TortoiseSVN is a very easy to use SVN front-end, but my fingers have long since learned the console commands and continue to crave them, so I use the Apache 2.0 binaries for Windows to allow me to use SVN from the prompt.
  • Console: An absolutely indispensable application for me is Console. This open-source app provides tabbed command prompts in a much prettier interface with a number of other incredibly useful features. I highly recommend it.
  • Editor: This isn’t a slam dunk, but the closest thing to TextMate in Windows is, well, the app that was created to be TextMate for Windows. E Text Editor is very good (though in my opinion still too buggy to be called a 1.0) and comes the closest to approximating my Mac development environment. The heavier IDEs such as NetBeans and Aptana With RadRails are also viable options, but I like the speed and simplicity of E.
  • Debugging: Since the reason I end up in Windows in the first place is usually IE compatibility, I need tools to approximate the incomparable FireBug. For markup inspection, the most-helpful-least-hurtful I’ve found is Microsoft’s own Internet Explorer Developer Toolbar. Javascript debugging, the most heinous of all tasks, is made much less painful by the Microsoft Script Debugger. Don’t let the “Windows NT 4.0 and later” fool you, this is the most useful thing I’ve managed to find to get some kind of control over IE Javascript debugging.

These aren’t by any means the only tools available, and your needs/mileage may vary, but after finally getting this stack together I can develop in Windows without going into fits of hyperventilation and frustration. If you have your own indispensable tools for Rails development in Windows, I’d love to hear about them!

Categories
Author
1
Subscribe to Tools