Official Unity Support on Native Platforms

Unity as a Library

Unity 2019.3 will add support for using Unity as a library controlled by native Android/Java and iOS/Objective C apps so you can easily insert AR and other Unity features.

https://blogs.unity3d.com/2019/06/17/add-features-powered-by-unity-to-native-mobile-apps/

Android Integration

https://forum.unity.com/threads/integration-unity-as-a-library-in-native-android-app.685240/

iOS Integration

https://forum.unity.com/threads/integration-unity-as-a-library-in-native-ios-app.685219/

Thoughts

Depending on the new official Unity as a Library feature could result in a more stable react-native-unity-view library and should be considered for version 2.x.x

Related Flutter Issue

https://github.com/snowballdigital/flutter-unity-view-widget/issues/10

[zbagley]

@alisherakb @ambewas I have minimal viable up and running for iOS. Minimal viable for Android is definitely on the plate for the near future as well, but iOS has temporary priority. Hoping to continue to expand on the base form, lifecycle management, subclassing, and general project structure down the line. Will likely also make branches to show examples for common packages. Feel free to watch/star/contribute https://github.com/CGS-Canada/react-native-unity

[zbagley]

@alisherakb @ambewas Currently I’m using Native to load in, and working directly with the RCBridge and Unity’s Native Calls protocol. I have it set up to communicate only between button clicks (click to load RN as well), and plan on auto-loading RN as the primary view on both platforms for initialization. General idea is that the native code is acting as the RN/Unity bridge. Once I get a better foundation implemented, I will gladly share a GitHub repo template both here and on the Unity forum links above.