Increasing API Adoption via a Code Playground

•Als PPTX, PDF herunterladen•

1 gefällt mir•2,306 views

This session will elucidate what is an API Code PlayGround, and how does it create a phenomenal developer experience. We'll be focusing the two main components of the Code PlayGround: SDKs and Reactive Code Samples. Developers love SDKs — simply because SDKs lift heavy burden of communicating with an API, and let developers focus on the app design and business logic. On the other hand, Code Samples provide the quickest way to the first “Hello World” application. Combine both as a Code PlayGround, and you’ll get developers up and running with your API within no time.

Technologie

Code
S. Adeel Ali | adeel@apimatic.io
@APIMatic | @AdeelAli25

SaaS
API
First
Mobi
le
First
Web
First
@APIMatic | @AdeelAli25

Software
Product
@APIMatic | @AdeelAli25

API
Software
Product
@APIMatic | @AdeelAli25

API
Software
Product
Developers
@APIMatic | @AdeelAli25

API
SaaS
Product
Developers
@APIMatic | @AdeelAli25

Don’t Make
Me Code
https://medium.com/the-opsee-blog/let-s-talk-about-developer-experience-dx-design- @APIMatic | @AdeelAli25

Product/API Adoption
@APIMatic | @AdeelAli25
∝

∝
Achieving the User Goal in the Least Possible
• Number of Steps
• Time
@APIMatic | @AdeelAli25

∝ Getting Started / Ref
Docs
Sample App Code
Authentication Code
API Interaction Code
API DX = Least Steps & Time to
the First Hello World
Hello World
@APIMatic | @AdeelAli25

Checks and
Validations
Encode Inputs
Serialize body
Build HTTP
request
Make HTTP
Call
Deserialize body
Decode to output
Handle errors
Getting Started
Docs
Configuration
API Call
Arguments
Authentication
∝
Hello World
@APIMatic | @AdeelAli25
API DX = Least Steps & Time to
the First Hello World

API Call
Arguments
Encode
Inputs
Serialize
body
Build HTTP
request
Make HTTP
Call
Deserialize
body
Decode to
output
4 - Static
1 - Static
2 -
Interactive
3 -
Interactive
∝
Hello World
@APIMatic | @AdeelAli25
API DX = Least Steps & Time to
the First Hello World

API Call
Arguments
Encode Inputs
Serialize body
Build HTTP
request
Make HTTP
Call
Deserialize
body
Decode to
output
4 –
SDKs/Client
Libraries
1- Getting
Started
2 – Dynamic
Code Samples
3 – Assisted
Auth
∝
Hello World
@APIMatic | @AdeelAli25
API DX = Least Steps & Time to
the First Hello World

• Your developers should be using your API like they use any other product
• For the best DX, Don’t make them code.
• Give them what they need to get started. Let them focus on what they ar
@APIMatic | @AdeelAli25

DX
@APIMatic | @AdeelAli25
Thank You
If you talk to a
man in a
language he
understands, that
goes to his head.
If you talk to him
in his language,
that goes to his
heart

Weitere ähnliche Inhalte

Mehr von Pronovix

API docs frequently fail to address developers’ needs by omitting common usage scenarios and use cases. Let’s take a look at good and bad practices for documenting API use cases, and take steps to ensure that developers get from our API and docs what they really want. You wrote an API specification, documented your endpoints, and published SDKs. Here’s a question, though: Does your API actually solve your users’ problems? API providers often fail to address common use cases to solve users’ needs, or their assumptions don’t match the reality. This may end up in frustration and loss of users. In this talk, we will take a peek into developers’ mindset. I will show how to better understand the developers’ needs by researching the usage patterns, existing libraries and 3rd party experience layers, provide examples of good and bad practices, and suggest actionable steps to improve developer experience for your API.

Why your API doesn’t solve my problem: A use case-driven API design

Pronovix

unREST among the docs

Pronovix

