| This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal. |
Expected output is an component packaged .aar for android and either a static or embedded framework for iOS that can be used from other native applications
This is an interesting ask, and we normally get questions on how to import native functionality from a native SDK into Visualizer rather than from Visualizer to a native SDK. I would submit this as a feature request, but Visualizer is built to create a natively rendered app within our framework and uses a VM to render the UX as well as talk to the device layer that encapsulates the entire app framework. When an app is started, the VM interprets the UX and Javascript and renders the UX using the native OS's drawing functions to give a true native user experience. The JavaScript business logic is interpreted by the VM. The key here is that the entire app is rendered by the VM making it difficult to virtualize a component using this method. Although the Kony Visualizer team may come up with a future approach to your request, it's not supported today. When developers use Kony, they are looking to create an app that spans across channels rather than create a specific exportable component.