posted: March 10, 2014 | author: Marianne Cardwell
I think this is my fifth year at the Esri DevSummit. I tend to count the years by remembering the hotels where I’ve stayed. There’s the Hilton, the Renaissance, the Courtyard, and the cheap timeshare that was cheap for a reason. This year, I’m staying at the Extended Stay a couple of blocks away from the convention center. If you’ve been here, you know it’s a good idea to book your hotel as early as possible or it becomes really difficult to find a reasonably-priced room within walking distance.
Overall, it’s a great conference for Esri developers. So great, in fact, that I haven’t been to the International User Conference in San Diego in 10 years! The content is very good, Esri staff is on-hand to answer questions and the fact that it’s in Palm Springs in March is the cherry on top. Especially if you’ve been in the Midwest this winter…
So, what have I learned so far? I’ll list the highlights in this post and will update it at least once daily.
This is the biggest DevSummit so far: 1800 attendees, including 300 Esri staff.
Unlike other years, I didn’t see any huge revelations, but mainly steady improvement of what’s available. Having said that, here are the biggest themes:
This was a great keynote, one of the better ones I thought. Chris Wanstrath, GitHub’s CEO and co-founder, was the speaker and spoke of his background, how GitHub came to be and how to look at open-source code. It was a dynamic talk and I recommend you check it out!
I attended the “Introduction to the New ArcGIS Professional .NET SDK” session and this really confirmed to me that this will eventually replace Desktop. Esri did not actually come out and say that though, but I think that given enough time, it will.
Having said that, if you’re looking at this from the ArcObjects perspective, you might be disappointed with what will initially be available. They will provide some minimal API functionality to start and increase that functionality over time based on customer demand. I asked about some of the big AO libraries such as geometry & geodatabase and it sounds like the first beta will include some geometry & maybe geodatabase functionality. What I was told was that it would be a fine-grained API similar to what’s available in ArcGIS Runtime.
As with Desktop development, the SDK will include Visual Studio templates. The first release will focus on VS 2013. Customization will be done via the development of add-ins. The UI is quite flexible. However, for those of us who mainly have experience with ArcObjects, the development approach will be a little different as the API is designed to use .NET’s asynchronous programming with async & await.
Sample code will be stored on GitHub and companion datasets will be hosted on ArcGIS Online. Esri hopes that developers like us will submit new or edited samples. This is a great idea and will hopefully provide more robust samples.
ArcGIS Pro will be released with 10.3 this Summer, so you won’t have to wait too long to start playing with it.
For a brief overview, check out the video below that comes from Tuesday’s plenary:
I am VERY excited about this. So far the demos look really slick and it’s obvious Esri has put quite a bit of thought into it. This explains why the next version will be version 4 and the other web APIs will be stuck at 3. The JSAPI will have a new internal architecture but should look the same to us developers. Esri says that this will be 99% backward compatible.
The API will include new 3D classes, including layers, symbology, labeling, popups, etc.
A lot will have to come together at once. For example, there will be a new service type in ArcGIS Server (Scene Service) for 3D vector data (mesh, point, line and polygon). We’ll be able to access this type of service in the Runtime SDKs, ArcGIS Pro and of course the JSAPI.
Check out this video from the plenary:
You might remember reading a recent announcement from Esri encouraging developers to switch to the JS API. Esri will soon release version 4 of the JS API but the Flex & Silverlight APIs will remain at 3. They’ll still maintain them but they will not release any new major functionality for those.
If you’ve used the Flex API because it was so quick & easy to develop new websites, you’ll be happy to know that Esri is releasing the ArcGIS WebApp Builder, which will allow you to create new JS websites in very little time. You’ll install the WebApp Builder on your machine and will have access to all of the source code (supposedly not minified or obfuscated). The Builder looks really good and includes the following functionality:
You can already sign up for the beta, which will be released on March 28. The beta will be fully supported. The public release is timed for 10.3.
Did I mention that this will include support for 2D AND 3D maps? And that it’s been designed to run on IE9+, FF, Chrome, and Safary 3+?
This is big and as I said above, we at Woolpert are *very* excited about this. We’ve been waiting for something like this for a while. It’s going to be integrated with pretty much everything: from ArcGIS Server to the JS API to Runtime to Pro.
Do check out the various JS sessions from the DevSummit, such as:
The new ArcGIS Runtime for .NET will handle all Windows devices (desktop, phone, store). Esri’s push with the ArcGIS Runtime for Qt will allow you to use the same source code for iOS, Android & Windows.
This is a big effort for the Runtime SDKs. If you’re going to do this, check out the ‘Building Offline Apps with ArcGIS Runtime SDKs’ session (there are two: Part I & Part II).
Start making plans for next year for the 10th DevSummit! It will be March 9, 2015 to March 12, 2015.