My product was developed because I've written more or less the same licensing API logic for a few different desktop applications. I figured I couldn't be the only person who didn't want to write licensing logic, especially when it starts getting more complex with add-ons, user accounts, etc. so I've been creating a solution for myself and everybody else.
Keygen solves that issue by making licensing simple for desktop applications (not only limited to Node/JavaScript, of course), as well as some web apps (most notably in my mind would be gaming or other SaaS apps, but really it could be used for many different types of web apps). I've tried to provide a better UX than current solutions, such as not requiring a license key but rather having your users login and then checking their account for a specific license.
That being said, it freaked me out a little bit when I opened it!
Challenges I've faced:
- Getting carried away with automation: emails after certain events, marketing to users who don't convert, billing features; all of these are things I should have done post-launch.
- Writing tests. I've literally delayed the launch of the product a whole month because I didn't feel my test coverage was good enough. I should have launched the beta and then started writing tests.
- Too many features. "Hey, x) would be a cool feature!", "Oh man, y) would be super useful to my users." – Yeah, I've written and then removed so many features that I'm a little ashamed.
- Wanting to adhere strictly to the JSON API spec. I shouldn't have spent so much time making sure that it followed the spec, because in the end, it doesn't.
After reevaluating things, all I need to do is finish writing documentation so that I can roll out the beta.