Great input, thanks! As you said, with a cross-platform UI solution, there will always be platform/OEM/device specific issues that need special care. We can solve a lot of these on our end. There will obviously be cases we can't anticipate. The take away for me here is, that it should be possible for developers to easily special case in such a scenario. E.g. use the cross-platform API for 80% of the app, mix it with native APIs where necessary.
As for our target. Atm Android developers who want to expand to iOS more easily as well as Android/iOS devs who already do both platforms but want to unify their tooling and share code across platforms are our target. In terms of type of apps, we want to cover all the bases. Game Dev is already covered (via libGDX) with great success. Retailers are also covered, they can use the native APIs on each platform to get 100% native UX, while sharing business logic between platforms. Governmental and enterprise is what we currently are working on and at which my initial questions are aimed. Thanks for the input, really appreciated! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