Nobody likes ambiguity—especially when it comes to the stability of APIs and the expectations for availability long term. Avoid common pitfalls and explore a critical area where trust is built with developers through thoughtful policy and the development of best-in-class documentation. A good deprecation policy involves a lot of forward thinking and an awareness of how developers or end users are currently leveraging your capabilities, and how a given API or feature deprecation could affect them in the future. The hard-earned trust that you’ve built and maintained with these individuals is at risk with any type of policy or documentation that is unclear. The road to developing a clear, trustworthy deprecation policy is a multi-faceted initiative with input from product, engineering, customer success and other cross-functional teams, as well as external market awareness. Knowing which voices to have in the room, what the industry standards are, and formulating appropriate communication timelines will ensure a world class policy is developed and documented before it’s needed. Join us as we dive into the nuances of this process and how to avoid the common pitfalls that come from lacking a strategic, thoughtful approach to documenting a deprecation policy for your APIs.

Developing a best-in-class deprecation policy for your APIs

Pronovix

At MongoDB, we now generate REST API references for MongoDB Atlas from annotations in the product’s source. Our team’s writers proposed, planned, led, and implemented this project–and learned a lot along the way. We’ll share how we got buy-in from engineering and product stakeholders, coordinated the project across teams, implemented swagger-core annotations in Java, and drove positive change to benefit our team, the company, and our users.

Annotate, Automate & Educate: Driving generated OpenAPI docs to benefit everyone

Pronovix

It turns out there is no single answer. Developers may have unique goals, motivations, constraints, and challenges, and all of these influence how they approach the problem in front of them. However, more than a decade ago, three development styles were identified - systematic, pragmatic, and opportunistic - and the academic literature suggests that these still exist today. Two of the three approaches, the systematic and the opportunistic pattern, can be considered as opposite extremes, while the pragmatic approach is situated in between and is similar to both. It is not a personality trait - people may approach a situation one way or another depending on their circumstances, goals, and motivations (however, they may also have a preferred approach, which is usually their characteristic). Understanding the differences between these patterns (and the different needs) helps us to design in a way that serves most of the users, and even helps them to get into a state of flow by providing the optimal level of challenge to solve their problem.

What do developers do when it comes to understanding and using APIs?

Pronovix

It's time to take the bias out of code, UI, docs, configurations, or our everyday language by ensuring we choose our words carefully to avoid harmful subtext or exclusion. We can do our part and take steps by examining assets from code to config files to API specifications to standards. Heard of suss? You can suss out more information or you can find someone's information to be suss. "Suss" shows the flexibility of language. It’s an ongoing process to change how we use certain words. It's important to choose words carefully to convey the correct meaning and avoid harmful subtext or exclusion. Let's explore some of the tools and triage methods that it takes from an engineering viewpoint to make bias-free choices. How can you ensure that biased words do not sneak into code, UI, docs, configurations, or our everyday language? First, let's walk through how to take an inventory of assets from code to config files to API specifications to standards. Next, by placing those findings into categories, prioritize the work to substitute with inclusive alternatives. Let's examine some examples using both API and code assets. Next is a demonstration of how to automate analyzing your source code or documentation with a linter, looking for patterns based on rules that are fed into the tool. What's in the future for these efforts? Inclusive language should expand beyond English and North America efforts. To do so, let's organize the work with automation tooling, as engineers do.

Inclusive, Accessible Tech: Bias-Free Language in Code and Configurations

Pronovix

How to create documentation and write code for an international audience, not just the people who speak and think like you. Make your APIs more useful for everyone on the planet. Much of the documentation supplied by both Open Source and Close Souce projects assume the community have a good understanding of the English language and often North American culture as well. This creates barriers for many solution providers, who are the gateway to potentially huge markets for your project. This talk discusses some of the cultural differences, particularly for people from Asia, in using English language API documentation. It suggests some strategies to help diverse audiences understand you APIs and create solutions using them. The talk will cover not only differences in language but also other cultural differences that are often not obvious. For example: Different expectations about publication formats, release processes, levels of support during the development process Meeting and communications styles Software development workflows, processes, and tools Supporting people who are visually impaired will also be briefly discussed. As well as discussing these issues, specific suggestions will be provided to make API docs accessible for as many people as possible. This talk is based on Alec's work with customers in Europe, North America, Middle East, Asia, and Australasia. The last five have been spent as a developer evangelist working with PaperCut partners in China, Japan, Korea, US and Europe.

