Panasonic Youth rob sanheim writes about software, business, ruby, music, stuff and things



Posted
8 April 2008 @ 8pm

Tagged
Business, Usability, Web 2.0

Discuss

If you think Huddle is ripping off Campfire

…then you haven’t seen mIRC, an irc client app that has been around for years:

mirc screen shot

See anything familiar in the screen shot above?

Tabs on the top, list of participants in the right hand pane, and chat in the main window. Change the font to Lucida Grande 12 pt and put in a browser and you pretty much have the Campfire l&f, minus a whole lot of polish and design love. Chat applications tend to follow a pretty standard UI model, and the fact that Huddle took the 37 Signals style is a good thing for Jason Fried and co.

Here’s why: The look and feel from Basecamp and Campfire have become the defacto “template” for web 2.0 apps without a design of their own. There is a good reason for that: 37 Signals develops kickass UI’s. As long as they stay on top of their game and keep their customers happy, they have nothing to worry about from people ripping off their design. The customer who leaves your app for a free one because the CSS is the same is a customer you don’t really want anyways.

Here’s the standard process whenever this becomes public and everyone gets up in arms about it:

  • 37 Signals gets a ton of free press and attention.
  • Paid users for the app in question (campfire in this instance) shrug and say “huh, I’m pretty happy with my service, and I’m not going to switch.
  • People new to both apps who are in the market try both and choose on their merits.
  • The user experience for the 37 Signals’ apps remains superior in most cases, as they are continuously tweaking and improving while copycats are stagnant or trying to keep up.

What exactly is the problem here?

The more interesting point about Huddle, and Google App Engine in general, is the lack of diversity the platform provides for. But please, drop the “Google ripped off 37 Signals oh noess!!!!” angle.


3 Comments

Posted by
Dion Almaer
8 April 2008 @ 8pm

Python is just the FIRST language. I heard that about 5 times during the launch. The backend is a language neutral runtime, and Python has the first bindings, for some pretty obvious reasons. That doesn’t mean that many people don’t want their own beast, and more and more will be coming soon (and with Java bindings you can imagine running JRuby and the other j* languages).

That guys like it hilarious: “Why is Guido even there!!!” I will tell you why, he worked on the project!

Not having features like cron and the long running process thing is very valid. This is not meant to be EC2. It is a way to quickly deploy applications that have the side effect of being able to scale really well.

Some people (and certain apps) like full control. Sometimes you want to get something up and not have to deal with deployment hell.


Posted by
Rob
9 April 2008 @ 12am

Thanks for clarifying some of that Dion, its good to hear that other languages are coming.


Posted by
Steve
16 April 2008 @ 12pm

but..mIRC, the first versions, the tabs were on the bottom :)


Leave a Comment

Zero to a Fully Git Enabled Rails App in the time it takes to drink an espresso history meme onwards…