apidays LIVE Jakarta - What will the next generation of API Portals look like? by Allan Knabe, apiable.io
0 likes260 views
The document discusses the evolution of API portals and their importance in enhancing the developer experience. It highlights the need for APIs to be treated as products with clear value propositions and discusses various options for building future API portals, including off-the-shelf solutions, custom portals, and SaaS-based services. The author emphasizes that understanding user needs and monetization strategies are critical for the success of API products.
apidays LIVE Jakarta - What will the next generation of API Portals look like? by Allan Knabe, apiable.io
- 1. Next generation API Portals... ...what will they look like? Allan Knabe, API Product Manager & Co-founder- apiable.io
- 2. Allan Knabe, API Product Manager & co-founder of https://apiable.io/ BECOME API ABLE API Portals as a Service @apiable_io apiable-io | allanknabe Twenty years of experience working with large organization across a wide range of industries:
- 4. What have we built so far? ● Developer Portals ● Developer Documentation ● Developer Communities ● Examples ● Sandboxes ● Hackathons ● Developer Portals ● Developer Documentation ● Developer Communities ● Examples ● Sandboxes
- 6. Then why don’t the developers come?
- 7. Reasons why developers don’t come: Reason 1: Your DX is terrible. Reason 2: Developers are not interested in your APIs.
- 8. Then who is interested in my APIs?
- 10. “A customer is someone who pays for your product. A user does not.” - Maurya, Ash. Running Lean: Iterate from Plan A to a Plan That Works
- 11. The developer is probably not your target customer.
- 12. Developer vs Business Products Developer Products: Immediate Access Business Products: Agreement must be signed Product Manager Developer Developer Enabled! Just add Developer! Trusted by Developers! ● SMS ● 2FA ● Call Forwarding ● Google Docs ● Live cricket scores ● SMS ● 2FA ● Call Forwarding ● Google Docs ● Live cricket scores ● Call Elevator ● Create new mobile subscription ● Track vehicle location ● Create Bank Account ● Call Elevator ● Create new mobile subscription ● Track vehicle location ● Create Bank Account
- 13. API Portals of Tomorrow.
- 14. Your APIs will be consumable.
- 15. You’ll give a great API experience when: Your APIs are Products They have a clear value proposition They are consumable They are monetizable Understandable by mere mortals Your APIs are Products They have a clear value proposition They are consumable They are monetizable
- 16. How do we present APIs as Products? Developer eXperience Customer eXperience
- 17. Digital Marketplace vs Developer Portal When to use a Digital Marketplace? When to use a Developer Portal? ● When the decision maker is Non-Technical ● When you have API Products ● When you wish to Monetize ● When you want a subscription model ● Technical Decision Maker ● The APIs are really clear ● If you can reach developers ● If your APIs can be found ● When the decision maker is Non-Technical ● Technical Decision Maker ● When you have API Products ● The APIs are really clear ● When you wish to Monetize ● If you can reach developers
- 20. KPI’s will be baked in Prioritise your business goals. Avoid vanity metrics.
- 21. Monetisation We’ll see more cases of Monetisation, led by Business Goals for your API Product.
- 22. How to build the API Portal of the future?
- 23. Off the Shelf - from API Management Vendor Pros Cons All major api vendors include a developer portal of some kind. No integration to underlying API Management needed. Enterprise Architects like homogeneous systems architecture, or “all their eggs in one basket.” Quite often an afterthought / hasn’t been upgraded in years. Can be quite expensive if you need a separate license. Can still require substantial development to bring to production. Ongoing maintenance. All major api vendors include a developer portal of some kind. No integration to underlying API Management needed. Enterprise Architects like homogeneous systems architecture, or “all their eggs in one basket.” Quite often an afterthought / hasn’t been upgraded in years. Can be quite expensive if you need a separate license.
- 24. Custom Portal - from a Software Agency Pros Cons You’ll get exactly what you want.. Your branding/marketing team will love you! Can be extremely expensive. Requires an ongoing support contract so that when the API Management system changes your portal needs to be upgraded. Needs a large project with a team, substantial amount of time needs to be invested. You’ll get exactly what you want.. Your branding/marketing team will love you! Can be extremely expensive. Requires an ongoing support contract so that when the API Management system changes your portal needs to be upgraded.
- 25. SaaS Based - API Portal as a Service Pros Cons Continuous improvements, new features available all the time. Subscription based, no need to invest a lot of CAPEX up-front. Is maintained and run as a Service, no need to worry about API Management upgrades. Multiple API Gateway support. If hosted “off-premise” then users data needs to be secure. Loss of control, someone else is running the system. There are very few API Portals as a Service… Continuous improvements, new features available all the time. Subscription based, no need to invest a lot of CAPEX up-front. Is maintained and run as a Service, no need to worry about API Management upgrades. Multiple API Gateway support. If hosted “off-premise” then users data needs to be secure. Loss of control, someone else is running the system.
- 26. apiable.io Portal as a Service
- 27. Next-gen API Portal Demo available - Prototype API Portal ● Technology agnostic (Apigee, Mulesoft, Kong, Axway, etc) ● Marketplace concept with subscriptions ● Role based (Business, BizDev, Developer) ● Identity Provider integration ● Technology agnostic (Apigee, Mulesoft, Kong, Axway, etc) ● Identity Provider integration ● Role based (Business, BizDev, Developer) Coming June 2021
- 28. Ways to get in touch apiable.io API + ABLE + .io +358 (0)50 564 75 03 allan.knabe@apiable.io +358 (0)50 564 75 03 @apiable_io apiable-io | allanknabe
- 29. Backup
- 30. API as a Product ● Not just for externals! Create “Internal Products” “Using established Product Management tools and techniques to create API Products with a value proposition, thus ensuring their success.” ● The product is a much better vehicle for delivering value, especially when compared to a project. A product endures, a project fades away. ● Speaking to your customers and understanding their pain is a vital step, don’t miss this part out! ● No point in having the best API Portal in the world if you have nothing to put on it. ● No point in having the best API Portal in the world if you have nothing to put on it. ● Not just for externals! Create “Internal Products” ● The product is a much better vehicle for delivering value, especially when compared to a project. A product endures, a project fades away.