Latest Contributions by RexHansen

Hi Tone,   The short answer to your question is yes - until July 2030.  More details...  Legally, the ArcGIS Maps SDK for Java (the last release being 200.6) will be retired November 2028, documented here: https://support.esri.com/en-us/products/arcgis-maps-sdk-for-java/life-cycle  ArcGIS Runtime SDK for Java 100.14 was retired May 1, 2026, documented here: https://support.esri.com/en-us/products/arcgis-runtime-sdks/life-cycle   If a product is retired, it's no longer supported by Esri - which means no further technical and product support.   Technically, ArcGIS Runtime SDK for Java 100.x and ArcGIS Maps SDK for Java 200.x can be licensed with ArcGIS named users and license strings (delivered via deployment packs).  Technically, these Java SDKs will continue to be able to be licensed with ArcGIS named users - no plans to change at this time - but also no guarantees that retired products are going to continue to support this approach with updates to ArcGIS Online or Enterprise in the future.     License strings are delivered in deployment packs for all supported versions, currently 100.x, 200.x, and 300.x.  If you purchase a Native Maps SDK Standard deployment pack today, you will get Standard license strings for 100.x/200.x (same string) and 300.x.   Technically you can buy more deployment packs that unlock 100.x/200.x until 200.8 is retired (July 2030).   In general, license strings are perpetual, they don't expire, but that does not mean the products they license are supported perpetually/indefinitely.  The primary purpose for the license string approach is to support clients that are offline for long periods of time/indefinitely and/or are accessed by users that do not have an ArcGIS identity/named user.      I'll state for the record, it's best to update your apps to use an SDK that is supported.  If you're using an SDK that has been deprecated (eg Java), you may need more time to transition to another SDK/client technology.   The product lifecycle for Runtime/Native Maps SDKs is purposefully long and includes an LTS release at the end of a major release cycle to provide a substantial runway for any migrations/transitions.               ... View more

Hi ABM Rokonuzzaman,  Great to hear you're considering use of the ArcGIS Maps SDK for .NET for your mapping application.  A few answers to your questions:  1.  Yes, as long as you abide by Esri's terms of use: https://www.esri.com/en-us/legal/terms/full-master-agreement. These are the same terms you clicked through when downloading the ArcGIS Maps SDK for .NET Nuget packages or when installing the VSIX.  2.  The Runtime Lite license string you acquire with an ArcGIS Online or ArcGIS Location Platform account is a perpetual license for ArcGIS Runtime SDKs 100.x and ArcGIS Maps SDKs for Native Apps 200.x (this includes the ArcGIS Maps SDK for .NET).  While the license does not expire, the product (Runtime or Maps SDK) it licenses has a lifecycle and will retire at some point.    3.  No, when a Native Map SDK is licensed for production use (eg licensed with a Lite license string) the watermark will be removed from the MapView/SceneView.   There is no limit to the number of deployments of Native Maps SDK apps licensed only with a Lite license string.  4.  To acquire a license string for any license level above Lite, or any extensions, requires the purchase of a deployment pack.  To get a price, contact the Esri office that serves your region: https://www.esri.com/en-us/contact#c=us&t=1   To abide by the Esri terms of use you need to determine the number of deployments to purchase the appropriate number of packs, and track the number of deployments over time to remain in compliance (and may need to purchase more packs if there are more deployments).    Thanks  -Rex Hansen Esri Product Manager, ArcGIS Maps SDKs for Native Apps             ... View more

Hi SWE,  I'll answer questions 1 and 2.  1 - Correct, direct access to S-63 encrypted ENC data is only supported with the ArcGIS Maps SDK for .NET at this time.   However, we are open to considering opportunities to support in other Native Maps SDKs.  2- Correct, ArcGIS Runtime deployment packs are sold in bundles of deployments.  Direct access local data that is not part of the ArcGIS system, such as ENC data, requires ArcGIS Runtime/Native Maps SDKs be licensed at the Standard level at a minimum.  One Standard deployment pack includes 25 deployments.   If you choose to license ArcGIS Runtime/Native Maps SDKs at the Standard level using a license string, the minimum purchase is one Standard deployment pack.  Another option to consider is the named user workflow.  If the user of your app will have an ArcGIS identity/account associated with a Creator user type or higher, this named user includes a Standard license you can use to license Runtime/Native Maps SDKs.  This requires ArcGIS Online or ArcGIS Enterprise, but if already available then you can purchase user types individually.  See this page in our doc for more details on the named user option: https://developers.arcgis.com/qt/license-and-deployment/get-a-license/ Feel free to send me a direct message if you'd like to share more details on your project so we can factor into our product plan.  Thanks -Rex      ... View more

Good feedback.   Unfortunately there are no specific plans to deliver geospatial capabilities in Rust at the moment.   A couple notes: It appears you've logged a related issue on the Developer ideas site: https://community.esri.com/t5/developers-ideas/offer-a-webassembly-sdk-for-rust-c-and-net-blazor-development/idi-p/1005474   That's a good place to start... and drum up support as well.  From a geometry operations perspective, an open source version of the geometry engine is available in Java: https://github.com/Esri/geometry-api-java   This opens up an opportunity for the community to port to a Rust implementation.  For ArcGIS Runtime specifically, we are seriously considering support for use in a service/server context.   This would likely be a streamlined version of Runtime, geometry engine, feature serialization, query and edit operations (no visual map or scene generation).      ... View more

I believe the ArcGIS API for JavaScript already supports WebAssembly.  For plans relating to the Web App Builders specifically, probably best in inquire in the ArcGIS Web App Builder community: https://community.esri.com/t5/arcgis-web-appbuilder/ct-p/arcgis-web-appbuilder   With respect to ArcGIS Runtime: No plans a native developer experience with JavaScript (eg React Native) at the moment.    The Qt Company's SDKs do support WebAssembly, and our ArcGIS Runtime SDK for Qt team has investigated, but we have no plans to deliver support for WebAssembly at the moment.  Behind the scenes the geometry engine in Runtime is available in the ArcGIS API for JavaScript via a WebAssembly implementation. Feel free to add a new idea or enhance an existing idea for ArcGIS Runtime: https://community.esri.com/t5/arcgis-runtime-sdks-ideas/idb-p/arcgis-runtime-sdks-ideas   ... View more

No specific plans to integrate knowledge graphs in ArcGIS Runtime at the moment, but we are keeping an eye on how they surface within the ArcGIS system.   Ideally, they surface through a specification (eg REST, webmap, mobile map, etc) where we can build out functionality to access and use.   If you have use case in mind, this may be a good addition to the ArcGIS Ideas board: https://community.esri.com/t5/arcgis-runtime-sdks-ideas/idb-p/arcgis-runtime-sdks-ideas      ... View more