Xamarin for Cordova – a bizarre idea?

• It is possible to use Xamarin and Cordova together to get the best of both worlds.

• However, the tooling for this needs to be created on a per-project basis since there is no general solution available at this time.

The main task set by the Cross-Platform .NET topic at the annual Zühlke Germany camp in Barcelona was how to combine Cordova and Xamarin to use them together. At first, this idea seems to be a bit crazy because both frameworks are trying to solve the same problem.

The main task set by the Cross-Platform .NET topic at the annual Zühlke Germany camp in Barcelona was how to combine Cordova and Xamarin to use them together. At first, this idea seems to be a bit crazy because both frameworks are trying to solve the same problem. <p>Xamarin as well as Cordova are cross-platform frameworks which were created to simplify the development of multi-platform mobile apps. Both with fundamentally different approaches but the same result: a native app bundle.&nbsp;</p>

While Xamarin offers the ability to write apps completely using the C# (or F#) programming language, Cordova is more of a native wrapper for web apps. If you want to learn more about both approaches, you can follow these links: Xamarin | Cordova.
But we identified use cases where there can be a real benefit to combining the two technologies. For example, if a customer wants to integrate his existing C# business logic into an existing Cordova app. One option would be the rewriting of all exisiting code in the common language. That would be mean investing substantial effort. A combination of Xamarin and Cordova could solve this problem really well.

Additional use cases could be:

• Cordova projects, which need a lot of plugin code benefit directly from the possibility to write the code in C#, because the plugins can be reused over the different platforms.
• Existing Xamarin plugins like Xamarin.Essentials can be reused in Cordova projects. Xamarin plugins are typically maintained better than Cordova plugins.
• Easy porting of existing web apps with C# backends to mobile.
• Using the possibilities of the entire .NET framework in a Cordova app.

That means?

Cordova provides two main features for app development:

• A native web view, that presents the included web app to the user.
• It allows the access and usage of native code snippets (e.g. Objective-C for iOS and Java for Android). These so-called Cordova plugins are used to access native platform features from the web app code. This allows accessing platform functionality that would normally not be accessible using web technology only. An example would be the fingerprint scanner plugin.

Some advantages of a combined solution of Xamarin and Cordova are:

• Existing Cordova apps can be executed as usual.
• Plugins can be written in C# (or F# and even Visual Basic .NET).
• Existing C# code can be used together with the Cordova app.

Our approach

There are two approaches which can be used to accomplish the goal:

• Including the existing Cordova library for iOS and Android through bindings into the platform-specific Xamarin projects.
• Creating an own web view in Xamarin (maybe even with Xamarin.Forms) and "reimplementing" the Cordova functionality.

We chose the first attempt, because it is possible to reuse existing Cordova plugins this way. If you're interested in the other approach, you can read about it in Shawn Anderson's blog.
 

Update the MainActivity.cs to the following code snippet, so the Cordova view gets executed on app start.

After Cordova has been installed, the command:

Zühlke Engineering AG
1    cordova create hello com.example.hello HelloWorld

creates an example app. The command creates a raw Cordova app, which is missing the according platforms. Add your desired platform with the following commands:

Zühlke Engineering AG
1    cordova platform add android --save
Zühlke Engineering AG
1    cordova platform add ios --save

Copy the assets folder into the Xamarin project. This folder contains the whole web app (e.g. *.html and *.js files).

Zühlke Engineering AG
1    HelloWorld/platforms/android/assets

After importing the assets folder, change the BuildAction to AndroidAsset. This is the correct way to tell Xamarin how to handle imported files.
 

Now it should be possible to build and run the project. The Cordova logo should be visible on the smartphone also.

Xamarin.Android Plugins

Plugins are used to communicate between C# code and the Cordova logic. With the plugin concept you could simply use any of your C# business logic inside of a Cordova app. If you want to access native features like the camera or file system, plugins are useful, too. The next steps will show you how to implement a simple Xamarin.Android Plugin.

Create a new class inside the Xamarin.Android project and inherit from CordovaPlugin.

The Execute method can be invoked from the Cordova code afterwards.

Create a new file called testplugin.js in the folder Assets/www. This file is the Cordova equivalent to the previously created C# class and manages the communication from the Cordova side.

The plugin can be used with the following sample code snippet:

The plugin is dedicated to transport the string Good Evening to the Xamarin code. The Xamarin code attaches from Xamarin to the string and returns the result. Afterwards the Cordova app shows an alert window with the respective result.

Cordova for Xamarin.iOS

Cordova iOS Binding

The iOS project needs a Cordova binding as well. To achieve that, the original iOS Cordova library is needed. Clone that library from the source https://github.com/apache/cordova-ios. To make things work with Xamarin.iOS we need to accomplish a tiny customization here. So open the file CDVCommandQueue.m and find the following line if (!([obj isKindOfClass:[CDVPlugin class]])) {. Change the code to:

After changing the code, a static library (which is needed for the binding project) can be built. Xamarin's documentation explains pretty well how to do that. Finally use the following makefile to create a fat binary:

Then, the binding project can be built. To make the binding work, we need the ApiDefinition.cs and Struct.cs. Both files were modified by us to fit the requirements.

Xamarin.iOS project

Like with the Android project, an iOS project is needed as well. So create a new Xamarin.iOS project and reference the previously built binding library. The steps are almost equivalent to the Android project.

In preparation, we already built a Cordova iOS app. Like before, we need the assets folder in our Xamarin.iOS project. This folder contains the web app inside the Xamarin project. The steps are just like in the Android project.

After the assets folder is copied into our project and the binding library is referenced, the class ViewController.cs needs some logic to run the Cordova app. So change the ViewDidLoad method as seen here:

If we run the project now, we should see the Cordova initial screen on the iOS device.

Xamarin.iOS plugin

To create a plugin, a respective class is needed inside the Xamarin.iOS project. This class needs to inherit from CDVPlugin, so Cordova can recognize it as a plugin. You can view our sample plugin below:

This plugin will simply transport the Hello string, but it's sufficient as a proof of concept.

To register the plugin, add the following lines to your ViewDidLoad() method, inside the ViewController.cs class. Just after the line: _cdv.StartPage = "index.html";.

Conclusion

The main finding: It's definitely possible to use Xamarin and Cordova together. Although the integration is not very intuitive (we didn't expect it to be, either), the integration seems to be not very clean and a lot of manual adjustments are needed. Significant effort is still needed to make cordova platform add xamarin-android and cordova platform add xamarin-ios work out of the box. If you stick to the steps we showed you above you will likely still have to invest a lot of effort for each platform update. This should defintely be considered before planning a real world project.

But against all the odds, the combination of both technologies is possible and works pretty well in the end. Whether it is a good choice for your project depends on a lot of factors, including your team know-how, the platforms you are trying to support, any legacy code you might have, and other factors.
Please feel free to contact us if you have any questions!