Show HN: EventLog - My first web app
Hey everyone,
I'm really excited to be sharing my first web app with you all, EventLog. EventLog is a tool that lets you track different events through your many applications. A little like Airbrake but not just for errors.
I have built out an API to log messages to and there's also a PHP library out there to make it even easier to integrate apps into EventLog.
I've also built a notifications system so you are notified of all the events logged hourly or daily.
Please check it out and let me know what you think.
Thanks.
http://www.eventlogapp.com
14 comments
[ 2.5 ms ] story [ 34.4 ms ] threadAlso, the front page design is, well how can I put this, bad. Would I pay for a service like this? Maybe, but then I question the integrity of the company. If someone puts out a half-ass design, what does that say about the company? Why should I trust you (the company). Also, I'd rather you include a link to a contact us page or something, putting your name on the page makes it feel like this is a one-man show (which I'm sure it is).
Instill some confidence in me and don't make this seem like you're an overnight sensation who might not be around months from now. I dont want to give up my credit card to someone working out of their bedroom. You use the word "We" alot, but at the bottom you said this app was developed by "Adam Griffiths." So, which is it? Did you make it or do you really have support people behind this? If I'm sending crucial log files to you, I need you to be able to support this when I need you to.
I'm not hating or trying to put you down but these are some of the things I've noticed. A well-design site wouldn't be the only reason why I would select a particular company, but it goes a long way to tell me a company is legit. I refuse to sign up for sites that don't show a support link or contact info. Who can I reach if I need help?
Thanks.
Volume is what costs you more hosting dollars. It's also a primary indicator of your customer's need for your service, and his ability to pay for it.
Restricting access to your other features only makes your service less useful on the low end, which is where you're supposed to be winning customers. It also sets up perverse incentives that leads to e.g. piggy backing multiple real-world applications into a single app on your site, having users share accounts, etc.
You should be looking align your incentives so that you succeed when your customer succeeds. Charging for volume does that.