We’re huge fans of Twitter – both as users and observers of the impact the Twitter API. Since it was opened, Twitter’s API has shown how providing access can unleash huge waves of innovation – giving rise to clients, data businesses and much more.
So it’s very sad to see the news today that the company will be cutting off their firehose partners. This will directly affect third party data re-sellers (DataSift already responded) and end customers. However, it is likely to affect not only them, but also be very negative to Twitter in the long run.
There are no doubt business drivers for the decision which are not visible on the outside. We also have no insight into the precise business relationship between …
At 3scale, we are API nerds, and we are surely not the only ones if you look at the number of API-related events around the world. During the year we participate in a lot of conferences and meetups with the API community, but nothing really existed in our local community of Barcelona besides the yearly APIdays Mediterannea.
We wanted to host a local group for hackers to exchange ideas about APIs and show the world that Barcelona has an active tech scene. This meetup would let local hackers present their work on APIs, as well as give them the opportunity to hear world-class international speakers. We plan to host this meetup regularly, every 3 months at 3scale HQ.
What better time than the week of Mobile World Congress to do the first meetup?
This year at the API Strategy & Practice Conference (APIStrat) in Chicago (Sept. 24–26) we are trying something new – the API Speed Hack.
What is it?
Think of the Speed Hack as a “performance enhanced” hackathon. We think it’s a very effective, practical and fun way to promote APIs to developers.
The idea of consuming rich content on small, portable devices – referred to as the Third Screen vision – has been around for a while. Currently, there is a lot of momentum in this space indicating that this vision is becoming reality. Additionally, third screens are not only used for directly consuming content, a more frequent use case is actually to use mobile devices to augment the content consumption experience on another (larger) screen like a TV.
Several technical advances such as more powerful hardware, better screen technologies and more bandwidth provided by improved wireless transmission technologies are the foundation for this trend. TechCrunch cited a recent study
Sharing API calls between your server side and the client’s browser is actually critical to making some Twitter integrations work and there’s a great tip on how to use server side caching:
You can call the API from the browser, display the results, and then call your server with the data you got from the API. In effect you are using all of the user browsers as a large collection grid. This approach can be used to reduce the amount of API calls you have to do from the server.
API Rate Limiting: Mapping Use Cases
This type of technique highlights how important it is for API Providers to map out the use cases they aim to …
Twitter once again made news this week with its 1.1 API terms and in particular the decision to drop support for RSS and ATOM. As with previous policy announcements (see our thoughts from early August here) this has caused unhappiness in various places and worry about further data lock-in by Twitter.
Presumably Twitter has reasons for the switch (it cites complexity of maintenance and their new #hashtag list follow features as reasons) so it is difficult to comment accurately. However, it seems useful to reflect on the differences between RSS and an API – this is something we’re very often asked at 3scale “why do I need an API when I already have RSS”.
“What do people expect – they got a free ride and now the gravy is running out”.
“Twitter is evil – nobody should trust it in the first place”.
APIs have deeply change the way innovative tech companies are building products, by allowing them to focus on their core value-adding service. It’s a bit like in the Apple ad: “there’s an API for that”.
Interview with Stanislas Polu, co-founder and all things Tech at Teleportd. Before this first entrepreneurial experience at Teleportd, he worked as a software engineer at Apple, Oracle and Quarter FS. He holds an degree from Ecole Polytechnique and a MSc in Computer Science from Stanford University.
Tell us more about Teleportd
Teleportd was born out of the observation that despite the number of images that were being taken from mobile devices and shared on “public” social networks, it was hard to access the data in transversal ways. Seeing all the latest pictures from a given location was a challenge, so was looking at images across platforms on a given key word. We set out to build a …
Business Strategy to drive the API
Many companies are embarking on initiatives to open their API. However, most API initiatives still do not fully harness the real potential that an API brings. Sometimes this is due to organizational reasons – such as being run as a side project in the engineering team. Often though, it is because of the lack of a rigorous process to ensure that all the creative options are investigated on how to adapt the business model. It is like getting into a car and just following the road ahead; instead of checking a map to see where you want to go and which the best route to take is.
The objective of this article is to define a structured approach to identify which business model will ensure that your API makes the most effective contribution to your business. Before we get to the meat of the business model options, the first step is to decide which your core assets are, and how you wa…