Lightweight IFTTT Makes a BIG hit!

Being as one of Tim O’Reilly’s web2.0 patterns, Lightweight and Scalability can be applied to both business model and technology. Beginning with a scalable and cost-effective approach has the following benefits:

  • Shorten the time from development to the market
  • Reduce time and cost = Faster ROI + Less risk
  • Greater adaptability

However, in order to achieve the success in web2.0, effectively scale and pivot the model to cope with ever changing environmental conditions are the key. The sooner we can recognise potential risks and failures and make change accordingly, the better we can survive.

Let’s take a look at the IFTTT, the lightweight and emerging website which offers amazing approach for mashing web services together and creating convenient outcomes. See how IFTTT managed to achieve great success just in 2 years (one of 50 Best Websites from Time)and what are their best practices:

Started up with only 2 friends and an awesome idea, IFTTT is a new website established  in 2010 offers simple but effectively approaches for users to connect web services, and even electronic appliance(Belkin’s WeMo) together, and perform specific tasks. It applies the simplest concept of programming:

IFTTT: how it works

Want to be informed when it’s gonna rain? Want to save all the photos that people tag you on facebook to your dropbox? Simply create your own “Recipe” like this:

Example of recipe: Send me a message when it's going to rain

It is so intuitive that even non-programmer can easily adapt and create their own recipes in no time. With the integration of third party APIs and their native “Channels”, indeed IFTTT provides the way to link all our favorite web services together with innovation and great convenience!

But, how they did it?

Start Small and Scale with demand: 

Small technology, revenue, and human resources model

IFTTT started with 2 friends and a beta version in the end of 2010, soon the beta attracted huge popularity with rapidly growing “recipe” amounts, eventually led IFTTT reach more than 400,000 recipes created with 62 channels, but with only 8 employee.

Syndicate business models, not coordinate:

IFTTT can be regarded as a giant web2.0 plant fed by third party APIs. The more web services that IFTTT can integrate, the more traffic and users. It has successfully created an online ecosystem for users to interact with their own recipes, their social connections and the popular web services. Now they are aiming to launch a platform for users or developers to turn their APIs into “Channels” to boost creativity and opportunity.

The cooperation with ESPN, Philips HUE bulb and Belkin WeMo: multi-device Control further facilitate IFTTT’s syndication with different business models to create more possibilities for cross-field collaboration.


However, Twitter decided to change their policy on how third party applications can access and interact with Twitter’s data. That is , users can longer use Twitter as a valid “Trigger” to perform something like: “IF anyone tweets about Web2.0, THEN send me an email”. Though it is still okay to have “IF I check in on Foursquare, THEN tweet”, where Twitter acts as “Action”.

Market virally without spending money on advertising! 

Since the launch in December, 2010 till now, IFTTT grows bigger with increasing Channels and viral popularity among internet users. Their huge success should attribute to the nature of social media: recommendations from popular bloggers and websites such as Forbes, The New York Times, Wired, Time and TechCrunch

Not to mention that how easy we can create a recipe and share it with our friends on Google, Facebook, Twitter, LinkedIn and many other social media platforms.

My Suggestions for IFTTT:

Though IFTTT is still in its early stages, it is better to start to further improve their current business model, for how to make profit. Possible approaches will be:

Premium and Customised Recipes: users can easily have their customised recipes done with extra fees. It would be awesome if there exist one platform where I can integrate all my recipes together and perform more complex task such as: IF the temperature is below 15 °C, THEN turn on the heating 10 mins AFTER I check out from campus. 

Cross-sell and collaborate with other business:  Strategic collaborate with other online service and encourage users to sign up for a new service through IFTTT’s Channels. Possible partners include public transportation API, Cinemas and even restaurants.

Reference List:

IFTTT, A Glue Gun For Sticking The Web Together, Raises $1.5M Seed Round From Top Investors, Eric Eldon, Jan 04, 2012
How to Never Miss a Deal with IFTTT, Thorin Klosowski, Mar 15, 2013
Twitter Screws Up For The Rest Of Us, Erik Deckers, Sep 21, 2012
10 IFTTT Recipes to Optimise Your Business, Stephanie Buck, MAR 29, 2013. 
IFTTT: San Francisco Startup Lets Anyone Control The Internet of Things, Elise Ackerman, Sep 23, 2012

What Is Web 2.0, Tim O’Reilly, Sep 30, 2005


tumblr and its Long Tail


The term “Long Tail” got popularised by Chris Anderson mentioning Amazon, Yahoo! and Apple are businesses which apply this strategy in his article. To put it shortly, Long Tail theory is about:

As the cost of production and distribution fall, the focus on mainstream products and markets at the head of demand curve has shifted toward a huge number of niches in the tails

The benefits of applying long tail theory include: it gives organisation the ability to target potential micro-market while reduces the cost of distribution, inventory and sales, and provides infinite shelf space. It also helps contents producer to reach wider audience and increase customer choice.

Being as a rapidly growing microblogging and social networking platform, Tumblr has many competitive advantages over other similar services such as: it allows users to write longer posts than Twitter and delicious, and most importantly, in an intuitive, easy and quick way.

tumblr001Established in 2007, Tumblr has experienced steadily growth and the dramatic jump happened between 2010 and 2011, led Tumblr to achieve over 110 million blogs with 72.9 million posts were made everyday.

How Tumblr applies Long Tail Theory?

Tumblr was built on the driving force of Long Tail:

The ecosystem of Tumblr is different from other Facebook, Twitter, or LinkedIn, where users interact with others by their real identities. Most of tumblr’s users regard the platform as a stage for expressing themselves publicly. With the help of tumblr’s content policy, miscellaneous categories made Tumblr a place for discovering one’s interests without many limitations. According the the statistic data measure by Quantcast, the major audience group is young adult (aged 18-34), and the most common interests are: humor, adult content, fashion and news. While the tail part of interests which are not in popular demand still makes massive contribution to tumblr’s daily traffic, the key is how to make the tail fat and thick.


Customer self service + Participation architecture = Reduce cost + High Customer Satisfaction

The success of tumblr is greatly based on user generated contents and its diversity to meet different customer expectations.  Users receive a lot of freedom on the creation of contents and controlling their accounts without much support, while tumblr can enjoy better customer satisfaction with lower cost of account management.

My suggestions for tumblr:
1. Optimise yourself with tons of key words for Search Engine (SEO)

Though tumblr has more than 40% direct traffic, in order to reach mote potential users, it is better to have the related posts or blogs shown on the results of major search engines. Compare to other blogging platforms like WordPress or Blogger, tumblr’s blogs indeed receive less favor from Google, Bing and Yahoo!. Tumblr’s blogs and posts are only visible when “tumblr” is included as keyword.

2. Dig into adaptive personalisation and customisation

In order to boost the interaction among users, deepen existing connections and expose active users to more potential followers, tumblr should launch the adaptive personalisation approach by adding customised suggestions like:  “you may be interested in this post/blog” or “users who follow this blog also like…”

3. Be open to encompass new contents, and stay open (Update!)

Tumblr was acquired by Yahoo! for approximately $1.1 billion on 20 May 2013. Though Yahoo! pledged not to screw up tumblr deal, the acquisition still received negative responses from tumblr users. “In order to keep the richness and breadth of the contents on tumblr and allow Yahoo! to reach more users”, CEO Marissa Mayer suggested that “tumblr’s porn can stay“. It is no doubt the best decision for coping with angry users at the early stage of merging tumblr into Yahoo!’s culture, however, as a nature of user generated contents, it seems unavoidably every social media platform will get dirty with time. How to keep the niche market growing within ethical and legal constraints but without losing specific user groups is definitely one of the biggest challenges for all the social media platforms.

Reference list:

* Usage Analysis: Tumblr, Brendan Smith, Apr 16, 2013
* Oh, The Places Tumblr Can Go, Ingrid Lunden, Jan 02, 2013
* Tumblr: David Karp’s $800 Million Art Project, Jeff Bercovici, Feb 01 2013
* Tenth Grade Tech Trends, Josh Miller, Dec 29, 2012
* Web 2.0 and the Long Tail, Chris Anderson, Oct 01, 2005
* Microblogging update: Tumblr feed, Chris Anderson, Sep 04, 2008
* 6 Ways to Leverage the Long Tail in Your Marketing, Prashant Kaw, May 5, 2009

Digg into Perpetual Beta


The concept of Perpetual beta, coined by Tim O’reilly within the explanation of one Web2.0 pattern, end of software release cycle , describes as software becomes ongoing services, “the product is developed in the open, with new features slipstreamed in on a monthly, weekly or even daily basis”, and “engage your users to be real-time testers, and structure the service to reveal how people use your product”.

Being as the once wildly popular social news website, Digg had experienced both the high time with numerous copycat websites featuring its story submitting and voting system, and also the disastrous user revolt toward its notorious release of Digg v4, and followed by  dramatic decline in web traffic and fierce competition from Facebook.

After the acquisition by Betawork, Digg had its second act successfully regain popularity among social news community by rebuilding the website from scratch. Through the launch of, digg invited users to participate in the decision of user interface design and user experience by answering the survey. Based on user’s idea, the new digg v1 came back with newspaper-like front page and more images, new story ranking system integrating Tweets and Facebook likes, to be counted with its traditional thumb-ups, “diggings”.

Critical Success Factor comes from frequent and early release

Through its nine-year long run, Digg has its new version released almost every year between 2004 to 2007. however, despite the “extensive overhaul in 2010“, it took nearly 3 years for Digg to introduce version4, which was, eventually proved to be an death knell for Digg. Luckily enough, Digg got a second life and came back to the market after 6 weeks sprint transformation by the new team. The new team plays well with the concept of Perpetual Beta by frequently introducing new features and fixing bugs almost every week, and so do its mobile apps.

Actively engage users in the development and test cycles

The new Digg team is very keen on extracting the “Digg experience” from its users. Even for the new Digg Reader, users are invited to have their says and participates in the decision of core features and UI. Since only users know what kind of service and features can meet their need, the developer can rarely go wrong if following closely with user requirements and expectations. Plus users can perform the task to test the platform, in real time, and feedback straight away. Thus the process is shorten and the efficiency is improved.

My suggestions for Digg:

Capture the implicit facts that users interact with Digg

I got to admit that the new Digg team really has done a good job by getting Digg back to the old good times. And indeed, surveys and questionnaires do offer a lot of essential information about user experience and provide directions for improvement. However, what users do often tells more than what they say: according to Digg’s survey about what topics that users enjoy to read most, the result is as follows:


However, the statistics measured by SimilarWeb, suggest another thing:



Interestingly, part of the users who visit Digg also like adult websites. But the option is not even on the list of hot topics voted by the users. Apparently observing user behaviour and capturing the implicit usage data can reveal more facts and possible approach to boost website traffic.

Right before the new Digg team started to launch the overhaul, they conducted a survey and which indicated a stark statistic that: 92% of Digg users would NOT recommend Digg to friends. And straight after the big triumph they made, they happily reported that according to the survey done after the relaunch, now 81% respondents said they would recommend Digg to a friend. But, why can’t they just add a feature like “invite your friends to Digg together” and see how many users actually do it? Maybe the survey is simply an indicate of user satisfaction, but I believe there exist more user behaviour facts awaiting Digg to “dig out” and act on it. In order to compete with Reddit, SlashdotStumbleUpon and other social news websites, Digg still have a long way to go.

Reference List:

SXSW: Digg’s Big Redesign Taps Into Social Web
* Digg – Yes, That Digg – Is Building A Google Reader Replacement, Complete With API
* New Digg Vs. Reddit Vs. BuzzFeed: Your Mind On Viral Content
* Digg’s replacement for Google Reader due in June; might cost money
* What is Web2.0? – Page 4,  End of Software Release Cycle

LINE App: Software Above the Level of a Single Device

LINE is a proprietary instant messaging application initially released for smartphones in June 23 2011, and has since expanded to desktop computers and other mobile phone such as Blackberry, Windows phone and Nokia Asha after its tremendous hit and popularity among 230 countries. In addition to basic text messages, LINE allows users to send images, video and audio message and make free VoIP calls. The company has further launched a platform, LINE Channel which integrates more service and even native apps to provide more fun and enriching user experience.

The great success of LINE can be attributed to the pervasiveness of smartphones and the company’s design strategy: building a “Smartphone-life platform” and an ecosystem (economic zone) by “offering various content and services developed by its external business partners for the 45 million users worldwide.” The concept of “Smartphone-life platform” aligns well with Tim O’Reilly’s web2.0 principle, software above the level of a device.

The principle can be clearly elaborated by Microsoft developer David Stutz in his Advice to Microsoft regarding commodity software, which is cited by Tim O’Reilly as well, that:

Useful software written above the level of the single device will command high margins for a long time to come.

So let’s take a look at 7 awesome practices that LINE has employed to fully utilize this principle:

As mentioned above, LINE was initially designed for smartphones like Android and iOS platforms but soon with its rapid success, the application now is available on multiple operating systems including: Microsoft Windows, Mac OS X, Blackberry, Windows Phone and Nokia Asha with up to 10 languages.

Benefit: allow the app to be accessed anytime, anywhere.

LINE app requires user’s permission to access location data for specific functions such as LINE camera, “Shake it” and QR code scan for adding friends (see picture below), and location sharing with contacts (see picture below). Users can take further social interaction like get direction to where the contacts are or send the location info to another chat. More location aware features like coupons will be released in the near future.

Benefit: Location aware contents is essential for personalization.
Suggestion: Location aware interaction such as QR code coupon or place check-in can make the service more personalised and open up new business opportunity with local business owners.

LINE has successfully turned the mobile into a social platform for instant message, multimedia sharing, and even contents creation through LINE Camera. In attempt to reach a “Smartphone-life platform”, LINE Channel has introduced service and function including: Line Tools, Time Line (Like Facebook TimeLine for status update), LINE Game, LINE Talk Novel, LINE Fortune, LINE Coupon, LINE Sounds Shop and LINE Coin (virtual currency).

Initially, LINE adopted Redis as the app’s primary storage and data structure server and after the integration of Time Line feature, they switched to HBase for accommodating increasing workload and exponential growth patterns such as Time Line data.

The client contact data is stored on LINE server for easy access and data migration to another device, which make the process of synchronization between different devices easier and more efficient.

LINE Camera, LINE Brush and LINE Card allow users to generate and personalise the contents easily with their simple UI and fascinating functions. All the contents can be shared and exported to other app or social media.

LINE features several simple, one-click functions such as “Shake it” to add friends and one-click sharing. The purchase at its sticker shop is nearly one-step as well, despite the process of entering password for Apple account. LINE Camera also features one-click photo sharing on other social platforms such as Facebook, Twitter, Flickr, Sina Weibo, Tumblr and etc.

LINE allows users to seamlessly store, access and synchronize data across devices such as smartphones and desktop computer. Though there’s still an issue that only the contact data is stored and can be retrieved from the server while the conversation log is stored in device. Another problem is that once users link LINE app with their mobile phone number, the app can only be activated on one mobile device (PC version is not affected).

Suggestions: In my case, I have LINE installed on both iPhone and iPad Mini, it happened to me so many times that all my conversation data was completely deleted on one device when I activated another one. Though the chat data synchronization between PC and mobile version is quite reliable and real-time, I still wish that I can access the app across multiple mobile devices.The other concern with “Smartphone-life platform” is the accessing speed. Most of the features require a bit long responding time than other apps. For example, a lot of users have been complained about the message sending speed of LINE is not as good as its arch-rival, Whatsapp.

List of references applied in the article:
1. Japan’s Line App Evolves into Platform, Expands into… Um… Everything, Rick Martin, July 3, 2012
2. Line messaging and VoIP app adds ‘timeline’ and ‘home’ features, throws in new platform for app integration, Mat Smith, Engadget, Jul 3, 2012
3. Software Above the Level of a Single Device, by Tim O’Reilly, Nov 28, 2007
4. LINE Storage: Storing billions of rows in Sharded-Redis and HBase per Month, by Shunsuke Nakamura, April 26, 2012
5. Advice to Microsoft regarding commodity software, by David Stutz, 2003

6 Best Approaches for Rich User Experience by ASOS!

Being as the UK’s biggest online-only fashion and beauty retailer, ASOS is slowly but steadily increasing its market share in the international markets through the combination of extensively deploying insightful marketing strategies and, more importantly, constantly improving its user experience.

In this article, we are going to examine ASOS as an online retail platform with O’Reilly’s Web2.0 pattern – Rich User Experience and its best approaches.

Let’s take a look at the interface of ASOS website:

Interface design combines the bests of desktop and online experiences:

The interface offers very clear and visible guidance which facilitate the navigation process. Links and tabs provide instant response and information on mouse hover, by which creates a rich interactive and responsive user experience like desktop application.

Usability & Simplicity first

Through appropriate compartment of multimedia contents and global navigation, ASOS gives us a good example of achieving rich user experience without sacrificing the efficiency and usability.

Simplifying and integrating related contents into pop-up menu also helps to improve the process of navigating users to desired contents.

Match the technology usage to the requirements

ASOS was the first UK online store to launched catwalk in 2006. Now it gets virtual. Users no longer need to run their imagination about: does the dress look good on me? Even though the catwalk is no more than a promotional gimmick, it is always better to watch video than pictures.

Another great hit by ASOS is the campaign of digital equivalent queue before the summer sale started in 2012, which achieved an overall ROI of more than 2000%. Through a series of games and viral marketing
on social media platform to encourage users to digitally ‘elbow’ to the head of the queue for early entry to the sale, ASOS successfully turned the existing users into brand evangelists and achieved a new level of engaging
user experience.

Search over Structure

ASOS offers a precisely categorized content structure for user to easily access desired information. All items can be found through submenu links, search box and its comprehensive search refine options.

The search history also offers a certain degree of adaptive personalization to improve the efficiency and convenience of browsing the website.

Preserve content addressability

The website uses XML and Javascripts as scripting languages while the API is RESTful and employs JSON exclusively for both requests and responses, by which ensure the content addressability.

Not to mention that ASOS is the best performing website on natural search among other online retailers.

Deep, adaptive personalization

In order to present personalized information, the application constantly learns from user’s behaviour through recording and analysing each action and preference (“Recent viewed” box, see below picture) then deliver the relevant contents accordingly (“We Recommend” box, see picture below), and even further anticipate users’ need (“buy this look” button, see picture above).

Any room for improvement?


First of all, the font size of submenu is too small for users with poor eyesight. Plus there are too many options to search from, which somehow poses a problem for efficiency. And according to the Eye Tracking research in Human Computer Interaction, users tend to skim through a group of words without carefully examining the contents. I will suggest ASOS to enlarge the font-size of drop down menu, or simply highlight some major categories for users to choose from, thus to improve the visibility.

Secondly, the user experience can be further enriched by employing more prompt and responsive interaction/feedbacks to the links or multimedia contents. The typical mouse hover responses like colour change or slight movement are not enough. Providing concise information on mouse hover about the contents which the link will direct to can effectively save time and improve the usability.

However, while most of the websites with rich user experience may suffer from poor performance and long loading time, ASOS successfully trounced the speed competition by applying the performance testing tool to effectively improve platform performance through complex and functionality rich test and simulating the diverse behaviour of online users. As a result, ASOS has risen from 49th to 9th faster retail site in the UK.

References: – Case studies in The Times 100, by The Times 100 Business Case Studies
ASOS is king of natural search among fashion retailers, by David Moth, 30 April 2012
User Experience Review – ASOS, by Jamie, January 2010
Asos -“Life” Section Review>, by User Vision, 7 May 2010
Expedia, ShopNBC, ASOS enhance mobile sites via HTML5 platform, by Rimma Kats, 10 May 2011
Client Portfolio – ASOS, intechnica, retrieved 31 March 2013

Data makes the difference-Yelp and its story

Starting as an online local business directory service with basic social networking feature in 2004, Yelp has successfully attracted 100 million unique visitors in one month period, January 2013. With more than 22 million user-generated reviews (in 2011), Yelp gained its fruit of victory through pivoting and a set of effective data strategies.

The initial yelp website was not easy-to-use and only received few visitors and reviews. But soon after Jeremy Stoppelman and Russel Simmons, co-founders of Yelp, noticed that an increasing number of users are using the function to leave reviews without being urged, they relaunched the website in February 2005 and pivoted on building a unique and irreplaceable database of authentic, user-generated reviews.

Yelp’s success comes from acknowledging that “Data is the next Intel Inside”, one of the least understood Web2.0 principles from Tim O’Reilly. The pattern is concisely elaborated by Marissa Mayer, Google’s VP, in an interesting interview, she confessed that:

having access to large amounts of data is in many instances more important than creating great algorithms.

So what else does Yelp do to further enhance its data strategy?

      • Creation strategy: set the network effect by default and build up the unique, hard to recreate database by accumulated user-generated contents.
      • Enhance the core data by allowing users to participate in the creation of data: user reviews, review voting, ratings
      • Let users control their own data: users can post their reviews, vote for other reviews and even share them through the integration of social networking sites such as Facebook. User-generated content can further be enhanced by the power of reputation system of Yelp’s online community.
      • Share the control with users: while Yelp owns the content of the website, users are responsible for their own contents
      • Design data for reuse: Yelp offers RSS for users to easily track recent reviews in the newsreader, publish reviews to their blogs or Facebook accounts and invite friends to follow

However, Yelp still received criticism over its review filtering system which claims to identify illegitimate reviews and remove them. The fairness of both negative and positive reviews and how Yelp decides to display on each business’s page is remained ambiguous and unclear.

Who owns the data?

Yelp introduced a feature in 2008 for business owners to manage their listing and keep the information up to date with moderator approval. Though business owners still don’t actually own the data, they cannot edit or delete any contents or negative reviews without the agreement from Yelp moderator.

How to keep the review stay authentic?

Yelp was accused for asking business owners to pay for hiding negative customer reviews on the their business listing in 2009 and in response to increase the data transparency, Yelp added a feature which lists reviews which are filtered.

As an online community providing unsolicited review writing, it is very essential to keep the content stay genuine and unbiased. Underhand review manipulation will not only lose the trust from users, but also pose a severe impact on the collaboration with advertisers.

What can Yelp do to avoid dishonest review and deliberate defamation?

Yelp’s reputation system us like a double-sided sword. We trust the reviews written by Yelp Elites, those Yelp Evangelists who actively generate authentic and useful reviews. But what would happen if business owners pay those Elites or offer free products for them to write the reviews? Are those reviews still true and unprejudiced?

While the concern is more about the morality than legality, I would suggest that Yelp:

  1. Add specific recognition mechanism to make the identity of review authors more transparent. (e.g. connect with Facebook, LinkedIn or other social media identity)
  2. A due process which requires the user to confirm that the state respects all legal rights owed to a person, may be considered as well

Twitter’s Innovation in Assembly

Twitter's Innovation in Assembly

Being as one of the ten most visited websites on the internet, Twitter has rapidly gained its global popularity soon after it was launched in July 2006. The success of Twitter has been widely studied and discussed about how it aligns with web2.0 principles. One thing to look at is how Twitter effectively turns its website into a platform, and fosters the innovation and evolution through the power of network and community.

As web2.0 mindset promotes data to be re-useable, it creates opportunities for companies to simply integrate and merge applications or services provided by others, and generate better outcome than the product standalone.

The web2.0 principle, “innovation in assembly” is described by Tim O’Reilly as

When commodity components are abundant, you can create value simply by assembling them in novel or effective ways.

Let’s see how Twitter utilizes a set of great practices to fully elaborate this principle:

    • Twitter offers API to its platform:

      Twitter’s growth can be attributed to Twitter API which not only allows the service to be further expanded to mobile platform, but also encourages external programmers to build an API upon it and create additional value to it. (Examples of APIs built on Twitter API: Klout API and Topsy.

    • For better development: Data remixability and support multiple standards

      Twitter introduced a new rule in August 2012, which makes the per-endpoint rate limits more restrictive and ensures that all API requests must be authenticated. Data remixability can be realized when data is uniquely addressable and supports multiple formats and delivery mechanisms (Twitter API supports XML, JSON, and the RSS and Atom syndication formats.)

    • Great API practices for the developer community:

      Twitter successfully created a well-structured developer support infrastructure which fosters an active community for programmers to exchange ideas and collaborate more efficiently. Full documentation, sample code in multiple development languages are provided within the infrastructure as well.

    • Build your business model into you API

      Twitter’s API focuses on how to make the service available to users through different platform and access ways. Its core Twitter API even made the service reach users through mobile platform before the production of Twitter mobile app.

    • Use Web 2.0 to support your platform

      Twitter applied Web 2.0 practices such as “reward users first” by minimizing the barriers of adoption and fully “utilizing network effects” to build a vibrant ecosystem.

    • Use your platform to build customer trust and loyalty

      Twitter applied REST API methods allow developers to access core Twitter data. This includes update timelines, status data, and user information. The Search API methods give developers methods to interact with Twitter Search and trends data.

    • Learn from how your customers remix

      Twitter’s official iPhone application started from an external developer’s project, by which sufficiently illustrates how Twitter learn and adopt ideas from its users.

What’s more?

After the release of Twitter REST API v1.1 last September, the company has announced to retire API v.1 in March 2013, by which all unauthenticated client-side API calls will not be supported and other older widget users should switch to its Embedded timeline. Followed by the retirement of Twitter API v.1, TwitterDeck AIR and TwitterDeck Android/iPhone will be discontinued soon.

In response to those changes, Twitter promises its users a fast, feature-rich web –based application for modern browsers and a chrome app:

Twitter regards this action as “a reflection of where our TweetDeck power-users are going.” And in the future, all new capabilities will be introduced on this web-based application first, then Mac and PC apps.


Twitter API changes kill off Tweetdeck apps, GMA News, March 5, 2013
An update on TweetDeck, by Twitter TweetDeck Team, March 4, 2013

5,000 APIs: Facebook, Google and Twitter Are Changing the Web, Adam DuVander, February 6, 2012
Twitter’s Other Ecosystem: Twitter-derived APIs Double in One Year, Adam DuVander, May 26, 2011
Salesforce Marketing Cloud Launches Social Ads Platform For Twitter With New Twitter Ads API, Michael Lazerow, Feb 20 2013 
What’s Driving Twitter’s API Changes?, Bob Fine, September 7, 2012
First Look at Twitter’s New Ads API, Geoff Simon, March 11, 2013