Migrating apps and adapters to MobileFirst Foundation 8.0
- Gone are MobileFirst projects you would create in MobileFirst Studio
- Gone are Hybrid apps you would create in those MobileFirst projects
- Gone is generating an SDK for native apps using MobileFirst Studio or MobileFirst CLI
- Gone is deployment of .war and .wlapp files to the MobileFirst Server
But not all is gone! there is plenty of new and improved:
- Registering apps (think “deploying”, but don’t use that word anymore for apps…) is now simplified and done directly from the MobileFirst Operations Console (or using the MobileFirst CLI)
- You now have full and unrestricted access to the Cordova ecosystem with the introduction of support for standard Cordova apps, made possible thanks to the introducion of the MobileFirst Cordova SDK (in other words, a set of Cordova plug-ins providing the MobileFirst feature set)
- You can use CocoaPods, Gradle and NuGet to add the MobileFirst Native SDKs into native apps (no more copy & paste and manual configuration)
- Adapters are now based on Apache Maven, giving you a standard developmnt path, easing dependency inclusion and management
- Security configuration no longer requires deployment of a .war file, instead you do this straight in the MobileFirst Operation Console
- And lots and lots more
It’s a lot of things and to help you migrate your existing applications and adapters to their new form, we’ve written a cookbook.
The intention of the cookbook is to provide you with a clear and simple view of the migration steps you’ll need to take.
There is also a fair amount of API changes, so in addition to the cookbook to there is also a Migration Assistance tool that will:
- Scan your projects and provide you with an API report detailing potentials actions you should take.
- For Hybrid apps the tool will also generate a Cordova project with all the metadata of the existing app, install the SDK for you and so on
You can read more about the Migration Assistance tool and find the migration steps you need to take, in the Migration Cookbook.
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.