4
2 Comments

Less is more - how to create a new product by reducing features or adding constraints to the existing product

I just published a new article explaining the motivations behind my newly launched product:

Why build a messenger app only for sending to yourself?

I think there are some interesting lessons from this product I built -- a new product idea can be coming out of existing products by reducing the unwanted features or putting constraints on it. A few key take away to think about the potential new product ideas in this way:

  • Are people "abusing" the product that's not originally designed for? (like sending msg or emailing yourself)
  • By removing features, is there any benefits of doing so? (like remove the risk of sending to the wrong person)
  • Is there any constraint I can add to hit a niche people actually wanted? (for example, like time limited post)

The Monoline app is an example of reducing messenger app to become a note-taking app. Are people going to use this product? I don't know yet, but at least, this is something I am trying and I would like to share it here. I am also curious to know if there's any idea you made based on "less is more" thinking and how did it go? Let's discuss 😃

on November 11, 2021
  1. 2

    Hey 👋

    Awesome stuff. I totally agree with your thinking above. Downloaded the app and will give it a go. I’ve been a “serial self messager” for years, but recently I’ve stopped - in hindsight it’s probably because I’ve not had easy access to all the items of the past. Perhaps Monoline will reboot my old behaviours :)

    Thanks for sharing.

    PS: the blog post about why is very good 👍

    1. 1

      Thanks for the kind words! Please let me know if you have any feedbacks, I will see what I can do 🙌