Re:Show HN: Errorception - High performance JavaScript error...
by rakeshpai on Tuesday December 06, 2011 @08:40AM
(#3319192)
Thanks for the feedback, Clay.
I considered that model for a really long time. But there were two problems with it. (a) Actually just handling large amounts of hits wasn't really a huge cost for me, and (b) I don't think the usefulness will reduce for people who actively deploy regularly.
If people don't deploy regularly, they'll likely be happy with the free plan anyway. :)
Re:Show HN: Errorception - High performance JavaScript error...
by richardmarr on Wednesday December 07, 2011 @04:39AM
(#3323154)
Charging per exception also adds a nice synergy to bugfixing.
If your product works and adds value, it will result in the reduction of exceptions. A reduction in the number of exceptions will result in web sites requiring a smaller plan. Smaller plans will result in lower revenue. The more useful your app is, the less money you will make (a bit of a generalization but you get the point).
Could you not migrate to page loads? Fire off an event on every page, regardless of whether or not there was an exception?