My view is simply that native is practically always better - if you have the resources to maintain two codebases. The biggest risk I see is that you're running

My view is simply that native is practically always better - if you have the resources to maintain two codebases. The biggest risk I see is that you're running two separate development teams (Android and iOS) with varying skills. On our last project, the Android code was of much worse quality than the iOS one (perhaps due to both tooling and Java null pointers; which can be attributed to poor development skills), so the projects did not match in terms of quality and sometimes even the way features behaved.