| The author explains a few problems with the current state of the Web under the section The Five Lacks: - "On the closed social web... We lack freedom, innovation, trust, respect, and transparency." - "Innovation on these platforms is dying." - "And there’s little transparency. All of the data is locked up or rate limited to a prohibitive degree." While some of these may or not even be true (innovation dying, really?), I think the author makes a large leap from his premises to the conclusion. So just because the author claims there are issues with the current state of the web, that doesn't mean the solution is to completely ditch "the tech giants in control suppress our freedom" and remove yourself from the current web platform and applications (e.g. fb, google, etc.) The best way to determine whether this is a viable and useful solution, and whether or not some of the apps are actually something people want and find useful is to see how many people ditch applications from the "tech giants" start using these new apps built for the social web. A lot of ideas sounds great in theory, but then don't hold up years down the line. Plenty of new applications and social networks have been created over the years with great explanations and a "Our Philosophy" section, but what actually matters is whether or not people change their habits and start using these new applications. The problems the author listed in The Five Lacks section are completely real problems on a lot of the applications on the Web, but I don't think any of these social web apps listed in the article are the solution. |
My reason for mentioning these things is to help start the conversations around then.
I think any app with infinite scroll, which I think Patchwork might have, isn't respecting how repetitive motions like that lead to addictive behaviors and/or repetitive stress issues.
Also, I'd like to see other design patterns useful for addicting users to be publicly and loudly set aside.
Since these apps are open source, I can at least start the conversation & I can do it with pull requests.
I also think the metric of conversion is misguided for determining if it's successful. I think it's time to start measuring software design based on subjective well-being. Allow users to see metrics related to their well-being, like how much time is spent using the apps and in what ways.
I think people are first going to populate a new app ecosystem with iterations of what's popular outside the ecosystem before doing the serious work of addressing all the ways we software wrong beyond what's kept in mind when designing the ecosystem. Could that be what you're talking about?