Don’t waste too much time on picking a perfect name for your product. It doesn’t matter very much.

One thing we learned early on talking to Basecamp customers: Many of them didn’t even know that the app was called Basecamp. They called it “GroupHub” or “ProjectPath” because that was their project URL. Didn’t stop them from using it (or paying for it) though.

And what about picking a name that’s available as a domain? HighriseHQ.com and Backpackit.com have worked fine for us. Search is the way most people wind up finding us anyhow.

Obsessing over a name is an easy time trap to fall into when you should be focused on more important obstacles (i.e. building something that people truly want to use).

Matt, 37Signals

However you feel about the concept of designing in the browser, the reality is that more and more designers are adopting this as part of their workflow. Some, like Andy Clarke, treat it as the biggest part of the design process, allowing the client to see flexible layouts, type, and rendering engine treatments on the fly as a design comes together; others, like me or Mike Kus, use it as an extension of our Photoshop work: initial design is done offline and is completed by filling in the gaps while in the browser. It’s certainly not my intention to write about the merits and pitfalls of designing in the browser here, but the key point is that if you don’t know how to write HTML and CSS, it’s an avenue that’s completely closed off to you. The design process can begin and end entirely in your graphics app, but because websites will not (and should not) look the same in every browser, the design will not actually be complete until it’s coded.

- Elliott Jay Stocks