Sorry if the title feels misleading (I didn’t intend to), this has nothing to with the number “2” in particular, just that I have launched 2 products on ProductHunt and the outcome was vastly different from those with no co-relation or causation implied.
First product posted on ProductHunt, it got all of 3 votes (all from my friends), dejected I left it alone and went ahead with life. 5 days later, I get a twitter notification that my post got more than 1000 votes. Seems PH posted my product back again that weekend and it picked steam. It ended up being #1 product of the day and I just have a theory on why they might have picked mine up and why at that time. But that might sound far-reaching and without backing of data, so I’ll leave that out of here as the world has more of it already.
This one I was looking forward much as this was my first proper SaaS. And also, since I already had a highly voted product (got some followers from it), figured I’d get decent reception on ProductHunt. Ended up getting all of 6 votes. Greedy and hopeful as I am, I waited to see if PH would pull another card like they did with my first product. Nothing.
But… as a surprising turn of event the product got picked up by a tech blog, and from there another and with some big names following suite. It just snowballed from there and I ended up getting more signups from there than I could’ve anticipated from ProductHunt success. I still continue getting users from these referrers and they have been of huge help in SEO front.
So my take is, it doesn’t matter whether the product has “successful” launch with 1000s of upvotes or left in oblivion on launch. As many have said before me, launch day is only the first day of your Product.
Put your head down, continue your grind and talk to your users. The growth maybe slow, but the foundation you build will be strong.
As mentioned in my previous post, here is the roadmap I have planned out for Finesse this year.
Broadly I want to focus on 4 different categories of features, each with its own merits.
For the past couple of months, I’ve been hard at work in completely revamping the user experience on Finesse.
This includes changing the whole frontend framework (bootstrap to semantic-ui), redesigning all the pages and completely rewriting all the front-end code involved.
As you probably know, git is a popular version control software used in projects across the globe. One of the major features and one that distinguishes it from other tools is it’s branching mechanism. The code is usually tracked via commits and grouped by branches in git.
As the branches are lightweight and disposable it’s very easy to get cluttered when many people are working on a project or if there are many branches. And so, as anything with software, naming a git branch will itself need a standard convention to be followed in a project to keep it organized and sane. There are many naming formats out there and several project-specific ones I’ve worked with.
This is a follow-up post to my previous article on how to implement passwordless authentication in rails in sitepoint. It basically talks about how to implement login with just rails model, controller and a login token.
Recently I received an requirement to build a Password-less authentication system for a client project and while I wanted to do the way I have written in the article, I was looking out for if any viable options are out there since it’s been 3 years. And there is one. I stumbled across passwordless by mikker. It’s basically a gem that you can add it to your Rails project and get the password-less authentication system enabled.
Barring couple of hiccups I faced (project specific requirements, the PRs were promptly addressed), the gem works neatly as advertised. I’ve used it for the project and it’s running smoothly in production now.
That’s why this entry. I wanted to share the gem because it’s a nice solution for something I advertise a lot(get rid of those passwords!).