|
IDEA
|
@JB19Starting with version 4.34, we will be hosting archived (currently supported) versions of the SDK. Here is version 4.34: https://archive.developers.arcgis.com/javascript/v4-34/
... View more
2 weeks ago
|
0
|
0
|
75
|
|
IDEA
|
@ChristianNitschkowski_AIDB this is a great suggestion. We'd love to gather more details about your requirements - for this specific ask and any other component customization requirements you have. Please consider filling out this survey to help inform our roadmap... all responses are read by the SDK product team: https://arcg.is/14yzvW1 cc @HeatherGonzago
... View more
2 weeks ago
|
0
|
0
|
36
|
|
IDEA
|
Hello @fdeters ! We would really love to learn more about your application requirements. Do you have other JS Maps SDK component configuration/styling needs? When you have the chance, it would be great if you could fill out this survey for us to help inform our roadmap: https://arcg.is/14yzvW1
... View more
2 weeks ago
|
0
|
0
|
79
|
|
BLOG
|
This is your chance to inform the roadmap for the JavaScript Maps SDK components! We are gathering requirements for customizing components through styling, configuration, and slots -- fill out this survey, and ensure we are aware of your application's requirements. All responses will be read and carefully considered by the SDK product team. Background: Web components encapsulate HTML, CSS and JS within a shadow DOM which ensures that internal styles and logic do not conflict with the rest of the application. As a result the shadow DOM makes it very complex for developers to customize the DOM or style of the component internal elements. For that reason, we would like to offer documented and tested APIs and tokens with components so that you can style and customize the components to meet your requirements. By providing as much detail as possible, we will be able to identify and prioritize enhancements to the components. Your input is extremely valuable as it informs our roadmap as we continue to evolve the JS Maps SDK component library.
... View more
2 weeks ago
|
3
|
0
|
163
|
|
BLOG
|
The next release of ArcGIS Maps SDK for JavaScript (version 5.1) is just around the corner! Keep your eye out for our release blog and documentation update which will go out on June 25th. 5.1 will include some great updates to the arcade editor component, enabling debugging and the arcade assistant, scale-based rendering for unique values and class breaks, and LOTS more. Stay tuned!
... View more
3 weeks ago
|
7
|
0
|
281
|
|
BLOG
|
Starting with version 4.34, archived versions of the JavaScript Maps SDK documentation website are now available, providing access to earlier documentation and resources for developers who need them. The site corresponding to version 4.34 can be accessed here: https://archive.developers.arcgis.com/javascript/v4-34/ While we recommend using the current version of the SDK to take advantage of the latest enhancements and ensure maximum stability, we recognize that not all developers are ready to upgrade immediately. Beginning with version 4.34, all supported versions will have a corresponding archive SDK website, enabling you to continue maintaining your applications until you are ready to move to the latest version.
... View more
05-11-2026
02:07 PM
|
9
|
0
|
283
|
|
POST
|
@Stefano_Schiavini the new (beta) support in ArcGIS Online for the Google Photorealistic Basemap is currently only available for use in Map Viewer, Scene Viewer, and configurable apps/builders hosted in Online (Experience Builder, Instant Apps...). We are actively working on adding support for custom apps (and apps hosted outside of Online), to be made available in a future release. Stay tuned!
... View more
03-03-2026
08:02 AM
|
0
|
0
|
553
|
|
IDEA
|
@Michele_Hosking 4.33 is the ArcGIS Maps SDK for JavaScript version which is what powers ArcGIS Online/Enterprise web mapping. Enterprise didn't pick up version 4.33 until 12.0 so you would have to upgrade in order to see the multipoint labeling support.
... View more
02-02-2026
07:14 AM
|
0
|
0
|
1273
|
|
BLOG
|
We’re excited to announce a major change in how we version and release the ArcGIS Maps SDK for JavaScript; we’re moving to semantic versioning (SemVer)! This change will make it easier for developers to upgrade between versions, understand release impacts, plan upgrades, and integrate with modern tooling. Learn more by reading this blog and feel free to share any thoughts or questions you have under this post. https://www.esri.com/arcgis-blog/products/js-api-arcgis/announcements/arcgis-maps-sdk-for-javascript-is-moving-to-semantic-versioning
... View more
10-09-2025
03:54 PM
|
9
|
1
|
1340
|
|
BLOG
|
The goal of this blog is to provide information and guidance for customers using web applications that are causing browser tab refreshing on iOS devices. This can be any web app, including ArcGIS configurable apps and builders, custom apps built with the ArcGIS Maps SDK for JavaScript, or any other memory or processing intensive app. The foundational differences between mobile and desktop environments - especially in terms of hardware and memory management - are significant. A mapping app that runs flawlessly on a desktop may not perform well on a mobile device. When it comes to building web mapping applications, developers often encounter unique obstacles when targeting Safari and all other browsers on iOS. iOS devices often have stricter memory and CPU usage limits compared to their Android counterparts, making web mapping applications more susceptible to browser tab refreshes. Adding to the challenge, iOS 18.4 has introduced a regression leaking image bitmaps that will accelerate the occurrence of browser tab refreshes in certain scenarios. In particular, maps that include a layer using image tiles (raster basemaps, tiled imagery layers) or full-screen images (map image layers) will see the issue more often. We have created a workaround for the iOS issue in the ArcGIS Maps SDK for JavaScript which will be included with version 4.34 and will drastically reduce the refreshing behavior.. This guide will explore these considerations, offer advice for better understanding issues you may be experiencing when running your app on a mobile device, and provide resources for tuning your app for performance. Web mapping in iOS While today’s web mapping technology provides rich, dynamic visualizations and interaction with anything from small to very large datasets, they are also inherently memory and processing intensive. On iOS, memory constraints are more tightly managed by the system to prevent a single tab from affecting the entire device. These limits are process-based, meaning a webpage runs in a dedicated process with a memory ceiling. When a browser tab exceeds the set limit, the system will immediately free up memory by reloading the tab and effectively resetting your application to its default state. Tuning your ArcGIS map and app for performance When creating web apps, the goal is to create performant web applications, but this shouldn't come at the cost of other user needs. The key is to balance user expectations with the highest possible performance. The ArcGIS Maps SDK for JavaScript is already optimized for efficient data fetching and visualization, so you should test your application on different devices before beginning any manual optimization. To benefit from constant improvements in CPU and memory usage, always use the most current SDK release. If you still encounter performance issues, consider reducing the amount and complexity of data that your app must display. For example, you can reduce the number of layers in your map and use techniques like client-side aggregation (clustering or binning) to reduce the number of features the map needs to draw. There are several available resources that cover performance optimization techniques for maps and apps, such as: Blog: Performance Tips for ArcGIS API for JavaScript Optimize performance in ArcGIS Best practices for creating scalable web maps General Best Practices To ensure your web mapping app performs well on iOS, consider these recommendations: Reduce Memory Impact: The most common cause of crashes is excessive memory usage. To mitigate this, encourage users to close other tabs, close non-essential applications, and restart their device to reset the device’s memory state. Learn Mobile Debugging: Familiarize yourself with mobile debugging techniques. Apple's Web Inspector, available in Safari on macOS, can be used to debug a connected iOS device. This allows you to inspect the DOM, view network requests, and analyze CPU and memory usage. If you are having challenges with the Safari inspector crashing while connected to your mobile device, you can also do some level of debugging using the desktop Chrome DevTools on MacOS. Isolate Bugs: When troubleshooting, try to isolate the issue as much as possible. While it can be challenging with complex, custom applications, narrowing down the problem helps the development team and others assist more effectively. Check Device and OS Support: Always verify that the mobile device is still supported and is running the latest operating system. Older OS versions generally have lower memory limits and may not support the latest optimizations. Consider Native/Hybrid Apps: For some applications, a native or hybrid app, such as Capacitor.js, might be a better choice. This approach offers developers a more direct relationship with the operating system, including the ability to detect low memory or high CPU usage and react proactively within the app to prevent crashes. To build a native mapping app, you can use the ArcGIS Native Maps SDKs, and with SDKs like Flutter, creating native apps has never been easier. Debug with a Mobile-First Mindset: You can't treat mobile devices the same as laptops. Differences in hardware, operating systems, battery life, and network speeds mean that an app that runs well on desktop may not run well on mobile. Remember, you have very limited control over other apps running in the background, which can consume valuable CPU and memory resources and contribute to crashes. Understand Crash Categories: Crashes typically fall into three categories: bugs, memory usage, and CPU usage. While bugs can be in the application or API code, they can also be in the browser or the OS. It's crucial to remember that mobile devices have much more limited resources than laptops, making efficient use of memory and CPU paramount. Communicate Expectations: Help end users understand that mobile devices are not the same as laptops. Due to differences in hardware, operating systems, and network speeds, an app that runs well on a desktop may not perform the same on a phone. Ultimately, understanding the unique constraints and behaviors of iOS is key to building a robust and performant mobile web mapping application.
... View more
10-08-2025
12:38 PM
|
2
|
0
|
1065
|
|
POST
|
Ahh, ok. Sorry about that. yes no This one is a bit more complicated, see below The Widget class is going away with widgets. With regards to view models, it is a bit more complicated. First off, we know how important it is that developers can continue to create tailored experiences with the SDK. Going forward, you will be able to build the same custom experiences using the underlying business logic, but the implementation will change. As we move to the component-based architecture, view models are being considered for 3 possible buckets: 1) The View Model will be kept in the core API, but reworked/moved: The functionality will simply move to another location (since they are currently located in the widgets/ folder). 2) The View Model will be dissolved into the core API: The functionality will be available in core, but through other APIs. For example, AreaMeasurement2DViewModel logic could move to an analysis API similar to what 3D has for AreaMeasurementAnalysis. 3) The View Model's logic belongs to the component: The logic will be exclusively used by the component and the view model will be deprecated and later removed. View models fall into this category when we believe that they don't provide additional value to developers. For example, in the case of the WeatherViewModel, different APIs already exist to set Weather directly on SceneView so the view model isn't really necessary. Categorization of view models into the three buckets above depend on the explanation above, but also based on what we are learning from customers. We really want to understand which view models are being used, and for what purpose so that we can make sure we account for the wide variety of scenarios and customer requirements. We are encouraging customers to fill out this survey to help inform this roadmap: https://arcg.is/005zS9 One other aspect that I would like to share is that sometimes view models are used to make a slight adjustment to the UI (like hide part of it, or add a button to do something). Part of our roadmap is to implement slots which are placeholders within the component UI for you to embed your own functionality/workflows. Components also have configuration and styling options through css properties. So in some cases, developers can write and maintain less custom code because they are able to use the out of box components (as opposed to creating their own UI on top of the view models), and still tailor the experience to meet their requirements. So, the more specific information you can share in the survey, the better we can design the component options for your needs. I am working on a blog that covers this topic. I will post a link here when it is published.
... View more
07-28-2025
08:58 PM
|
4
|
3
|
1844
|
|
POST
|
Hello @Aeseir! We are making a full transition to W3C standards-based web components. Widgets will eventually be removed from the SDK. We are currently working towards the following tentative schedule: All widgets deprecated by Q1 2026 Widgets removed Q1 2027 You can find more information about our transition plan in this blog: https://www.esri.com/arcgis-blog/products/js-api-arcgis/developers/javascript-maps-sdk-a-full-transition-to-components
... View more
07-28-2025
12:46 PM
|
1
|
5
|
1869
|
|
IDEA
|
Hi @jacobgqc thanks for sharing this idea. We do have a data weighted heatmap which multiplies each pixel's density by the attribute value, but I am guessing that it isn't what you are looking for. Can you share a visual of what you want to achieve?
... View more
07-23-2025
08:38 AM
|
0
|
0
|
1293
|
|
IDEA
|
Hello everyone, good news... We are adding support for labeling multipoint features in version 4.33 which is going out later this month! That capability will of course be available in Experience Builder as well.
... View more
06-16-2025
02:26 PM
|
0
|
0
|
2070
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 2 weeks ago | |
| 7 | 3 weeks ago | |
| 9 | 05-11-2026 02:07 PM | |
| 9 | 10-09-2025 03:54 PM | |
| 2 | 10-08-2025 12:38 PM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|