Back in September 2014 I came up with an idea: Vibite.
At the time I'd been a music enthusiast for several years; this was one of my first business ideas. And because of this I'd listened to and found a ton of good music.
I came up with the idea of creating a music blog where I could share the best music I found into an assortment of playlists for different scenarios. Things such as 'rainy day vibes', 'working out', and different genres.
It went pretty well. I promoted it with my friends and on the comments for music videos on YouTube. I had some decent feedback and traffic initially, but after about 6-9 months it died out because I slowly stopped working on it.
Since the beginning I've always had a vision of building a social network for music enthusiasts to share really good music with each other—not just me and my music on my blog.
That idea has stuck with me for years and has come a long way, but I've still barely done anything on it. It's time for that to change.
How the idea progressed
Since the inception of Vibite the idea has gradually evolved in my mind. I've worked on several other projects and things over the years.
I've doubted it a ton, too. This is partly because I haven't yet figured out a business model for it, and I don't want to waste my time building something if it's not going to work.
But as the idea developed over time, I began to see what it'd look like more clearly which gave me confidence in it. A few music enthusiasts I've met since have also told me it sounds awesome and were genuinely keen to use it which helped a ton too.
And unlike back when I made the blog, I'm a full-stack developer now, so I can actually build the thing.
My struggle building the project
Around July last year I finally sat down to build it. But after ~600 recorded hours of work it's still not finished. That's a ridiculous amount of time and I have little to show for it. Here's why.
First of all, I was suffering from severe depression which cut my productivity in half. I'm not going to go into that, but it was basically a grind and working was very difficult.
Secondly, I didn't have focus. I had a vague idea of what I was building, leading to procrastination and perfectionism. I had a huge list of features and the project scope was ridiculously unrealistic.
Thirdly, I had to learn a ton. This project required me to not only code the front-end and back-end, I also had to design the project. I'd never designed the UI for an app so it was very challenging for me.
And lastly, one of my goals was to improve my skills as a developer through implementing new skills into the project. So plenty of that time has been spent honing my skill-set.
What I managed to complete
Barely anything—or at least anything tangible.
Despite the fact I still don't have a product to show for it, I've learned a ton from the hundreds of hours spent designing and thinking about the project.
This is something I especially realised after reading Talent Is Overrated; deliberate practise is an arduous yet necessary process to become great at anything. So if you spend 600 hours on something and have nothing to show for it, you just need to keep going.
Most of the time spent has been on designing the UI. I still don't know what it looks like exactly and I was being a huge perfectionist. Here's a pile of all the sketches I've made:
I've also attempted to build the UI like 3-4 times. Here's a screenshot of one of them:
Besides that there's some front-end code, but not much.
What's happening from here
I've decided to set myself a deadline of 30 days and build the thing. So long as I let it drag on I'll never finish it.
Starting tomorrow, the 4th of May, 2018 I'm going to start building it with a 30 day deadline (June the 3rd). This strict deadline will force me to build a MVP and get it out there.
The details and other features I'd like to add can wait. The longer this drags on the more I procrastinate, whereas getting something out there will inspire me to keep working on it—especially if users sign up and give me positive feedback.
Alongside this I've also signed up to wip.chat to keep myself accountable. And I'll be blogging regularly to publicly share my progress, so subscribe if you're keen to be updated :)