Use React Native to create an iOS framework and Android library from the public code library (instead of app)

Does anyone use react native to create iOS and Android applications that can be used as libraries/sub-projects in other iOS and Android native projects? Created in the case of this machine? My goal is to create new features for an existing application that has an iOS and Android code base that was developed without native reaction.

Just give one Simple example, let me need to create a series of screens and logical images to allow users to “create a new account”. Ideally, I want to use react native to create new functions (controllers, views, api-client, etc.), Then export it as self-contained iOS and Android apps. In addition to being able to run these apps by myself, I also want to be able to include them as sub-projects in other native iOS/Android projects. Then, native iOS projects A new storyboard/ViewController/segue will be created, and the main view of the react native iOS App will be linked to it.

I know that on iOS/xcode I can drag and drop .xcodepro to another Add sub-projects to sub-projects. If I use .xcodepro created with react native to do this, how would I link the top-level view to an existing non-reactive native iOS project? Is there a similar process on the Android side to achieve the same function?

I also want to explore React Native. We have similar needs as you – developed for iOS and Android Universal library/framework. Our solution is to write the library in C language and use it in XCode on iOS and JNI (Java Native Interface) converter on Android. JNI is a pain because not everything is converted to 1 to 1. I did research using Ruby/RubyMotion, but there is also a JNI conversion step. There are other languages ​​that do not require JNI conversion-but from the last time I read these, these are also experimental. Trying all of them will require effort and The result is not guaranteed. Assuming that in addition to shared libraries, you still want to use Native for the rest of the application (UI, etc.), this will require developers to use Swift, React, and Java (which can become expensive). The most meaningful The way is to use Swift as the iOS framework, Kotlin as the Android library and use the same style (functional/react-swift/react-java style code) so that although the libraries are still different, they are coded in the same style, so Development/maintenance work of one person can be quickly copied/applied to another.

Is anyone using react native to create iOS and Android apps that can be used as other iOS and Libraries/sub-projects in the Android native project. Are these projects created without native? My goal is to create new features for an existing application that has an iOS and Android code base that was developed without native reaction.

Just give one Simple example, let me need to create a series of screens and logical images to allow users to “create a new account”. Ideally, I want to use react native to create new functions (controllers, views, api-client, etc.), Then export it as self-contained iOS and Android apps. In addition to being able to run these apps by myself, I also want to be able to include them as sub-projects in other native iOS/Android projects. Then, native iOS projects A new storyboard/ViewController/segue will be created, and the main view of the react native iOS App will be linked to it.

I know that on iOS/xcode I can drag and drop .xcodepro to another Add sub-projects to sub-projects. If I use .xcodepro created with react native to do this, how would I link the top-level view to an existing non-reactive native iOS project? Is there a similar process on the Android side to achieve the same function?

I also want to explore React Native. We have similar needs as you-develop common libraries/frameworks for iOS and Android. Our solution is to use C Language writing library and use it in XCode on iOS and JNI (Java Native Interface) converter on Android. JNI is a pain because not everything is converted to 1 to 1. I did research using Ruby/RubyMotion , But there is also a JNI conversion step. There are other languages ​​that don’t require JNI conversion-but from the last time I read these, these are also experimental. Trying all of them will require effort and the results are not guaranteed. Assuming that apart from shared libraries, you Still want to use Native for the rest of the application (UI, etc.), which will require developers to use Swift, React and Java (which can become expensive). The most meaningful way is to use Swift as the iOS framework and Kotlin as Android library and use the same style (functional/react-swift/react-java style code) so that although the libraries are still different, they are coded in the same style, so development/maintenance work by one person can be quickly copied/applied To another one.

Leave a Comment

Your email address will not be published.