This is the second of two articles on the growing trend of API-first design. In this article Uri Sarid, CTO of MuleSoft (parent to ProgramamableWeb), discusses the approaches to API-first design. He touches on the value of this approach and how it allows businesses to optimize for a great API instead of having the API simply be a reflection of existing code. Previously, Patricio Robles explored real-world examples that illustrate why API-first design is an emerging trend.
This week, we had 59 new APIs added to our API directory including a flu outbreak tracking application, an online business launching tool, and an online management system for churches. We also explored the top tools that help developers mock web services instead of starting from scratch.
Chris Sheldrick, CEO of the London-based company what3words, has taken a novel approach to the task of navigation with a new API. Sheldrick’s idea stems from the logistical difficulties he encountered while working internationally in the music business. During that period in his career, Sheldrick was faced with coordinating the rendezvous of dozens of people in remote locations. Despite his best efforts at communication, people would still find themselves calling one another on the day of a meeting, seeking clarification on the location of the meeting place.
In one of the opening sessions at today’s NordicAPIs, co-organizer of the event and CEO of Twobo Technologies, Travis Spencer, urged businesses to not only adopt an API strategy, but to reorient their businesses towards becoming an API platform. It is a bold assertion that previously has only been taken up by large players (US telco AT&T speak about reorienting as a platform for example), yet Spencer is saying that in order to succeed, all businesses will need to reorient – and the sooner the better.
This week at Dreamforce, Salesforce.com CEO Marc Benioff, announced Salesforce1. Benioff suggested that Salesforce1 could be the single platform to run entire companies, and manage the internet of things from a single source. However, the bigger story behind Salesforce1 is an API story. How else can a single platform claim to “Connect all your apps. Connect all your devices. Connect all your customer data.”? Increase your APIs tenfold is how.
This week, we had 54 new APIs added to our API directory including a social people search API, a multi-lingual social network, and a product information and pricing provider. We also discussed hackathons and the top 10 mistakes in running hackathons.
Pinterest reveals more about its API. Amazon Web Services launches CloudTrail for user visibility tracking. Plus: Twitter announces timelines for hashtags, APIMetrics offers service to monitor API performance, and 10 new APIs.
As companies, organizations and professionals become more and more interconnected via social networks such as Twitter, LinkedIn and Facebook, a new trend is beginning to emerge—social network data visualization. So let’s make a data visualization of our own.
Hackathon events continue to be a key strategy used to promote API products and services. For developers, they provide an opportunity to work on solutions to real world problems, create new networks of like-minded technologists, connect with potential clients, and provide a chance to hone core developer skills from programming to pitching.
Hackathon event planners are encouraged to read ChallengePosts’ top 5 keys to a successful app challenge. For competitors, we have already covered one key piece of advice: book your place in a hackathon early. This year has seen an explosion in growth of hackathon events, but surprisingly, this is yet to outstrip demand for new competition opportunities.
But once you have booked in to a competition, how can you best prepare to compete? Many hackathons operate over 24 hours or a weekend. How can you maximize the productive time you spend when the clock of a hackathon starts counting down?