6 Ways to Create a Successful Facebook Application
BJ Fogg, a Stanford professor who teaches a "Psychology of Facebook" class, spoke today at the Snap Summit 2.0 in San Francisco, where he told the audience that he believes Facebook is the most revolutionary technology since the radio in terms of influencing the decisions we make and the actions we take.
He also laid out six ways in which Facebook developers can create successful applications by tapping into Facebook’s capability to facilitate "mass interpersonal persuasion."
Took some quick notes on them here:
1) Facebook is a persuasive experience. Since Facebook opened its platform to third party development, there has been an explosion of applications. As Dave Morin, Facebook’s senior platform manager said today, around 30,000 have been application created to date since May 2007. Fogg says that explosion has been driven not just by the technology itself, but by people encouraging peers to install it, use it, share it, and keep it.
2) Automated Structure. Due to Facebook’s simplicity, and the ease with which you can share and post information to it, it allows people to collaborate faster. As an example, Fogg says that telling people to set up a group of supporters for Barack Obama in person can be difficult and require time (weeks or months) and money. On the other hand, setting up a Facebook application for people to unite under the presidential candidate, which they share with friends (and so on), could take hours.
3) Social distribution. The success of an application often depends on the amount of people who share it. As such, it’s incredibly important that Facebook maintains an environment of trust, where people believe they will be caused no harm when they participate.
4) Rapid cycle. From a business perspective, quick and dirty can often be better than slow and polished. In order to have an application get noticed on Facebook, you need to develop it fast and make tweaks after it hits the directory.
5) Huge social graph. Tap into "the large sandbox" that is Facebook, and try to go broad instead of niche. The social graph is what Facebook has to show users degrees of separation to their "friends" and "networks." The more of the social graph you reach, the more successful an application will be.
6) Measured Growth. Not only do you need to develop applications quickly, you need them to catch on virally. One of the ways that Facebook users decide to download an application depends on how many people on Facebook have added it. If the install rate is low, and doesn’t rise quickly, it’s likely to fall off the radar. Companies that have done this well, Fogg noted, have been RockYou and iLike. CIO did a feature months back on what business lessons can be learned from these start-ups.
Previous Post: Facebook Manager Talks About Hopes for the PlatformNext Post: Four Qualities of a Top Performing IT Deparment
Most Discussed Posts
Cloud computing has emerged as one of the most significant game changers to hit the technology landscape in the past 20 years. With this massive expansion of the cloud, the perception of the IT organization is shifting from a utility player to a change agent. This eBook breaks down five ways progressive organizations are using cloud-based IT Management solutions to help drive innovation and become more strategic, including: adding visibility and analytics, speeding up time-to-value, lowering costs, improving prioritization, and providing a blueprint for future cloud deployments.
Read the white paper to see how IBM helped Citigroup deliver new services and enhancements to their 200 million customers faster.
There are 3 ways to modernize legacy applications: rewrite completely, acquire packaged solutions or migrate existing code. This paper explains why it's best to migrate and how IBM® Rational® software can help.
Accommodating specific lines of business can result in a hybrid ecosystem of applications and servers. The resulting complexity of this architecture makes for an environment that is costly to maintain and difficult to change when addressing new challenges.
This whitepaper will help you to define a mobile device passcode policy. Security managers must attempt to reconcile two opposing goals. They must: 1) create a passcode policy that is strong enough to protect the device if it is lost or stolen, while: 2) not annoying users with needless length or complexity.
This whitepaper, authored by The Radicati Group, looks at the key reasons organizations should consider moving to a cloud-based archiving solution. Email archiving solutions enable organizations to store, monitor, and collect electronic data exchanged by their users to comply with internal policies and regulations.
ATERNITY will showcase a 30-minute demo on how Fortune 500 companies are leveraging its award-winning FPI Platform to deliver a user-centric approach to Proactive IT Management.
For businesses to move forward and tap into the ever-expanding universe of Internet users and network-enabled devices, it's critical to learn how to make the transition to IPv6. Learn the critical steps your organization must take to make a seamless transition-and keep your business world connected.
Learn how IT teams can protect against spear phishing tactics. Harry Sverdlove, chief technology officer of Bit9 offers a frank discussion about spear phishing - the most common technique used in today's advanced attacks.
Learn how to build a solid business case for your migration to Red Hat Enterprise Linux so you can run leaner, innovate faster, be more flexible and own the New Now.
Social media isn't about you; it's about everything around you. As you consider how your customers want to communicate with you, social media is something that can't be ignored. But what should your strategy be? Is social media "just another channel?" What kind of a plan makes sense for your contact center and for your customers? Join our experts as they share their insight and research results.
Hardware tokens were a popular method of strong authentication in past years but the cumbersome provisioning and distribution tasks, high support requirements and replacement costs have limited their growth. The additional log-in steps that hardware tokens require and the resulting user frustrations have limited adoption and make them impractical for larger scale partner and customer applications.
Sponsored Links