Creating API documentation for international communities

Pronovix

APIs in a modern enterprise are rarely uniform or all of the same type. The multitude of API types can be due to organic growth, mergers and acquisitions, or any number of other reasons. Regardless of their origin, APIs of all types need to be fully documented to facilitate a developer’s journey as they interact with your API ecosystem in order to develop useful applications. In this talk I will show examples of how we have augmented developer portals to document APIs that are not of the REST variety, such as AsyncAPI, GraphQL, SOAP, gRPC, and more, such that all API documentation can seamlessly live side-by-side.

One Developer Portal to Document Them All

Pronovix

We are a software engineering team creating API docs. Docs are authored using Instructional Design principles to narrate use-cases and practical API implementations. This talk shares why & how we've applied software development practices to evolve our document tooling, creation, & delivery methods. Our APIs describe asynchronous protocols used for embedded software (firmware) components in a digital 2-way radio communications system. The API is protocol data unit (PDU) based and its definition is described in a proprietary format; consequently, well-known API formats, such as Swagger/OpenAPI, or tools, such as doxygen, are not used. Our product training and technical writing teams are very experienced in Instructional Design methods, but these teams have only written documentation for an end-user audience. Understanding software development processes is equally important as understanding two-way radio networks in order to successfully integrate with the APIs. This is the rationale for having a software engineering team develop the skillsets to write API documentation for a developer audience. With a solid foundation of API documentation in place, regular examination of engineering efficiency and developer experience is appropriate. Repeated actions can be replaced by automation. Content can be modular and re-usable. Formats can be streamlined for easier consumption. Docs can be made portable and lightweight for faster delivery.

Docs-as-Code: Evolving the API Documentation Experience

Pronovix

Ever wonder how some products are just lovable and easy to use while other are not? The good products have optimized onboarding into their ecosystem where you get the information served at the right time. That’s thanks to developer journey and we will teach you how to get it right! We will go through the basics such as how to analyze existing and non-existing developer touchpoints, set metrics and optimize them to increase the conversion.

Developer journey - make it easy for devs to love your product

Pronovix

Deliberate Complexity Conferences - 19 JULY 2022 Alicia Juarrero - Complexity is not complicatedness Professor Alicia Juarrero, a leading complexity theory philosopher and academic, as well as the founder and president of VectorAnalytica, a technology company that specializes in large scale scientific data capture and real time analysis tools. Alicia's work in complexity theory is widely quoted by thought leaders in the technology space and referenced in many recent complexity-informed approaches for managing highly dynamic systems, as well as in knowledge management.

Complexity is not complicatedness

Pronovix

How cognitive biases and ranking can foster an ineffective architecture and d...

Pronovix

APIs: Semi-permeable, osmotic interfaces

Pronovix

How to develop an API ecosystem in the fintech industry from the ground up

Pronovix

Open sourcing Adyen’s API explorer

Pronovix

Creating Interactive Docs with Postman

Pronovix

Technical writing is rarely taught in code schools or listed among the qualifications for an engineering job. Yet developers rely heavily on documentation to use the tools they need to use. Not only that, decisions about which tool to use often take into account the availability of quality documentation. It’s important not to leave the task of writing docs to technical writers who may not fully understand the underlying technology or use cases. This talk will teach you the basics of technical writing–from tutorials and API reference guides to pull requests, release notes, and even code comments - so you can increase adoption of your software and keep the developers using it happy.

The Joy of Docs, or, Technical Writing for Developers and Engineers

Pronovix

I’d like to share how technical writers can pair up with product and development teams to measure and improve API references usability with additional content: use cases and best practices. We’ll take a closer look at the API design challenges and practical solutions. We’ll touch on the importance of spotting development and product biases when designing and developing the APIs, especially if technical writers were not involved in the process early on. I’ll share examples of how I work with multiple teams and manage dependencies, the tools we use, and the organizational methods we rely on to collaborate effectively. I will guide everyone through an API reference review example and discuss how writers can use API reviews as a way to get everyone, from design to development, on the same page.

