Hi,
If we build a plugin with some native code components for iOS & Android does it require us to either have self-hosting ($1k per year) or to put the plugin in the marketplace in order to use it inside an iOS app?
Thanks,
Nathan.
No, but you will have to build your entire project with corona native if it contains a native plugin. See the app template in the corona native folder, it contains both the native plugin code and the Corona project folder.
To build it from the simulator, one of the options you mention is required.
The primary purpose for the self-hosted plugins is so that you can build your own native plugins and use them in your own simulator builds. This was designed for larger studios which is why it was part of the former Enterprise Professional package where studio with multiple developers could host their own plugins instead of paying for multiple Enterprise licenses.
For developers wanting to make marketplace plugins, this is a helpful tool, but by no means required. It lets you build and test your plugin before you submit it. But you can certainly build an test your plugin using Xcode/Android Studio to a point where you’re comfortable to submit it, and then once you do, we will host it and you will have access to the repository where you can make a change, push it to our servers, wait a bit for it to propagate out and test against what will eventually be the live version.
Rob
Thanks @RobMiracle but what if we just want to use a plugin for our own product in production (not on the marketplace, not on simulator) - can we do this without self-hosting?
When I say “simulator”, I’m specifically meaning simulator builds. Most plugins are going to use SDK’s that won’t work in the simulator anyway. This is about the building phase.
If your team is comfortable building with Xcode/Android Studio you wouldn’t benefit from self-hosted plugins, but, if you want your team to use the simulator and do device builds there, then you would benefit from self-hosted plugins. That way, only your “native” expert would need to build the plugin, host it on your server and everyone else could just use the simulator to build.
Depending on your team size, it may not be worth it if everyone is okay doing native builds.
Rob
OK thx
No, but you will have to build your entire project with corona native if it contains a native plugin. See the app template in the corona native folder, it contains both the native plugin code and the Corona project folder.
To build it from the simulator, one of the options you mention is required.
The primary purpose for the self-hosted plugins is so that you can build your own native plugins and use them in your own simulator builds. This was designed for larger studios which is why it was part of the former Enterprise Professional package where studio with multiple developers could host their own plugins instead of paying for multiple Enterprise licenses.
For developers wanting to make marketplace plugins, this is a helpful tool, but by no means required. It lets you build and test your plugin before you submit it. But you can certainly build an test your plugin using Xcode/Android Studio to a point where you’re comfortable to submit it, and then once you do, we will host it and you will have access to the repository where you can make a change, push it to our servers, wait a bit for it to propagate out and test against what will eventually be the live version.
Rob
Thanks @RobMiracle but what if we just want to use a plugin for our own product in production (not on the marketplace, not on simulator) - can we do this without self-hosting?
When I say “simulator”, I’m specifically meaning simulator builds. Most plugins are going to use SDK’s that won’t work in the simulator anyway. This is about the building phase.
If your team is comfortable building with Xcode/Android Studio you wouldn’t benefit from self-hosted plugins, but, if you want your team to use the simulator and do device builds there, then you would benefit from self-hosted plugins. That way, only your “native” expert would need to build the plugin, host it on your server and everyone else could just use the simulator to build.
Depending on your team size, it may not be worth it if everyone is okay doing native builds.
Rob
OK thx