-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance API Tile Information for Marketplace Relevance #2106
Comments
Update I have completed the initial UI design for the new API tiles. Currently, I'm working on the backend implementation for the REST API modification. |
Test for performance impact if any after the implementation is completed |
Update I have completed the UI enhancements for the new API tiles and the corresponding REST API modifications to the publisher portal. Currently, I'm working on the task of making it to be configurable. After completing this implementation, will add this to the dev portal. |
Update Completed the configuring part by integrating it into the settings API, as discussed during the last sync-up. With this implementation, users are able to configure the business properties that need to be visible in the API tile through a global config. Remaining Tasks Adding this implementation to the dev portal. |
Hi all, The design document for the feature can be found here[1]. [1] https://docs.google.com/document/d/187z3HkyDiByosUA55COzGBP4WX_prgnTDRgobPsSgqM/edit?usp=sharing |
Hi all, The performance test results for the feature can be found here[1]. [1] https://docs.google.com/spreadsheets/d/1koUsHVeNbaXYBN-S-Uk5pnqB_pEGUK9HzCsYa7eQoj0/edit#gid=0 |
Update We conducted a feature code review last week, and during the review, some suggested changes were discussed. I am currently working on implementing the suggested changes. Additional Facts Based on the performance test results, it is recommended to proceed with the UI approach, as the backend approach results in longer response times. While adding the feature for API products, it was noticed that monetization is not functioning correctly for API products. Please find the relevant Git issue[1]. In the email thread, there were requests to include additional details with this feature. The requests are as follows:
[1] #2176 |
Update Opened the carbon-apimgt PR[1] & apim-apps PR[2] to this feature. Feature details are added in the PRs with screenshots. Please note that we haven't introduced a new configuration for the 'display' property of external APIs, as this label is already displayed in the API tile of the publisher portal when an API is marked as a Third-Party API. Therefore, we have added the same behaviour to the dev portal as well. Below are screenshots of the new API tile for reference. Publisher Portal Dev Portal Here we have added a popover to display the email of the business owner & technical owner. But we are not going to add more details here by taking the performance impact into consideration. With Popover |
Hi all, Please find the Doc PR[1] for this feature. Thanks! |
Hi all, Closing this since feature changes and document changes have been completed. Please find the attached PRs [1], [2], [3] & [4]. [1] wso2/carbon-apimgt#12161 Thanks! |
Problem
The current state of the API tile information lacks crucial business details necessary from a marketplace perspective. In order to improve the user experience and facilitate decision-making, it's essential that the API tile information provides relevant business insights.
Solution
To improve the API tile information's relevance to the marketplace point of view, the APIInfo structure should be extended to accommodate optional properties like business information and external APIs. This extension will allow API providers to supply the essential business context and references to related APIs, making the tile information more informative and valuable to potential users.
Affected Component
APIM
Version
No response
Implementation
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: