![]() ![]() The fundamental attribution error has always been one of my cautionary mental models. When designing an app that shapes its user experience off of a social graph, how do you ensure the user ends up with the optimal graph to get the most value out of your product/service? ![]() I refer to this as the problem of graph design: I've mentioned it in various passing conversations online before. While many of these flaws have already been pointed out and discussed in various places, one critical design mistake keeps rearing its head in many of the social media Testflights sent my way. The converged surface area in the design of all these apps suggest oblique vectors of attack. It's never smart to tackle powerful incumbents head on anyway. Still, it's easier to learn from where they went wrong if we're to head towards greener pastures. A lot of mistakes are understandable in hindsight given that online networks of this scale hadn't been built in history before. Of course, to be where they are today, they had to do a hell of a lot right, too. The next wave of social startups should learn from the weaknesses of some of these choices of our current social incumbents It's easy to point out where our incumbent social networks went wrong. By now, we're all familiar with the infinite vertical scrolling feed of content units, the likes, the follows, the comments, the profile photos and usernames, all those signature design tropes of this Palaeozoic era of social.īut just as there are reasons why these design patterns won out, we shouldn't let survivor bias blind us to their inherent tradeoffs. ![]() Looking back at the companies that have survived, certain application architectural choices are ubiquitous. It feels as if we're at the tail end of the first era of social media in the West. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |