I started lurking on Hacker News and Product Hunt at the beginning of the year. The motivation for building serializer came from an approaching assignment deadline, rather than cutting out news I thought I’d make following it more manageable. For me this meant a sequential feed - I didn’t like having to scan the entire ranked list for new items.
I decided on a name pretty quick and bought serializer.io the next day. Students got a discount on .io domains at Namecheap (at the time).
I set to adding some extra features. Read-to-Here marker, ‘loginless’ syncing, pick and choose custom feeds and tweet counts came about pretty quickly.
At this point I was still the only user of serializer.
April 2nd: I added the word count feature (and a save to Trello Reading List feature that’s live but isn’t really ready for the world yet).
April 19th: Switched to a $5 Digital Ocean droplet using dokku-alt and made the source public. This was in pursuit of better performance as well as in response to Heroku’s pricing changes. serializer is still going strong on the same $5 droplet.
I took a break for a while after that, only making very minor changes over the exam period when I needed a break from the books. I started using an ‘over 10 url’ for Hacker News and made some other adjustments to marginally reduce the number of collected items. Pressure of exams and all that.
May 15th: I added a link to points, a cool app I’d seen on Product Hunt. I’d found it was pretty good at summarising articles wanted make it a feature. I reached out to points and heard back from Hugh Jones, he liked serializer and the points connection and offered to setup a post on Product Hunt.
May 18th: serializer did better than I ever expected and finished the day in the top 10 with around 100 votes at the time. Since I hadn’t done any promotion before I saw a vast increase in traffic, I was impressed that the droplet held up.
This weeks trend, can you spot the Product Hunt boost?
This in turn led to some really great feedback from Product Hunters on Twitter and via the feedback form. In response to this I’ve made the following changes over the last few days:
- Display unread count in the tab title.
- Added an apple-touch-icon.
- Reduce chances of users being assigned the same random session identifier (potential error)
- Revise the feedback page, trying to move over to GitHub Issues and a TypeForm for feedback.
- Add some pointers to the GitHub repo.
- Added clarification to the way the session links work. You just need to visit the session path on each browser and then use the site as normal.
Looking forward, I think serializer is fine where it is. I might add some more sources and tidy things here and there, but nothing major. I’m never going to try and make money from it.
It solves a problem for me (and apparently some others too). At the end of the day that’s all it needs to do.