Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 5,972 | Comments: 44,518

filter by tags archive

Deal Breakers

Occasionally I get to try something that sounds really good, but it falls on the execution because of the small details. Let us take FireFox Prism as an example. The idea is good, I get a separate fire fox window just for gmail, or other always on apps. Note that I am using it as an example only, because I just run into it. Prism is still in beta, so it is just an example.

This means that if the browser crash I don't lose my unsaved email, and more importantly, I can close FireFox (and thus release the memory) without closing my mail.

Here is why I wouldn't be using it for now:

 image image

Can you spot the difference between the two images?

The Prism one is on the left, FireFox is on the right. The Gmail on Prism doesn't display a caret symbol in Gmail's rich edit box. That is a deal breaker for me, because I can't really type without it.

I. Can't. Type. Without. The. Caret. Period.

The point that I am trying to make is that you need to consider the deal breakers for the user. And even something as small as the caret is a deal breaker.

In my last project, the first release was completely useless to some of the users, because a select list didn't contains all the old values, and we couldn't bring those values, because their presence depended on so many other things. Those users had to wait for the second release to use the application.

Deal breakers are the other side of the killer features, and are just as important when you analyze a solution. Examples of deal breakers in typical software include:

  • Not supporting the old application's keyboard shortcuts
  • Web application replacing local app - latency
  • Different fonts (True story!  Priority 0 bug!)
  • Compatibilities



This is probably due to a known bug in Firefox where the caret disappears in forms sometimes. This is supposed to be fixed in the next major release.

Ayende Rahien

I actually never had that with FF

Brad Mead

Which is why I'm always nervous realeasing apps into the "wild" for the first time in my current development paradigm. Sure X,Y and Z purse holders have approved it... but how will the bulk of users react?

In a recent discussion the notion of agile's "iterate often and verify assumptions" jelled for precisley this reason... it's not just about the qulity of the code; it's about the quality of the user experience too.


THis has more info on the bug:


Aaron Jensen

I've got a cursor in prism. I wouldn't consider using it for gmail though because I lose my addons (Better Gmail) support. I'm using prism now for Campfire and it works great (RIP Flare)


I just made .netPrism with drag drop in 2 minutes... really...

Jon Davis

What about dropping menus altogether for some less-structured look-and-feely thing... coughOffice2007*cough If it wasn't so beautiful and fuzzy it would have been my deal-breaker.


The cursor issue has been fixed. Download and reinstall Prism 0.8.

Comment preview

Comments have been closed on this topic.


  1. Reducing parsing costs in RavenDB - 14 hours from now

There are posts all the way to Aug 04, 2015


  1. Production postmortem (5):
    29 Jul 2015 - The evil licensing code
  2. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
  3. API Design (7):
    20 Jul 2015 - We’ll let the users sort it out
  4. What is new in RavenDB 3.5 (3):
    15 Jul 2015 - Exploring data in the dark
  5. The RavenDB Comic Strip (3):
    28 May 2015 - Part III – High availability & sleeping soundly
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats