Skip to main content

Twitter and wrong business decisions

You've must have been on a trip to Mars if you haven't heard about the ordeal of Twitter, saying they close down their services to give it's customers (???) a consistent user experience. In short, they don't want external developers to further develop applications on their API.

This blog article is not about bashing some more on decisions made by Twitter's management and VC's, but to open up a discussion to see if there's no better value to be found for the company to make money without killing innovation. I'd like to know your points of view on this discussion, maybe not to save Twitter, but the next best thing that comes along feeling pressure of VC's wanting to see money for their hard invested money.

If I was a VC or a major stockholder of Twitter company, I'd think twice on killing competitive client developers! [Editorial: I'm no VC nor stockholder, but I do run a business]

First of all you don't have the world geniuses working at Twitter, so you might kill innovation that could bring your service on the next level. I love how CoTweet allows teams to share one twitter resource and delegate tasks to each other. This is just one of the many innovations that sprung out of nowhere just because of the existence of Twitter.

Adds, good to have them but the revenue you earn on adds is still peanuts compared to other solutions, although in the case of Twitter those are a lot of peanuts. Don't use a stupid bar that annoys people (because it's intrusive and unwanted). Inject an add in between every five or ten tweets, like commercials do on TV or in the newspaper. Twitter is the source, so it's easy to implement it. You can even have trending, profiled or geolocated ads send to individual users as Twitter has all that data. Bang! There's some real money to be found.

The added value for Twitter can also be found in it's eco-system, as "to tweet" is generally recognized as a verb. Take a look at GitHub's business model! They've a free platform to share code with the world, but charge for private use. I am sure there's a lot of potential right there, as more and more people are so familiar with sending out a tweet, it can co-exists within companies as their own private twitter flow. Even more, for enterprizes like newsmedia it can also be a business model to have a "sticky" tweet to give them extra attention when major events occur (like we see now in Japan). Even give international aid services a "place" to show where people can contribute, but I suggest to make that a free service.

One thing I do want to say to the folks over at Twitter is this: you have a huge user base and you might keep it for a very long time. But don't forget, it can all be over when someone comes up with the next best thing. You've provided a service that's been used to provide event coverage as it happened, crumbled governments in North Africa, witnessed thousands of reunions of people being at the same spot and so much more. Developers are building new tools on top of that for giving people an added experience on top of what you've originally set up. Closing the doors now on those developers is not just acting as a jerk, but is also a motivation for developers to come up with the next best thing a whole lot quicker.

Let's talk and see how you can become again the hero you used to be.


  1. That's exactly what will happen, someone will come up with the next best thing, which will be someone offering a nice public API again... and the cycle starts again.

  2. Very interesting post you have made here

  3. According to my view twitter is an very good network to promote any kind of business.I really enjoyed reading your blog and get enough information.Thanks for your words.


Post a Comment

Popular posts from this blog

PHP 7 and Apache on macOS Sierra

I posted several talks about compiling PHP from source, but everyone was trying to convince me that a package manager like Homebrew was a more convenient way to install. The purpose of Homebrew is simple: a package manager for macOS that will allow you to set up and install common packages easily and allows you to update frequently using simple commands. I used a clean installation of macOS Sierra to ensure all steps could be recorded and tested. In most cases you already have done work on your Mac, so chances are you can skip a few steps in this tutorial. APACHE AND PHP WITH HOMEBREW I’ve made this according to the installation instructions given on GetGrav. The installation procedures These installation procedures will set up your macOS Sierra with PHP 7.1 and Apache 2.4. Install Xcode command line tools (if not done yet)xcode-select --install Install Homebrew/usr/bin/ruby -e "$(curl -fsSL" Set up for in…

Speeding up database calls with PDO and iterators

When you review lots of code, you often wonder why things were written the way they were. Especially when making expensive calls to a database, I still see things that could and should be improved.
No framework development When working with a framework, mostly these database calls are optimized for the developer and abstract the complex logic to improve and optimize the retrieval and usage of data. But then developers need to build something without a framework and end up using the basics of PHP in a sub-optimal way.

$pdo = new \PDO( $config['db']['dsn'], $config['db']['username'], $config['db']['password'] ); $sql = 'SELECT * FROM `gen_contact` ORDER BY `contact_modified` DESC'; $stmt = $pdo->prepare($sql); $stmt->execute(); $data = $stmt->fetchAll(\PDO::FETCH_OBJ); echo 'Getting the contacts that changed the last 3 months' . PHP_EOL; foreach ($data as $row) { $dt = new \DateTime('2015-04-…

Sessions in PHP 7.1 and Redis

In case you have missed it, PHP 7.1.0 has been released recently. Now you can’t wait to upgrade your servers to the latest and greatest PHP version ever. But hold that thought a second… With PHP 7 lots of things have changed underneath the hood. But these changed features can also put unexpected challenges on your path. Our challenge One of these challenges that we faced was getting PHP 7.1 to play nice storing sessions in our Redis storage. In order to store sessions in Redis, we needed to install the Redis PHP extension that not only provides PHP functions for Redis, but also installs the PHP session handler for Redis. Because we upgraded our servers to PHP 7.1, we were looking to use the latest provided version for this Redis extension: redis-3.1.0. Once installed, we bumped against a nasty problem. Warning: session_start(): Failed to read session data: redis (path: tcp:// Searching the internet for this error, we didn’t got many hits that could point us into a dire…