4 ms·
I like the concept but I don't like your pricing model. For what it is, even $19 a month feels like a lot. I would love to add this to the couple of web apps I
by acron0 13y ago
I like the concept but I don't like your pricing model. For what it is, even $19 a month feels like a lot. I would love to add this to the couple of web apps I run but at that cost it'd run parallel to the cost of my AWS overhead.
Semi-seriously, you should add a PAYG model that costs by the error, thus incentivising me to make my code less error-prone!
- stephanos2k 13y ago> For what it is, even $19 a month feels like a lot. Please read http://wadefoster.net/post/49775946303/startups-you-should-value-software-more http://wadefoster.net/post/49775946303/startups-you-should-v... :) EDIT: What I am trying to say is that the comment is underestimating the value of something like an error tracker, vastly - especially when managing several web apps.
- StavrosK 13y agoThat response can be generalized to "you should always give people whatever they ask". What if he already is valuing the app a lot, but the app just isn't worth the price compared to other apps, or he just doesn't find it that useful?
- acron0 13y agoSorry, I should have said "feels like a lot for my scenario".
- thackerhacker 13y agoWe considered charge-by-the-error, but felt people don't like to be nickel-and-dimed. You'd disagree?
- mtrimpe 13y agoIf you're looking for a simple solution that gets you close some of the way here ... consider mailing every error you get to GMail. I recently discovered that it's conversation grouping works quite decently for error messages.