Measure and improve API references with use cases: challenges and best practice

Pronovix

This talk describes the development of ABN AMRO’s API handbook, the single-source of truth for the development and management of internal and external API products. Our company is moving towards an API-First culture and mentality. Streamlining the development process is key to enabling this. In the beginning, API development knowledge was not documented or centralized in one location. Accurate information was not available for developer teams and they were not aware of what exactly the process entailed. My colleague and I began by making agreements on how the overall process works, describing it in an intuitive way, and then by making it open and accessible company-wide. This involved setting up and hosting face-to-face meetings or MS Teams calls with specialists to find out what was required This talk describes our approach to gathering content from experts, defining and refining processes, obtaining feedback from readers, and redesigning the content in a more user-centric format.

Blood, sweat, and creating an API handbook

Pronovix

Leveraging API Docs and Tools at Mercedes-Benz /developers

Pronovix

Mehr von Pronovix (20)

Why your API doesn’t solve my problem: A use case-driven API design

unREST among the docs

Developing a best-in-class deprecation policy for your APIs

Annotate, Automate & Educate: Driving generated OpenAPI docs to benefit everyone

What do developers do when it comes to understanding and using APIs?

Inclusive, Accessible Tech: Bias-Free Language in Code and Configurations

Creating API documentation for international communities

One Developer Portal to Document Them All

Docs-as-Code: Evolving the API Documentation Experience

Developer journey - make it easy for devs to love your product

Complexity is not complicatedness

How cognitive biases and ranking can foster an ineffective architecture and d...

APIs: Semi-permeable, osmotic interfaces

How to develop an API ecosystem in the fintech industry from the ground up

Open sourcing Adyen’s API explorer

Creating Interactive Docs with Postman

The Joy of Docs, or, Technical Writing for Developers and Engineers

Measure and improve API references with use cases: challenges and best practice

Blood, sweat, and creating an API handbook

Leveraging API Docs and Tools at Mercedes-Benz /developers

Kürzlich hochgeladen

Accelerating FinTech Innovation: Unleashing API Economy and GenAI Vasa Krishnan, Chief Technology Officer - FinResults Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

apidays

The presentation was made in “Web3 Fusion: Embracing AI and Beyond” is more than a conference; it's a journey into the heart of digital transformation. The conference a provided a platform where the future of technology meets practical application. This three-day hybrid event, set in the heart of innovation, served as a gateway to the latest trends and transformative discussions in AI, Blockchain, IoT, AR/VR, and their collective impact on the information space.

AI in Action: Real World Use Cases by Anitaraj

AnitaRaj43

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

AI+A11Y 11MAY2024 HYDERBAD GAAD 2024 - HelloA11Y (11 May 2024)

Samir Dash

Dubai, often portrayed as a shimmering oasis in the desert, faces its own set of challenges, including the occasional threat of flooding. Despite its reputation for opulence and modernity, the emirate is not immune to the forces of nature. In recent years, Dubai has experienced sporadic but significant floods, testing the resilience of its infrastructure and communities. Among the critical lifelines in this bustling metropolis is the Dubai International Airport, a bustling hub that connects the city to the world. This article explores the intersection of Dubai flood events and the resilience demonstrated by the Dubai International Airport in the face of such challenges.

Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...

Orbitshub

Dubai, known for its towering skyscrapers, luxurious lifestyle, and relentless pursuit of innovation, often finds itself in the global spotlight. However, amidst the glitz and glamour, the emirate faces its own set of challenges, including the occasional threat of flooding. In recent years, Dubai has experienced sporadic but significant floods, disrupting normalcy and posing unique challenges to its infrastructure. Among the critical nodes in this bustling metropolis is the Dubai International Airport, a vital hub connecting the world. This article delves into the intersection of Dubai flood events and the resilience demonstrated by the Dubai International Airport in the face of such challenges.

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Orbitshub

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

The microservices honeymoon is over. When starting a new project or revamping a legacy monolith, teams started looking for alternatives to microservices. The Modular Monolith, or 'Modulith', is an architecture that reaps the benefits of (vertical) functional decoupling without the high costs associated with separate deployments. This talk will delve into the advantages and challenges of this progressive architecture, beginning with exploring the concept of a 'module', its internal structure, public API, and inter-module communication patterns. Supported by spring-modulith, the talk provides practical guidance on addressing the main challenges of a Modultith Architecture: finding and guarding module boundaries, data decoupling, and integration module-testing. You should not miss this talk if you are a software architect or tech lead seeking practical, scalable solutions. About the author With two decades of experience, Victor is a Java Champion working as a trainer for top companies in Europe. Five thousands developers in 120 companies attended his workshops, so he gets to debate every week the challenges that various projects struggle with. In return, Victor summarizes key points from these workshops in conference talks and online meetups for the European Software Crafters, the world’s largest developer community around architecture, refactoring, and testing. Discover how Victor can help you on victorrentea.ro : company training catalog, consultancy and YouTube playlists.

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Victor Rentea

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

Understanding the FAA Part 107 License ..

Christopher Logan Kennedy

presentation ICT roal in 21st century education

jfdjdjcjdnsjd

DBX First Quarter 2024 Investor Presentation

Dropbox

Passkeys: Developing APIs to enable passwordless authentication Cody Salas, Sr Developer Advocate | Solutions Architect - Yubico Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

apidays

Discover the innovative features and strategic vision that keep WSO2 an industry leader. Explore the exciting 2024 roadmap of WSO2 API management, showcasing innovations, unified APIM/APK control plane, natural language API interaction, and cloud native agility. Discover how open source solutions, microservices architecture, and cloud native technologies unlock seamless API management in today's dynamic landscapes. Leave with a clear blueprint to revolutionize your API journey and achieve industry success!

WSO2's API Vision: Unifying Control, Empowering Developers

WSO2

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

sammart93

Webinar Recording: https://www.panagenda.com/webinars/why-teams-call-analytics-is-critical-to-your-entire-business Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Why Teams call analytics are critical to your entire business

panagenda

Vector Search -An Introduction in Oracle Database 23ai.pptx

Remote DBA Services

Tracing the root cause of a performance issue requires a lot of patience, experience, and focus. It’s so hard that we sometimes attempt to guess by trying out tentative fixes, but that usually results in frustration, messy code, and a considerable waste of time and money. This talk explains how to correctly zoom in on a performance bottleneck using three levels of profiling: distributed tracing, metrics, and method profiling. After we learn to read the JVM profiler output as a flame graph, we explore a series of bottlenecks typical for backend systems, like connection/thread pool starvation, invisible aspects, blocking code, hot CPU methods, lock contention, and Virtual Thread pinning, and we learn to trace them even if they occur in library code you are not familiar with. Attend this talk and prepare for the performance issues that will eventually hit any successful system. About authorWith two decades of experience, Victor is a Java Champion working as a trainer for top companies in Europe. Five thousands developers in 120 companies attended his workshops, so he gets to debate every week the challenges that various projects struggle with. In return, Victor summarizes key points from these workshops in conference talks and online meetups for the European Software Crafters, the world’s largest developer community around architecture, refactoring, and testing. Discover how Victor can help you on victorrentea.ro : company training catalog, consultancy and YouTube playlists.

Finding Java's Hidden Performance Traps @ DevoxxUK 2024

Victor Rentea

Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows. We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases. This video focuses on the deployment of external web forms using Jotform for Bonterra Impact Management. This solution can be customized to your organization’s needs and deployed to support the common use cases below: - Intake and consent - Assessments - Surveys - Applications - Program registration Interested in deploying web form automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

Jeffrey Haguewood

Corporate and higher education. Two industries that, in the past, have had a clear divide with very little crossover. The difference in goals, learning styles and objectives paved the way for differing learning technologies platforms to evolve. Now, those stark lines are blurring as both sides are discovering they have content that’s relevant to the other. Join Tammy Rutherford as she walks through the pros and cons of corporate and higher ed collaborating. And the challenges of these different technology platforms working together for a brighter future.

Corporate and higher education May webinar.pptx

Rustici Software

Kürzlich hochgeladen (20)

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

AI in Action: Real World Use Cases by Anitaraj

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

