Is there any plan to support dual usage of these two components? It feels silly to have to build our own UI to mimic as much of the ASK functionality as we can when a clear solution exists. However, it has a seemingly artificial limitation in front of it to prevent its use in our case. Just curious as to know the rationale behind this decision and to help aid in planning where to put development time going forward, as ASK would be great, but this seems like a deal-breaker for its adoption.

Is there any plan to support dual usage of these two components? It feels silly to have to build our own UI to mimic as much of the ASK functionality as we can when a clear solution exists. However, it has a seemingly artificial limitation in front of it to prevent its use in our case. Just curious as to know the rationale behind this decision and to help aid in planning where to put development time going forward, as ASK would be great, but this seems like a deal-breaker for its adoption.

Is there any plan to support the dual usage of these two systems? It would be great to use the built-in first-party support of ASK and not have to build our own UI to mimic as much of the functionality as we can. Just curious as to the rationale behind this limitation, as it feels superfluous.