7 Reasons Why Web Apps Fail

转载 2006年05月19日 11:26:00
URL: http://bokardo.com/archives/7-reasons-why-web-apps-fail/

7 Reasons Why Web Apps Fail

Update: 7 More Reasons Why Web Apps Fail

I’m not one to believe that we’re in a Bubble 2.0 or anything like that (aren’t we always bubbular?), but here are a few ideas about why some of the web apps out there fail.

  1. Focus on social instead of personal.
    Following up on my Del.icio.us Lesson post, this is a critical reason why web apps fail. Many apps focus on being the new social killer-app when, in general, people don’t have time to worry about what other people are doing, and will only use software that benefits them personally at every step. You could call this selfishness or laziness, but I would call it optimization. For example, we simply don’t have time to tag things for tagging sake. Instead, we might tag things if we think that it will help us in the future, but adding tags to an app does not a solution make.
  2. They solve too many problems, or try to.
    This is when the buzzwords rear their ugly head. If you’ve got a list of problems you’re solving with an application, it stands to reason that you can’t solve any one of them fully. Instead of trying to solve more than one, focus like gangbusters on one problem and really nail it. If you think about the successful web apps out there right now that have garnered impressive mindshare, it should be easy to line up the one problem (or activity) they really get right. Flickr: photos. Del.icio.us: bookmarks. Facebook: college. Myspace: identity. Gmail: email. Plaxo: contacts. Tailrank: news. Etc…
  3. They’re about making someone other than the user happy.
    So much focus is on aggregation right now that it is easy to overlook the happiness of users. Many services, such as Technorati Tags or Google Sitemaps, exist solely to make the aggregators happy, and not the user themselves. They sell themselves on incentives that sound like what a movie agent might say to an aspiring actor: “We’ll make you famous, kid. You’ll get found!”. First of all, this is all talk directed at the developer, who is not the user. That’s a huge tip-off right there. Second of all, if the aggregators had their way everyone would be using these formats, which simply dilutes the value for everyone else and only serves to lock the site into some weird relationship with the aggregator. This is not how it should be. That’s why I stopped using those two services ages ago. Instead, focus on adding features that make the user happy, and when that happens everyone else can be happy, too.
  4. They sell it the wrong way.
    Web apps are not about Ajax, tags, Web 2.0, SOA, REST, or any other technology. Why do so many startups and web pundits focus on these terms when talking about a product? To get a better frame of reference, talk about how your app empowers users to improve their life. Think about how the long-term successful companies sell their stuff. They relate it to some bigger idea. So, for example, Nike has always embraced the hero archetype. They might talk about how great their foam arch is, but that’s always secondary to how buying their shoes makes you a hero. Their commercials are often amateur runners out running in the rain. How cool is that? Way cooler than double-density shock foam. A good example of this in web apps is the messaging from 37signals. They’re not selling software, they’re selling rebellion.
  5. Not in it for the long haul.
    If you build it, they will not come. There is too much competition right now, so another wiki-type application isn’t going to set the world on fire. I can’t tell you how many stories I’ve heard about web apps that became successful only after they adapted to their user base over time (short periods of time, but over time nonetheless). Their initial effort didn’t work, or was too similar to another one, but they were in it for the long haul and they adapted to what their users wanted. Flickr is a great example of this. Flickr started out as a game called Game Neverending. That didn’t work, but their second attempt did. Many web app makers would never make it to the point of seeing the light (or admitting the failure).
  6. They show too much of what’s going on, and get gamed.
    One of the big promises of aggregating the wisdom of crowds is building systems that use the input from huge user populations to come up with value. However, as people get used to how the wisdom is aggregated, they figure out how it all works, and the more public the mechanism for aggregation, the easier it is to figure out. That’s why gaming is such an issue with Digg. The voting on Digg is public, so you can see which items have the most votes before you submit your vote yourself. This goes against one of the principles of the Wisdom of Crowds, which states that in order to successfully harness it, each member of the crowd needs to be making an independent vote.
  7. They don’t have an underlying business strategy of improving people’s lives.
    Most business strategy is about making money. However, this is a short term goal. If you focus only on ways to make money, then you’ll make decisions that in the short term seem good for the balance sheet but in the long term actually work against it. Take the case of LLBean. Where everyone else is trying to get away from call centers and move all of their customer interaction to a web site, LLBean actually allows you to talk to a human being almost instantaneously. Their phone number is easily found on their web site/app. This probably does cost them a lot more than if they had some contact forms or an instant chat room, but it sure does make it quick and easy to give them money. My sister worked at LLBean for a time, and I was always impressed by the way that they empowered her to handle customers. It probably cost them money in the short term, but people remember when you make their lives easier, not harder. Many companies, unfortunately, see the Web as a way to reduce direct communication with customers, when in reality it should cause an increase in communication if you’re successful.

