Businesses exploring an API strategy are asking themselves: private, partner or public? Since the start of the year, there has been a lot more thinking aloud about how businesses decide whether to start with an internal (private) API; use partner APIs to manage specific business relationships; or jump straight into designing external, developer-facing open (public) APIs.
As part of its ongoing effort to turn its cloud service into a platform for enabling the delivery of application service, Box this week announced The Box Services Partner Program, a new network of systems integrators and consultants focused on helping organizations transition to the cloud.
Today, Box announced a few developer-centric moves it hopes will fuel enterprise adoption and the app economy. First, Box revealed Box $rev–a program through which developers can monetize applications integrated with or built on the Box OneCloud platform. Box $rev monitors third party app integration and developers receive compensation based on integration levels. Additionally, Box released new SDKs for iOS and Android. The new SDKs allow developers to easily build apps that seamlessly integrate into Box with enterprise level security and scalability.
Duedil API widens its reach with company information from 20 additional countries across Europe. Box Developers can now take advantage of its HIPAA Compliance Plus: Khronos to create Camera Control Open Standard API and 9 new APIs.
Our API directory now includes 95 sharing APIs. The newest is the Screenhero API. The most popular, in terms of mashups, is the Zillow API. We list 79 Box.net mashups. Below you’ll find some more stats from the directory, including the entire list of sharing APIs.
Gartner analyst Laura McLellan made a bold statement in her 2012 webinar: “By 2017, the CMO will spend more on IT than the CIO”. While I think it is too bold a statement, you can’t deny the fact that an eco-system shift is happening and API Management is the catalyst. From my own personal experience, I can vouch for this shift in who is doing the big spending. A new set of tools are enabling CMOs to create new, powerful channels. They are called APIs. The very introduction of these APIs are resulting in new ways of leveraging channels and exposing content, media, and data to customers, partners, the community, developers, and even to the public.
Box continues to encourage creativity and innovation with its ongoing parade of challenges, competitions, and hackathons. Its latest quest to engage the developer community arrives in the form of a Risk-inspired online battle: BRISK. BRISK started as a typical Box challenge; however, to date it has developed into its “own wondrous virtual world, complete with it’s own servers, it’s own API and it’s own set of rules.” The strategy and competition have become intense and complicated, but the goal remains simple: “devise the optimal strategy for your bot to take over the world.”
Humans are great at observational learning. As children we learn by observing the goals, actions and outcomes of others. Many programmers have applied this style of learning to improve their craft by studying and understanding code written by their peers. The same is true for our API design world. Reviewing and dissecting the web APIs that are available on the web can provide us with enormous insight into the design of APIs in general. In this post, we will look into the Box.net API and see what we can learn.
There is a bold new version of the Box.net API, as the enterprise-focused file sharing company iterates on its platform. In the interview below, we discuss the future of APIs with Box’s Peter Rexer, the first in a series conducted by ProgrammableWeb and Hojoki (where I work), an aggregation tool for apps such as Google Drive, Dropbox and Evernote, that helps support team work.