Open vfridkin opened 1 month ago
I'm glad you find Deneb valuable enough to consider it in other MS Products. Power BI visuals are... very special cases and it would not be easy to port this elsewhere without significant work (or which I definitely do not have the capacity for 😅). I also don't know much about PowerApps extension development so this would represent considerable upskilling for me to develop and support.
However, v2 design will separate the Editor component from the Power BI visual platform and make the Power BI parts injectable dependencies, therefore opening up the editor component and template system for use elsewhere. We will have the concept of a Power BI visual client, and a simple web client. If someone were to want to integrate this as a PowerApps component, they would be able to contribute the necessary changes to the core components and R&D a PowerApps client or write their own and theoretically use the Deneb core as NPM packages in their work.
As per notes on other issues, the v2 planning and architecture is a huge undertaking for one person (me) to fit into their spare time and do for free, so I don't have a solid ETA for when this could be available. I'll keep this open for now but mark it as a "Blue Sky" feature, as it would be a fair way down the lane in terms of where Deneb is currently going (but not completely impossible with the right kind of time and effort investment).
Power apps has a very limited visualisation capability. Could Deneb be made into a code component for power apps so we have input and display in a single platform? I'm guessing I could use deneb in power bi imported into power apps but besides how messy this seems, I'm also feeling the performance would be terrible.