You should turn the "s" in Ducksboard into a duck (logo); if not, people like me will keep forgetting that the letter is there and remember it as "Duckboard".
It's probably the easiest character to draw as a duck, so it's not going to be a big problem. :)
Yes, both are dashboards for online metrics, so they will necessarily be similar.
We believe that our product puts the accents in different places. Two things we put much emphasis on are user interface and true realtime updates. We spent a lot of effort polishing the UI and making sure it's consistent and informative, we're using websockets to deliver updates as soon as our backend gets them.
Check out the demos for both of them and pick the one that pleases you more.
What are the main things that differentiate you from similar products like Geckoboard? Also it'd be pretty cool to get a list of all the widgets that you currently have.
* real time and continuous (even when the user is not connected) data retrieval.
* a very polished UI.
* mail reports and XLS and other formats exports in a near future.
First, we caught bugs (not even regressions) just by writing tests. More importantly, many time when we left code without tests, we found a bug in it later. We're not 100% sure it's been a good investment, but we're 90% sure.
Second, because it wasn't that hard. With the tools available, writing tests that cover all of your code is not too painful.
Third, in private beta we're sure we'll have to change things as we face scaling problems and get failure reports. We wanted to have these tests before we started monkeying around with code.
This looks awesome. I rarely sign up for Show HN's but I just signed up for yours. I run a startup and it's inconvenient to hunt and peck between Google Analytics, Facebook, Twitter, etc to find this info. Good idea to bring it all together. Nice design too. Good luck with it.
Thanks, we'll try to get you an invite as soon as possible but we're still in the "too embarassed to show it to anyone else than close friends" stage :)
Short answer: we're ashamed (if you're not ashamed of what you launched, you launched it late) :)
Long answer: we're inviting close friends first, expanding to people that signed up back when we launched the first teaser and then the rest. As soon as we see how well does it scale, we'll start sprinkling invite codes on HN.
[+] [-] kmfrk|15 years ago|reply
It's probably the easiest character to draw as a duck, so it's not going to be a big problem. :)
[+] [-] wulczer|15 years ago|reply
Anyway, I hope that this exact conversation will make you remember it's duckSboard.com ;)
[+] [-] aitorciki|15 years ago|reply
1. The first batch goes to close friends. This is not favoritism, we just feel more comfortable sharing the rough edges with them :)
2. The second batch will go to people who helped us validating and testing.
3. Lastly, we will provide invitations on a first-come/first-serve basis (you can subscribe from the site's sign up form).
We will give out the invites as fast as we can… but be patient!
[+] [-] andypants|15 years ago|reply
[+] [-] wulczer|15 years ago|reply
We believe that our product puts the accents in different places. Two things we put much emphasis on are user interface and true realtime updates. We spent a lot of effort polishing the UI and making sure it's consistent and informative, we're using websockets to deliver updates as soon as our backend gets them.
Check out the demos for both of them and pick the one that pleases you more.
[+] [-] biaxident|15 years ago|reply
What are the main things that differentiate you from similar products like Geckoboard? Also it'd be pretty cool to get a list of all the widgets that you currently have.
[+] [-] aitorciki|15 years ago|reply
To answer your question, our main assets are:
[+] [-] gavinballard|15 years ago|reply
Are you planning on providing a means to create custom widgets?
[+] [-] aitorciki|15 years ago|reply
Custom widgets are currently our top priority.
Expect it to land in the next few weeks.
[+] [-] k7d|15 years ago|reply
[+] [-] wulczer|15 years ago|reply
First, we caught bugs (not even regressions) just by writing tests. More importantly, many time when we left code without tests, we found a bug in it later. We're not 100% sure it's been a good investment, but we're 90% sure.
Second, because it wasn't that hard. With the tools available, writing tests that cover all of your code is not too painful.
Third, in private beta we're sure we'll have to change things as we face scaling problems and get failure reports. We wanted to have these tests before we started monkeying around with code.
[+] [-] dgurney|15 years ago|reply
[+] [-] wulczer|15 years ago|reply
[+] [-] Spines11|15 years ago|reply
[+] [-] wulczer|15 years ago|reply
[+] [-] timjahn|15 years ago|reply
Hope I get an invite. :)
[+] [-] MatthewB|15 years ago|reply
[+] [-] troels|15 years ago|reply
[+] [-] pmjoyce|15 years ago|reply
Welcome to the space :)
http://betali.st/startups/streamer http://www.streamerapp.com/
[+] [-] dmarinoc|15 years ago|reply
Ask them ;)
[+] [-] markbao|15 years ago|reply
[+] [-] wulczer|15 years ago|reply
Long answer: we're inviting close friends first, expanding to people that signed up back when we launched the first teaser and then the rest. As soon as we see how well does it scale, we'll start sprinkling invite codes on HN.
[+] [-] paulnelligan|15 years ago|reply
[+] [-] noodle|15 years ago|reply
[+] [-] wulczer|15 years ago|reply
We have a fix that we'll apply in a few minutes. Thanks!