The main aim of this guide is helping you in the process of migrating your application from the old CocoonJS cloud to the new Cocoon cloud. Hope it helps, if you have any question, please let us know in the forums.
The old CocoonJS cloud and the new Cocoon cloud have a lot of differences (why to bother otherwise?) but probably the main one is that the new Cocoon cloud is completely Cordova based. This means that all the application framework behind the scenes and all the plugins that you can use are pure Cordova. This has some advantages that we think are really interesting for you compared to the old CocoonJS cloud.
We have automated the project migration so you can find your old CocoonJS projects almost ready to work in the new Cocoon but you still need to do some small changes for it to work in the new Cocoon. We could divide the old CocoonJS project in two categories, projects with and projects without extensions. If your project didn’t have any extension (you weren’t premium in the old CocoonJS cloud), you can read the project migration guide to set it up for the new Cocoon. If you have CocoonJS extensions, please read the plugins migration guide below to know the steps to follow to set the plugins up.
Let’s take a look at the some migration questions that you are probably interested in.
We have migrated your accounts in the old CocoonJS cloud to the new Cocoon cloud. You can login to the new Cocoon cloud just using the same username and password that you were using before.
We have migrated all your projects from the old CocoonJS cloud. When you login in your new Cocoon cloud if you had projects other than the welcome project you will see that they have been migrated and are available int he projects dashboard. Before start building the project, please read the project migration guide just in case you need to perform some of the needed changes. To start compiling a project just drop your zip file in the dropping area and the click in the “compiler” button to start building it.
One of the changes related to old CocoonJS extensions in the new Cocoon cloud is the name, now we call them “plugins” instead of “extensions” as it’s how it’s called in Cordova. The other and most importante is that in the new Cocoon you don’t need any special plan or being premium to be able to use plugins, you can use any plugin you want with the free plan.
In the old CocoonJS cloud we had developed several extensions, the most used ones, but there always were people asking for more plugins that we hadn’t developed yet. In the new Cocoon you can take advantage of all the plugins made for Cordova and there are many and you can easily install them using the Cocoon plugins interface.
We also have developed our own Cocoon “certified” plugins that are up to date and well maintained and fixed by us. Now when you want to the plugin installation interface, you will find a search engine for finding any Cordova plugin available and also a Cocoon category where you can find all the Cocoon “certified” plugins. We have made plugins for all the extensions we had in the old cloud so you should be able to migrate all those plugins to the new cloud without issues.
If your project in the old CocoonJS cloud had extensions, the corresponding plugins in the new cloud will be added and configured during the projects migration but in some cases you might need to make some changes in your code as the plugin interface may be not exactly the same.
You can check the plugins migration guides for information and examples about how to migrate each of your plugins to the new Cocoon.
InApp Purchases Plugins
- AdMob (Android & iOS)
- MoPub (Android & iOS)
- Chartboost (android & iOS)
In the new Cocoon we support the same webview engines as in the old CocoonJS cloud (Canvas+, Webview+ and the System Webview) so your project should work exactly the same. The main improvement in that all of them have been updated with respect to the old CocoonJS cloud so you should notice some performance and stability improvements. When your project is migrated, the webview engine that was selected in you last compilation will be set in the new Cocoon cloud. You can always change it using the project general settings.
Also now you can compile for armv7 and x86 architectures in both the Webview+, Webview and Canvas+.
Here you can see where the webview engine selection option was in the old CocoonJS cloud Vs the new Cocoon cloud.
In the old CocoonJS cloud we supported several platforms, after some years we have realised that 95% of the compilations were for the big two: Android (this includes Amazon and OUYA) and iOS. So for the new Cocoon cloud we have removed several platforms to only leave these. If you were developing for Amazon or OUYA, you will notice that there is not an OUYA or Amazon compilation platform, don’t worry, in the Cordova world almost everything is solved with plugins, so you only need to add the right plugins to be able to publish for those platforms, the Amazon AppStore plugin (which is available as a Cocoon plugin) and the OUYA SDK plugin which is a Cordova community plugin.
Another important difference between the platform configuration is that in the old CocoonJS cloud, you have to select every platform you wanted to compile for at the moment of compiling. In the new Cocoon cloud, you can enable/disable platforms and you will compile for those only every time you compile.
In the old CocoonJS cloud we have a very useful tool that you could use to test your developments, it was called the CocoonJS Launcher. We have an almost identical tool in the new Cocoon cloud but here we call it the Cocoon Developer App (or just DevApp). The tool is basically the same but in the new Cocoon cloud you can build it on demand and it will have the same exact configuration (bundle Id, name, icon, splash, etc) and plugins that you have configured for your app. This is an important difference, in the old CocoonJS cloud the Launcher wasn’t exactly the same application, it didn’t bundle your icons or the splashes and although it was really useful, internally the application didn’t behave exactly the same as the final app and you might encounter some differences with the final build. In the new Cocoon cloud both applications are identical so that makes your testing more reliable and time saving.
Once you have created a project, you can compile a developer app using the “compiler” button in the “Developer App” section.
The build process is quite similar between both clouds. The main difference int he new Cocoon cloud is that you don’t get an XCode project for iOS, now you always get a final binary, an IPA for iOS and an APK for Android. Another important improvement is that now you can sign your binaries so you don’t have to do it locally and just get the binaries ready to upload to the stores. You can sign your binaries uploading your keys in the “Signing keys” section and selecting them. The next compilation with sign the binaries automatically.
Well this is probably the most important things you need to know when starting a migration. You can always read the plugins and project migration guides for more information regarding the migration process.
Thanks for using Cocoon!