2
2 Comments

The journey starts here

It's time to build something.

Yesterday I was walking in the park, when the idea hit me.

Every morning I spend 10 minutes drinking a coffee. It's part of my morning ritual. While I do so, I flick through the internet. My brain not fully awake.
Eventually I land on something interesting. It's usually something new that I'm not aware of. Probably thanks to the caffeine, my brain leans in, and for 4-5 minutes, I absorb whatever I stumble upon.
Fulfilled by the experience, my day can finally starts.

Now, I want to make it easier for me and other people to get that daily knowledge drop. Something that is already there the minute you open your browser.

I'll try to build something that does that, and blog here while attempting.

Next Step:
I want to get the lifecycle of developing this up and running as soon as possible. What is the bare minimum thing I need to do, to get something something working? I'll start with a chrome extension. I'll need to learn how to develop a chrome extension (I assume is basic CSS/HTML/JS with some manifesto configuration), and how to publish it.

Random Thoughts:

  • This can easily rabbit-hole into a recommendation product (which unfortunately, I have worked on my entire career). I'll try to avoid collaborative filtering or topic modeling too soon.
  • content sourcing is probably the biggest bottleneck for me (I know little, and I'm not good at writing). Going marketplace here might help: have content providers taking a cut based on satisfaction/volume of readers)
  • if content sourcing is solved, content moderation becomes a problem. I don't have a solution yet here, maybe there is a tier of power user that gets content earlier on - this is turning into a community, which I don't necessarily like as Business model
  • Revenue:I want to keep this cheap. Knowledge should be nearly free, especially because I expect effort on curation, but not on knowledge creation (the majority of the facts are already out there). Costs 1 coffee a month? (4.99$).
  • Principles: this shouldn't take more than 5 minutes of your day. You can learn something without having to build any prio knowledge (self contained information). I cannot spend more than 1h a day on this project.

Open questions:

  • Internationalisation (i18n): I'll worry about this later, and I'm sure I'll regret this decision.
  • accessibility: sad, but I'll worry about this later too.
  • multiplatform: I want to stay away from mobile as much as possible (i know little on how to deploy fast there). I also hope that mobile extenions are easily portable across different web browser (most likely safari will disappoint me)

Stay tune for the next update

on September 13, 2020
  1. 1

    React.native is your friend for mobile.

    1. 1

      Yes, you are absolutely right. I'm a bit concerned that the deploy lifecycle is quite long (from code to the user's phone), and right now I want to get this out of the door as fast as possible