Update: 7 More Reasons Why Web Apps Fail

7 More Reasons Why Web Apps Fail

URL: http://bokardo.com/archives/7-more-reasons-why-web-apps-fail/ 7 More Reasons Why Web Apps FailT...
  • coofucoo
  • coofucoo
  • 2006年05月19日 11:47
  • 1183

读《why programs fail》的闲话

发现《why programs fail》有一些很特别的话。有些调试方法确实经典,还是写好自己的junit吧。 调试的六个阶段: 1.这不可能发生在我身上 2.它没有发生在我的机器上 3.它不该发...
  • iaiti
  • iaiti
  • 2013年09月17日 23:33
  • 2066

Serverless 风格微服务的持续交付(上):架构案例

GitChat 作者: 关注微信公众号:GitChat 技术杂谈 ,一本正经的讲技术 无服务器架构 (Serverless Architectures) 简介Serverless 架构最早可以追...
  • GitChat
  • GitChat
  • 2017年09月21日 11:28
  • 2084

7 Reasons Why BSD Is Better than Linux

One of the great joys about using Linux full time is the fact that I can also appreciate other opera...
  • lxgks
  • lxgks
  • 2009年08月18日 14:58
  • 246

Office web apps 预览服务器的配置

Office web apps 预览服务器的配置 本次测试的硬件要求是: 操作系统:Windowsserver 2012; 内存:4GB CPU:2核 以上的配置时不时还出现文档无法预览的情...
  • dqccsdn
  • dqccsdn
  • 2015年09月02日 17:19
  • 1196

基于Office Web Apps Server 2013 的文档在线预览汇总

1、部署Office Web AppsServer 2013后就直接提供了该功能。 下面是在本地服务器上的效果(http://aqqz-dellr710.aqqz.net/op/generate.as...
  • cybersoft
  • cybersoft
  • 2015年05月17日 13:26
  • 3784

Office Web Apps Server 打造手机移动办公系统

有关IPAD上或者手机上怎么看文档,我估计10个人有10种方法   前几天Ms专家来推销他们的产品,我倒学会怎么搞个移动办公系统让网络上设备不需要安装Office软件查看Office文档。    ...
  • luozhuang
  • luozhuang
  • 2013年05月15日 16:05
  • 7420

自定义开发的系统整合 office Web apps

其实网上有关office web app的整合已经有相关的文章了,典型的是如何整合Office Web Apps至自己开发的系统(一) 和如何整合Office Web Apps至自己开发的系统(二)...
  • jason_dct
  • jason_dct
  • 2017年01月18日 17:14
  • 3025

你的首个 Progressive Web App

Progressive Web Apps 是结合了 web 和 原生应用中最好功能的一种体验。对于首次访问的用户它是非常有利的, 用户可以直接在浏览器中进行访问,不需要安装应用。随着时间的推移当用户渐...
  • liangyihuai
  • liangyihuai
  • 2017年02月09日 15:53
  • 2786

[译]模仿原生应用的 Web 应用(Progressive Web Apps)对 Web 的意义

原文:What Progressive Web Apps Mean for the Web Opinion by TJ VanToll 作为一个开发者,我持一定的怀疑态度去了解新平台特性...
  • derek518
  • derek518
  • 2016年03月30日 23:20
  • 2694
您举报文章:7 Reasons Why Web Apps Fail