Two concurrent and supported versions of ArcGIS Runtime SDK are now available: 100.x and 10.2.x. You may have heard version 100.x referred to informally as "the Quartz release". It’s essential to understand the differences between 100.x and 10.2.x so that you can effectively decide which one is right for you.

Version 100.2 is the latest release of a new and modern generation of ArcGIS Runtime, which provides you (developers) with a set of brand new capabilities not in version 10.2.x. While not every 10.2.x capability is in 100.2 yet, over time you’ll find these gaps addressed through a series of updates.

So, if you’re starting to build a new ArcGIS Runtime app or you have an existing app you’ve never added ArcGIS Runtime capabilities to, use version 100.x if you don’t require any of the capabilities found in version 10.2.x. You can use the table below to see which main capabilities are supported in latest release of 10.2.x and 100.x.

If you’re planning on extending an app with ArcGIS Runtime 10.2.x capabilities in it, consider using ArcGIS Runtime version 100.x, if all the capabilities you need are in version 100.x.

If you need one or more of the 10.2.x capabilities, sit tight and stay with 10.2.x. Support for 10.2.x has been extended, affording you enough time to plan your migration to 100.x. Please see the Developer section of the Product Life Cycle page for more detailed support information. By the time 10.2.x has reached retirement, the main 10.2.x capabilities should be available in 100.x.

Now that 100.x has been released for commercial use, no new development will occur for 10.2.x. As mentioned, 10.2.x will continue to be supported. However, be aware that any new ArcGIS Runtime innovation, functionality and/or enhancements going forward will be implemented in the 100.x version only. There are no plans to back-port 100.x technology into 10.2.x

The following table shows some key capabilities, not all, by version, and for the most part applies to all ArcGIS Runtime SDKs. For SDK-specific information, see that SDK’s release notes.

Capability in 10.2.x in 100.2
Web maps – edit and save No Yes
ImageService layers Yes Yes
Vector basemaps No Yes
Local raster No Yes
3D visualization No Yes
WMS layers Yes Yes
WMTS layers Yes Yes
Time-aware layers Yes Some SDKs
Group Layers Yes No
Mobile Map Packages No Yes
Bing layers Yes Yes
OpenStreetMap layers Yes Yes
Find Task Yes No
Geographic Transformations Yes Yes
Related Tables Yes Yes

Conceptually, 10.2.x and 100.x are quite similar as motivations for a rich native client developer experience within the ArcGIS Platform are the same. Technically, however, they are built on different architectures and have a different API and programming model.

The series of 10.2.x releases provide many users with SDKs that were tailored for specific industry demands. For example, some industries and their customers needed Android to be able to perform certain GIS tasks earlier than, say, iOS. Therefore, today, 10.2.x users find the SDKs with differing sets of functionality and released version numbers, based on the tactical needs for each SDK product. The 10.2.x architecture has worked very well to this point. It does, however, limit the ability for Runtimes to quickly adopt and keep up with the changes and innovations in the wider ArcGIS Platform vision of "Web GIS".

100.x is an evolution of the previous 10.2.x architecture and API. It is designed for future resiliency, better maintainability, more release agility, and alignment with Esri's Web GIS vision for today and tomorrow.

They are not intended nor designed to be utilized together for the same development project.

The series of 10.2.x SDKs are quite mature and have been available in the market for a number of years now. Many applications have 10.2.x technology at their core. To transition from 10.2.x to quartz, in many cases, will be a significant undertaking. Therefore, you'll find 10.2.x supported concurrently so that planning and migration to take advantage of 100.x's new capabilities can take place in a reasonable amount of time.

Cross-platform choices

With the release of 100.x, a set of ArcGIS Runtime SDKs support building apps using a single, shared codebase to target different platforms on both desktop and mobile devices.

  • ArcGIS Runtime SDK for Qt supports use of C++ and QML to build apps that target Windows, Linux, macOS, Android and iOS devices.

  • ArcGIS Runtime SDK for .NET is the choice for C# developers who need to target Windows, Android and iOS devices with their apps.

  • ArcGIS Runtime SDK for Java supports development and deployment of apps on macOS, as well as Windows and Linux.

For more information

Where to continue from here depends on the platform/programming language you choose. Follow these links to access the documentation for specific release notes.

Feedback on this topic?