Poll: Do you actually use the product you are working on?

Many of us are working on their own projects, side projects or for some companies. And we all know that the best way is to develop/work on a product that we also need/use (eat your own dog food).

Do you need/use it (other than for testing purposes) or are you just developing a product for the sake of doing something?

Feel free to comment what's the product :)

I was writing an IDE that I planned to use every day, and it got to a usable point, but the perfectionist in me wasn't happy with some of the implementation details so I don't use it yet. Whenever Julia's C API matures enough that I can actually get it working, I think I'll pick my project back up and use Julia for most of it instead of C. But no luck so far on that route.

I'm building my product for the explicit reason that I want to use it. Its value to other people is just a (very) nice bonus.

I'm working on a visual web testing automation tool Usetrace (http://usetrace.com).

Our QA process is relying on it.

We're:

- automatically checking our most critical features every time our code changes in our QA environment

- monitoring the end user experience on production environment using the same automated tests every minute

- creating and maintaining the tests with our tool

- getting live feedback to our development team's flowdock chat through our own APIs

Since we offer free VOIP phone calls to US, Canadian an UK land-lines, of course I use it every day! But by using Upptalk almost constantly I've come across hundreds of small bugs and fixes that otherwise I might not have found.

But to be honest, the reason we built Upptalk was not because we needed VOIP telephony, but that we were incensed with habitual overcharging and roaming charges.