Over the last year there have been a number of requests from developers for information regarding Xamarin technology in relation to the ArcGIS Runtime.
Xamarin is attractive to many of our developers because it allows them to leverage their existing Microsoft .NET development skills when building Android, iOS, Mac, Windows and Windows Phone apps.
What is Xamarin?
Xamarin is an evolution of the Mono project, which is a cross platform open source .NET development framework.
When Microsoft created the .NET technology they did two things; they defined a specification and then implemented that specification for the Windows Operating System. The specification they defined and subsequently published was in fact composed of several specifications. Microsoft implemented these and released them to the world as the Microsoft .NET Framework. Microsoft, Intel and Hewlett Packard then worked to standardize the specifications. This was achieved in 2003.
The situation with User Interface components is more complex. Xamarin Forms, released in May 2014, is a technology similar to Microsoft’s XAML to allow developers to capture a form layout within a visual designer. Xamarin will bind these UI components of the layout to native UI widgets appropriate for the platform the UI is executing on. Since the various platforms that Xamarin supports have very different UI capabilities, only a subset of UI controls are supported by Xamarin Forms. Xamarin Forms can coexist with native UI controls which are also accessible through Xamarin, although when using the native controls the UI code is not portable between platforms.
3rd party components that extend the capabilities of the operating system, for example the ArcGIS Runtime, can expose their capabilities to Xamarin by creating Xamarin bindings. These bindings allow the Xamarin runtime to be extended so that developers can work with the capabilities of the 3rd party library using C# as if they were coding against the 3rd party library using the native language.
Using Xamarin binding technology it is possible (through the effort of generating the bindings) to access 3rd party libraries and OS APIs not exposed by default through Xamarin. While possible it does mean that any code written will not be portable to other platforms.
ArcGIS Runtime and Xamarin in Practice
In order to expose the capabilities of the ArcGIS Runtime to the Xamarin developer Xamarin bindings would need to be created. These Xamarin bindings must be created for each platform by binding onto the appropriate ArcGIS Runtime API for the respective platform. The diagram below illustrates this architecture.
While this architecture allows Xamarin developers to access the ArcGIS Runtime, it does not present the developer with a way to easily write cross platform code since the differences in the ArcGIS Runtime APIs are exposed directly to the developer. The developer must learn the specific ArcGIS Runtime API and then with that knowledge they can code against that API using C#.
We have prototyped a set of Xamarin bindings to confirm that the theory actually works. The results of these tests are that this architecture does work. However, we also learned that the creation of these bindings is a non-trivial task. In addition, since the bindings map very closely to the underlying API, as the API evolves the bindings must be maintained, which is a process that can result in a brittle API.
Current ArcGIS Runtime and Xamarin Status
At this point, we have no plans to release Xamarin bindings for our native APIs. There are a number of factors that have gone into this decision.
- Sub-standard developer experience when coding against more than one ArcGIS Runtime API due their differences
- Does not easily support cross platform code development, due to the binding requirements
- Xamarin technology evolving rapidly
ArcGIS Runtime Cross Platform Development
We do support cross platform development with the ArcGIS Runtime. Currently the JavaSE and Qt APIs support cross platform development, but only for Windows and Linux desktop systems. The Qt API is currently being extended to support QML.
The Qt QML API will support cross platform development for all the runtime platforms. Code written against the Qt QML API must still be compiled targeting the native platform, but code written for one platform just works when compiled for a second platform. There are no differences in the Qt QML API between platforms, making cross platform App development with a single code-base possible.
To achieve this there are some compromises, for example, the UI controls available must exist on all platforms, meaning specific UI components that only exist on one platform cannot be used when building cross platform code. However, for a large percentage of use cases the Qt QML API will be a good choice.
So while we do offer cross platform development options with the ArcGIS Runtime today, we would like to hear from you regarding you development needs with respect to Xamarin. If Xamarin was provided as an option, would you use it? How are you managing your cross platform development needs currently? Do you use Xamarin today, and if so, how?
CTO, ArcGIS Runtime & APIs
The ArcGIS Runtime SDK for .NET 10.2.3 beta is now available on the Esri Beta Community. This is a quality release that resolves some issues encountered in the previous beta. A number of enhancements have also been included with the product:
On Friday April 18th, we updated the Operations Dashboard for ArcGIS app that is hosted within ArcGIS Online. We are busy working on updating the Portal for ArcGIS configuration utility as well so please look for this update inside of the Customer Care site later this week.
In March we rolled out quite a few updates to Esri products and the Operations Dashboard for ArcGIS was no exception. A lot of exciting new features were added and you can find a full list of updates on our doc site or a preview of them from this blog article.
Perhaps the most sought after request that we added this release is to extend the reach of Dashboard beyond Windows Desktops and laptops and add support for tablets (iPads and Android tablets) so that more people within the organization can use it. With the 10.2.2 release, we have done just that by building Dashboard into the browser so it can run across platforms.
This blog article will describe how you can author operation views that target the browser and highlight capabilities within the browser app itself. Continue reading
At the //build/ conference in San Francisco today, Microsoft announced a new development platform for Windows Phone that unifies the developer experience between Windows Store and Windows Phone. This greatly enhances the code-sharing story we presented at Esri Developer Summit … Continue reading
We are pleased to announce the 10.2.2 release of ArcGIS Runtime SDK for WPF. You can download the SDK today from ArcGIS for Developers. This release follows the 10.2 release in Q4 2013 and includes several new features plus performance and quality improvements. Here are some of the highlights (much more information can be found in the release notes):
We are excited to announce the 10.2.2 beta release of the ArcGIS Runtime SDK for .NET! This SDK enables developers to build rich, high performance GIS applications for Windows PCs, tablets, and phones. It includes three APIs that support building .NET apps for Windows Desktop, Windows Store, and Windows Phone. The APIs share a common design and structure, which encourages sharing implementation logic across Windows platforms. Continue reading
The new ArcGIS Runtime SDKs for 10.2 are almost here! And they’re full of new capabilities to help you stay productive when building and deploying your apps. Plus, with this release, the much-anticipated offline API will be available in beta! … Continue reading
When Microsoft announced Silverlight at the MIX conference in 2008, we quickly started to look at what this amazing new technology could do to enable .NET developers to build great web applications for ArcGIS Server. Since both Silverlight and WPF were based on .NET and XAML, we were able to quickly port our Silverlight implementation to the WPF platform. The SDK grew popular very quickly – we even won several awards. When the new Windows Phone platform was announced in 2010, we had a prototype running on a phone within the hour of launch. The parity between the platforms was amazing such that nearly 99% of the source code was shared across the three APIs. This provided a consistent experience for .NET developers building ArcGIS Server clients across all three platforms.