Currently, I'm a Product Designer at a SaaS company and so far I have always worked whether as a designer or a developer. The initial idea for Bardo came up around 2012. When I started to work for an agency the pain for an app like Bardo became bigger and bigger. I always had problems estimating my own work because I lacked experience.
After all these years in the industry, I found out that it's not just the lack of experience, it's human.
We are not good at estimating. Especially not when we are doing something for the first time and times like these sometimes require us to solve even more complex problems.
To tell you a bit more about my intetions with Bardo I created a small FAQ:
No. It's me, working on code, design, user research, marketing. You name it.
Currently, I'm juggling a dozen balls at the same time.
To quote Wikipedia: "In some schools of Buddhism, Bardo is an intermediate, transitional, or liminal state between death and rebirth." Basically, a state where time is unimportant and is no hassle anymore - get the idea? :)
I want Bardo to be something like Quora and Wikipedia for tasks.
The administration of projects or products shouldn't limit you, a team or a company.
No, currently I'm building it whenever I find time in the evenings after work and on weekends.
No. I want to quote Pieter Levels here:
"Remember all those cool startups you used that were free but then they were acquired, shut down and now don't exist anymore? It's because free apps don't make money, and therefore can't survive."
Maciej from Pinboard wrote the following:
Someone builds a cool, free product, it gets popular, and that popularity attracts a buyer. The new owner shuts the product down and the founders issue a glowing press release about how excited they are about synergies going forward. They are never heard from again.
Whether or not this is done in good faith, in practice this kind of 'exit event' is a pump-and-dump scheme. The very popularity that attracts a buyer also makes the project financially unsustainable. The owners cash out, the acquirer gets some good engineers, and the users get screwed.
To avoid this problem, avoid mom-and-pop projects that don't take your money! You might call this the anti-free-software movement.
If every additional user is putting money in the developers' pockets, then you're less likely to see the site disappear overnight. If every new user is costing the developers money, and the site is really taking off, then get ready to read about those synergies.
To illustrate, I have prepared this handy chart:
What if a little site you love doesn't have a business model? Yell at the developers! Explain that you are tired of good projects folding and are willing to pay cash American dollar to prevent that from happening. It doesn't take prohibitive per-user revenue to put a project in the black. It just requires a number greater than zero.
I love free software and could not have built my site without it. But free web services are not like free software. If your free software project suddenly gets popular, you gain resources: testers, developers and people willing to pitch in. If your free website takes off, you lose resources. Your time is spent firefighting and your money all goes to the nice people at Linode.
So stop getting caught off guard when your favorite project sells out! “They were getting so popular, why did they have to shut it down?” Because it's hard to resist a big payday when you are rapidly heading into debt. And because it's culturally acceptable to leave your user base high and dry if you get a good offer, citing self-inflicted financial hardship.
Like a service? Make them charge you or show you ads. If they won't do it, clone them and do it yourself. Soon you'll be the only game in town!