RankBlob notes · Builder video

Sofa: A better product can mean fewer features

Sofa creator Shawn Hickman explains when removing a feature can be the right product decision. He shares examples from his own app and discusses communicating changes and responding to users.

What to take into your own app

  1. Revisit what belongs in the product

    Hickman discusses features that are broken, underused, or no longer fit the app’s direction. Shipping something once does not mean maintaining it forever.

  2. Consider the people who rely on it

    Removing a feature changes someone’s workflow. Use the examples to examine the consequences before treating removal as a simple cleanup.

  3. Explain the change

    He covers communicating removals and navigating feedback. Tell users what is changing and why, and leave a clear way to respond.

A small experiment to try

Pick one feature you find difficult to maintain. List who uses it, what job it performs, and what alternatives exist. Draft a removal announcement before deciding whether to remove it.

The original source

Start at 4:53 for reasons to remove features; 11:47 for examples; 22:09 for considerations when making the change.

Watch the original on YouTube ↗

Visit the creator’s site ↗

Good ideas get better together.

Enjoying the read? Meet indie app builders, compare notes, and share what you’re working on.