There are certain API’s that are available in ‘App home (iframe)’, but not in ‘App home (ui extension)’ or ‘Admin’.
For example:
I can definitely understand that some of these wouldn’t make much sense in certain admin UI extensions. I can also think of numerous places where it would be extremely useful!
What are the odds of getting (perhaps a slimmed down) version of app bridge APIs in admin ui extensions?
Hey @bkspace, hope all’s well! Thanks for flagging too - I get the gap here. Admin UI extension APIs are currently target-specific, and I can’t confirm anything roadmap-wise around broader App Bridge parity.
Just to clarify:
Just want to make sure I’m capturing use case correctly as always so I can dig into this on our end for you.
I think there are some that are more obvious than others. One use case, might be an app theme extension, or checkout extension is required for a function-settings (e.g checkout validation).
What we do today in Discount Kit, is request a review with the review API, after completing a successful action - so I imagine similarly, after saving a checkout rule, you might want to request a review.
The same goes for optional scopes. To keep my access tokens lean, I might only request a scope when you’re actually creating that resource - that could even be for things like a product page action/block.
These can all be circumvented by navigating to an app bridge hosted page, but I think it’s a bit of a shame you don’t get these nice things in extensions!
Thanks @bkspace.
Admin UI extensions can query currently granted scopes through the Admin API, but they can’t launch the optional-scope consent flow, so I think this is a fair thing to highlight on your end for sure.
The App Home handoff works, but I definitely get why that isn’t equivalent after saving function settings or completing an action in context. I’ve got enough here to pass along the feature request, I can’t confirm roadmap or timing, but I’ll pass these examples along as product feedback. Thanks again!