That's kind of my point. By requiring the toggle we are shutting down a lot of cool/specific user experiences people could implement. I know a lot of design/devs that create a single experience and a toggle would destroy it.
Instead of requiring toggles in all clients, we should be more flexible to move between clients. Some clients can have toggles, while others don't. If you like them, you like them.
So much in agreement with this.
Normalizing moving through different clients at this stage is very important
“Culture eats strategy for breakfast”
Furthermore, compromising on your product’s vision with a bunch of optionals and toggles is very problematic. Specially when this is open source and open networks and you can implement whatever vision you have.
A lot of the success of Apple is not comprising with democratic design and executing on someone’s vision, everything else be damned
I agree. I think it's important that clients are honest about it though (if it isn't totally obvious) and doesn't just hide the fact that the algorithm applied some rules to what is filtered out of their feed.
Oddbean new post about login | logout 