Comment on page
A container is the end product of Electrode Native.
It is a native library, in the form of an AAR library for Android, and a Framework for iOS. It is composed of a single miniapp or a set of miniapps, and includes all of their supporting assets and dependencies (JS and native).
The mobile application will only have to depend/interact with a single container library, as it encapsulates eveything that is needed to launch the miniapps. This is an important point, so let us emphasize it again.
A mobile application will (and can) only depend on a single container. Composition of miniapps and container customization takes place at the container generation level to tailor a container to a specific target mobile application.
Here is a high level diagram, giving a better idea of what's inside a container, along with some additional details.
- Assets Represents all of the images, fonts and other assets that are used by the MiniApps. As in React Native projects, assets are not part of the JS bundle but are instead stored in the native project itself (assets directory for Android, Resources for iOS). Also, as in React Native projects, Electrode Native relies on Metro bundler to generate the target file structure for the assets.
- Native Libraries All of the native libraries that are used by the miniapps. This includes React Native (obviously) along with all its native dependencies, but also the native code of all of the native modules that are being used by the miniapps.
- ERN APIs Represents all of the native code of any generated ERN API, as well as any ERN API standalone native implementation, that are being used by the miniapps.
- ERN Initialization Code Native Code that is exposed to mobile application to integrate a container. Mostly consist of initialization code, along with some utility code to interact with the miniapps.