Modules iOS & android vs Cross-Platform Native Modules (C++) #270
-
|
In the documentation under Modules there are three sections I have a question regarding the difference between the following Modules: To me it looks like both are using natively coding it c++ with the module file structure. The only difference I see is that One require you to edit the Delegate file for iOS. And the new architecture has a switch app delegate file that you have to change to objective c. Can you please explain what's the difference and when we should use one over the other. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The core difference is wether you want to have a pure C++ Native Module, so that all the logic is stored in C++, or not. The "Android & iOS" Modules, have the implementation written in the platform layer. So for example if you need to access Android specific APIs, you'll go that way. If instead you're working on say a crypto library, you can go the C++ way, as you'll have a single implementation to maintain. |
Beta Was this translation helpful? Give feedback.
The core difference is wether you want to have a pure C++ Native Module, so that all the logic is stored in C++, or not.
The "Android & iOS" Modules, have the implementation written in the platform layer.
So for example if you need to access Android specific APIs, you'll go that way. If instead you're working on say a crypto library, you can go the C++ way, as you'll have a single implementation to maintain.