API Strategy / Enterprise Modernization
Tuesday, October 27, 2020
Integrating into an API is not always as easy for partners as it can be. Shutterstock’s API was built to provide easy access to the company’s content and technologies so that partners such as Facebook, Google and IBM can leverage it in their own their platforms. The goal is to ultimately drive business results for partners by making user workflows frictionless and providing flexibility for developers. In this session, learn the tools and solutions that allow partners to easily plug into your content and provide a seamless experience to their users. Shweta will discuss using modern technologies and API standards such as OpenAPI, building sandboxes, auto generating SDKs, and self-documentation to allow for efficient integration and faster results.
By extensive use of APIs to a myriad of back-end citizen service applications, municipalities can provide a full-service, round-trip, 24x7 experience and resolution to all customer requests for service. Whether it be a Water start/stop, bill payment, trash collection, library book request, fire inspection or a police non-emergency request, APIs can revolutionize the entire resident service request fulfillment, by municipalities, via a single customer facing portal.ent
API integrations and the reasons a business would want to do them are plentiful. Many are driven by wanting to drive higher user (employees and customers) productivity, greater employee engagement, or reducing busywork and task switching in order to increase, quicker, smoother cross-application workflows. As APIs are built multiple and different types of vendors are involved, fostering some critical business considerations. Steve Wilson will share his insights from building dozens of these integrations, detailing the critical business considerations to keep in mind about business restrictions and terms of service to put around APIs. He will explain how to set up a win-win alliance between your business and other vendors involved so that everybody's business model wins.
Creating APIs is more than just writing reading some docs and writing code. Your API is the interface developers use to access and take advantage of your company's services. And that developer experience (DX) deserves to be first-class whether you are dealing with important third-party devlopers, key partners, or just other teams within your own organization.
This workshop covers the basics of both designing and building APIs through the use of a series of handy command-line tools and existing services and open source tools. You'll learn about API-First design, using diagrams to map out your APIs, and API definition languages like Swagger and others to document your APIs. You'll also learn how to use NodeJS and the Sketch-Prototype-Build pattern to implement the right API design quickly and safely. And, finally, you'll learn how to use automated testing and deployment to get your API up and running on public servers.
Good design and implementation can reduce errors, improve API adoption rates, and contribute to the bottom line. Whether you are an experienced API developers looking to sharpen your skills or you new to APIs and want to start learning, this workshop will help you in your effort to design and build great APIs.
There are no shortage of API metrics you could track, but how do you aligned to business outcomes. This workshop takes a deep dive on how to align metrics to three key goals: Adoption, Engagement, and Retention. Then, we'll discuss changes you can make to your developer experience for improving these areas.
In this session I’ll cover our newly defined and implemented product-led software development lifecycle, centered on API first design. The process has one end-goal in mind: improve our customer's experience with our software and APIs. That is, build our software with end users in mind. Easy to say, more difficult to enact.
Planning is great, but action and implementation must follow. We have created an API first development CI/CD automated pipeline, following design-first industry standards and tooling. We’ve moved away from the siloed dev → test → doc → deploy methodology. The workflow involves multiple teams from the outset. Development, designing, testing, and documentation all have their part to play, with product management coordinating, leading, and owning the entire process.
While I can’t go into details of each step of the workflow, I’ll provide enough conceptual and technical insight to get an idea of what we’re doing, how we’re doing it, and the tools we’re using. I’ll also cover how we’ve worked with our design team to educate the various product teams through design workshops. Finally, I’ll touch on some mid-stream adjustments, lessons learned, and outline the next steps in our journey.