初心 shoshin

A Tale of Two Add-Ons

Speculations on niche vs general solutions

I made an Anki1 add-on to convert Markdown-formatted inline code and code blocks to HTML.

It got a bit of traction on its Anki add-ons page with 8 positive reviews. Not much, but I made it for myself and wasn't even expecting anyone at all to use it.

Problems

Rewrite

Instead of fixing/implementing these, I decided to make a new add-on. I figured that I could just use an existing Markdown library for Python to read the input and convert it to HTML. This new add-on was designed to support full Markdown syntax, along with optional extensions, rather than just focusing on code. I got it working in an hour or two and published it to the Anki add-ons page.

I am very pleased with the rewrite. In addition to delegating all the hard stuff to an off-the-shelf library, I added a lot of new parsing functionality, fixed bugs, and added the requested toolbar button. With fewer lines of code!

If my first add-on that did nothing but convert code to the proper HTML tags got 100% positive reviews, I figured that my new add-on, Simple Markdown, would receive a lot more. But that was not the case. Although the Github repo received a star, no one has left any reviews on the add-on page.

Extrapolations

If I had never written the first add-on and went straight to the second, the lack of reviews would have conformed to my expectations. But based on my experiences with the first add-on, I found the lack of reviews strange.

What can be extrapolated from this? Could one apply any insights gained here to a more lucrative endeavor?

I admit I'm hardcore speculating, but I like speculating. It's how you come up with new ideas. So to continue...

I wrote a decent add-on with a very specific purpose. I wrote a much better add-on with a much broader purpose. The former has (so far) received more traction than the latter. What drove the increased popularity of the former?

I suppose it was competition. There are already 10 other Anki add-ons claiming to provide Markdown support2. There are no add-ons that specifically target Markdown code translation. I actually found it odd that people wanted to use my add-on in the first place. Why not just download a full-fledged Markdown parser? Perhaps, like me, they desired simplicity.

I wonder if these extrapolations would work with real products. If there are 10 products on the market that accomplish X, would you be better off making a new product that specifically targets a subset of X rather than making a new product that does all of X (even if it does it better in your eyes)? More broadly, how much do the dynamics of add-ons (be it Anki, Chrome, or whatever) reflect actual market dynamics? Would be cool to try a similar experiment with apps on the Apple App Store and Google Play, however, marketing would be impossible to control for here3.

Footnotes


  1. Anki is an open source spaced repetition system for making digital flashcards. The desktop version allows the user to install add-ons written in Python. ↩︎

  2. Then, why make another? All the other Markdown add-ons added too much "junk", stuff I didn't need. I made Simple Markdown, because I wanted to make the simplest Markdown add-on possible. Something that I could install and forget that I ever had it installed. ↩︎

  3. If it wasn't obvious, I did zero marketing for my Anki add-on, not sure about the others (I know some people do make Anki add-ons for money). Hence, I assumed that marketing was controlled and at zero for my little experiment. ↩︎