Introducing the ArcGIS Maps SDKs

Today at the Esri European Developer Summit we announced that, starting in December, we will begin delivering our client SDKs and APIs under one name as the ArcGIS Maps SDKs.

This change reflects the common purpose and capabilities of these SDKs and will help to bring them to a broader audience.

New names, same great SDKs

In December, the names of the ArcGIS API for JavaScript and the ArcGIS Runtime SDKs will be changed. The name changes will look like this:

Current name New Name
ArcGIS API for JavaScript ArcGIS Maps SDK for JavaScript
ArcGIS Runtime SDK for .NET ArcGIS Maps SDK for .NET
ArcGIS Runtime SDK for Java ArcGIS Maps SDK for Java
ArcGIS Runtime SDK for Qt ArcGIS Maps SDK for Qt

When we roll out the name changes, the suite of ArcGIS Maps SDKs will look like this (note that the ArcGIS Runtime SDKs for iOS and Android are being superseded by the new ArcGIS Maps SDKs for Swift and Kotlin respectively):

There are a few reasons we’re doing this…

Common capabilities

The ArcGIS API for JavaScript, ArcGIS Runtime SDKs, and ArcGIS Maps SDKs for Game Engines all have a great deal in common:

And of course, each is already a world-class SDK with conceptual guides, an API reference, tutorials, samples, and community forums, and is backed by Esri Support.

Combining these SDKs under one name better reflects these common underpinnings.

Reaching a broader audience

We are proud to deliver some of the best SDKs available, and we want to make it as easy as possible to discover them. Whether searching the web or exploring package managers, the hard truth is that “ArcGIS” and “Runtime” often don’t mean much to a new audience. By including the word “Maps” in the SDK product name, we’ll make it much easier for developers to discover our SDKs when they’re searching for and evaluating location and mapping technologies for their projects.

One suite of SDKs, three groups

Although the ArcGIS Maps SDKs share many common capabilities, they do fall into three distinct groups, each of which is used to build specific kinds of solutions:

Here are a few notes on how we’ll refer to these SDK groups:

What will change?

This is a name change only, so while you might see the new name reflected on the surface (for example, in package manager listings, documentation, or the Esri Support site), the technology you work with won’t be changing.

Furthermore, the name will only change for new releases of the SDKs (see below).

What won’t change?

Even though only the name will change, it’s worth reiterating some of the things that won’t:

How does this affect versions of the APIs and SDKs that have already been released?

This is a forward-looking name change. Existing releases will not adopt the name change.

When will the change happen?

The ArcGIS Developers website will be updated in December when the next versions of the ArcGIS Maps SDKs for Native Apps and ArcGIS Maps SDKs for Game Engines are released.

Esri Support, the Esri Community, and other web pages, products, dashboards, and documentation will be updated to reflect the new name throughout 2023.

What do I need to do?

Just continue building amazing apps. When we roll out the name change in December, you can choose to reference the latest version of the SDK and continue to build and deploy your applications as before.

This blog post was updated to state that all 4.x versions of the ArcGIS API for JavaScript will adopt the new name, not just 4.25 and later.

About the authors

Nick Furness is a Product Manager for the ArcGIS Maps SDKs for Native Apps, and ArcGIS Maps SDKs for Game Engines, specializing in Swift and iOS. He's spent over 25 years working in the GIS space building projects ranging from small mom-and-pop solutions all the way up to enterprise utility and national government deployments. Nick presents at various Esri Developer Summits, the User Conference, and many other events, almost always talking about something to do with the Native Maps SDKs (although you might find the odd bit of JavaScript thrown in there).


Rex Hansen is a Product Manager for the ArcGIS Maps SDKs for Native Apps and ArcGIS Maps SDKs for Game Engines. He has over 25 years of experience in GIS, spatial analytics, and computer mapping. Currently, he guides the development of native technologies in the GIS industry to use authoritative geospatial content and analysis in offline workflows, photorealistic experiences, and immersive, extended reality solutions.


Mike Branscomb is a Product Manager for the ArcGIS Maps SDKs for Native Apps and ArcGIS Maps SDKs for Game Engines. With over 20 years of experience working in the Esri ecosystem, he specializes in .NET, Local Server, and 3D Scene Layers. Mike is also a Scrum Product Owner with over 10 years of experience guiding teams through the product development lifecycle.


Julie Powell is a Principal Product Manager, focusing on Esri's web development technologies. She works to ensure developers can be successful in building state of the art, purposeful solutions using ArcGIS software. Julie brings 20 years of experience working with global leaders such as Hewlett-Packard and Esri, delivering a variety of software solutions for both the enterprise and consumer markets. Julie has worked on a wide range of projects and consulting endeavors, including serving as technical lead for web mapping solutions for strategic customers.


Next Article

Explore BlueBikes ride data with ArcGIS Pro Charts

Read this article