Last week, the Nordic APIs team took on 4 events in 4 Northern European cities in 4 days. There was something for everyone in an agenda that covered API neo-security frameworks, the latest trends in B2B integrations, how government agencies are opening up their data, and API usability best practices.
APIs are at the heart of a new initiative aimed at giving the U.S. government the agility and flexibility needed to serve today’s citizens, communities and businesses. The White House’s General Services Administration (GSA) has established “18F,” a new department aimed at providing open source tools and demonstrating new ways of working with entrepreneurs and innovators to deliver digital services to government agencies, businesses and citizens.
API Strategy and Practice officially kicked off in Amsterdam this morning. After yesterday’s afternoon workshop sessions (see our separate coverage of the CitySDK workshop), this morning commenced with a packed room of developers, API providers, service managers, business innovators, and startup entrepreneurs, all ready to spend the next two days talking APIs.
Readyforce has announced a single hub for companies to discover, sponsor, and connect with student-run hackathons: HackerHub. W3C has published a working draft of a Clipboard API. Plus, the debate over an open government and APIs continues and 10 new APIs.
For a public API, adoption is key. Finding the right developers can be resource-intensive. Few can afford to blanket the web and every conference in advertising. Even if you could, the results might not be nearly as good as the methods covered below. In this post, I’ll provide an overview of five or six ways to increase API adoption, along with specific tactics within each strategy.
Code for Seattle and other civic hackathons this weekend. Cyborgs and self-aware robots to start demanding equal access to APIs? Plus: WSO2 Rome workshop on implementing an API in an SOA, Smart API is released, and 6 new APIs.
Having an intuitive developer portal is only the beginning of building your API community. Both online and offline aspects can really help you engage with the developers who use your API. The same methods can also help you identify or attract potential developers. These are all pretty much must-haves, but be sure to share in the comments the ones that you think are most important.
As pharmacy retail giant Walgreens has announced a new revenue sharing program that rewards in-app developers using its QuickPrints API with a bigger slice of the customer pie, we take a closer look at the business model behind the API.
It’s easy to forget that private APIs are the norm. Putting together the right public/private API strategy requires identifying the risks and needs of your business, and making smart moves to take things in the right direction.