AI+A11Y 11MAY2024 HYDERBAD GAAD 2024 - HelloA11Y (11 May 2024)

Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Understanding the FAA Part 107 License ..

presentation ICT roal in 21st century education

DBX First Quarter 2024 Investor Presentation

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

WSO2's API Vision: Unifying Control, Empowering Developers

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Why Teams call analytics are critical to your entire business

Vector Search -An Introduction in Oracle Database 23ai.pptx

Finding Java's Hidden Performance Traps @ DevoxxUK 2024

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

Corporate and higher education May webinar.pptx

Increasing API Adoption via a Code Playground

1. Code S. Adeel Ali | adeel@apimatic.io @APIMatic | @AdeelAli25

2. SaaS API First Mobi le First Web First @APIMatic | @AdeelAli25

3. Software Product @APIMatic | @AdeelAli25

4. Software Product @APIMatic | @AdeelAli25

5. Software Product @APIMatic | @AdeelAli25

6. API Software Product @APIMatic | @AdeelAli25

7. API Software Product @APIMatic | @AdeelAli25

8. API Software Product Developers @APIMatic | @AdeelAli25

9. API SaaS Product Developers @APIMatic | @AdeelAli25

10. @APIMatic | @AdeelAli25

11. Don’t Make Me Code https://medium.com/the-opsee-blog/let-s-talk-about-developer-experience-dx-design- @APIMatic | @AdeelAli25

12. Product/API Adoption @APIMatic | @AdeelAli25 ∝

13. ∝ Achieving the User Goal in the Least Possible • Number of Steps • Time @APIMatic | @AdeelAli25

14. ∝ Getting Started / Ref Docs Sample App Code Authentication Code API Interaction Code API DX = Least Steps & Time to the First Hello World Hello World @APIMatic | @AdeelAli25

15. Checks and Validations Encode Inputs Serialize body Build HTTP request Make HTTP Call Deserialize body Decode to output Handle errors Getting Started Docs Configuration API Call Arguments Authentication ∝ Hello World @APIMatic | @AdeelAli25 API DX = Least Steps & Time to the First Hello World

16. API Call Arguments Encode Inputs Serialize body Build HTTP request Make HTTP Call Deserialize body Decode to output 4 - Static 1 - Static 2 - Interactive 3 - Interactive ∝ Hello World @APIMatic | @AdeelAli25 API DX = Least Steps & Time to the First Hello World

17. API Call Arguments Encode Inputs Serialize body Build HTTP request Make HTTP Call Deserialize body Decode to output 4 – SDKs/Client Libraries 1- Getting Started 2 – Dynamic Code Samples 3 – Assisted Auth ∝ Hello World @APIMatic | @AdeelAli25 API DX = Least Steps & Time to the First Hello World

18. API Call Arguments Encode Inputs Serialize body Build HTTP request Make HTTP Call Deserialize body Decode to output 4 – SDKs/Client Libraries 1- Getting Started 2 – Dynamic Code Samples 3 – Assisted Auth Hello World @APIMatic | @AdeelAli25

19. API Call Arguments Encode Inputs Serialize body Build HTTP request Make HTTP Call Deserialize body Decode to output 4 – SDKs/Client Libraries 1- Getting Started 2 – Dynamic Code Samples 3 – Assisted Auth Hello World Not just a cost saver, but in fact a revenue generator — Andrew Cowell, Head of Innovation, Earthport @APIMatic | @AdeelAli25

20. • Your developers should be using your API like they use any other product • For the best DX, Don’t make them code. • Give them what they need to get started. Let them focus on what they ar @APIMatic | @AdeelAli25

21. @APIMatic | @AdeelAli25

22. DX @APIMatic | @AdeelAli25 Thank You If you talk to a man in a language he understands, that goes to his head. If you talk to him in his language, that goes to his heart

Hinweis der Redaktion

This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA
This Photo by Unknown Author is licensed under CC BY-SA

Increasing API Adoption via a Code Playground

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Mehr von Pronovix

Mehr von Pronovix (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Increasing API Adoption via a Code Playground

Hinweis der Redaktion