I’ve been tasked by my organization to create an app very similar to one that’s already been built as an open source app. Is it okay for me to reuse that source code in my app?
Yes! All of these apps are open source and covered by the Apache license, so you are free to use them as-is or as a starting point for a new app. This is one of the primary reasons that these apps were created – to showcase the power of our APIs and SDKs and make them easier to consume!
I found a bug in one of your open source apps. If I submit an issue, when can I expect for it to be fixed?
We do our best to maintain each of our apps, however cannot guarantee a specific timeframe within which the issue will be resolved.
If it’s something for which you already have a fix, in addition to opening an issue, we welcome you to also submit a pull request and contribute directly to the GitHub repository itself. We’d love to see our repositories represent collaboration with our developer community!
Do I need an ArcGIS for Developers account to build and run an unpublished app?
The need for a free ArcGIS for Developers account can vary by application depending on the features which it leverages. (For example, apps leveraging OAuth authentication to grant access to portal or organization content must use a client id and an ArcGIS for Developers account is required to create this.) To keep things simple, this is explicitly indicated in the README file of each app's GitHub repository.
In order to publish one of these apps as your own (which removes the 'For Developer Use Only' watermark) and allow others to use it, this will separately require you to have an ArcGIS Developers subscription and licensed access to the appropriate SDK. There are basic options of each that exist free of any cost. For more on that, see Developer Pricing and ArcGIS Runtime SDK Licensing.
I have a suggestion for a particular feature or app I’d like to see. Is there a place for me to share that feedback?
If your suggestion is a general one or revolves around the idea of a future open source app, feel free to open a discussion on the relevant developer community group pages. A discussion is a great way to raise attention to the idea.
Likewise, if your suggestion is specific to an existing app and you already have an idea in mind of how it could be implemented, feel free to:
log an issue in the appropriate repository and
submit a pull request with the suggested code change.
One of our repository admins will review the change and may either amend or collaborate with you on it before merging.
What differentiates these apps from the other apps I’ve seen from Esri, like `Collector for ArcGIS` or `Survey123 for ArcGIS`?
Esri makes available a number of apps that are intended to be used for production. These apps are official products from Esri meaning that they are fully supported and appear in Esri’s full product listing. They can be found in your platform's app store and are regularly maintained and updated. For a complete listing of these apps, check out: http://www.esri.com/software/apps.
The apps on this page are a little different. These applications are built with the intention of their source being opened to the public. The reason behind this is twofold:
Help showcase to you what can be done with Esri’s APIs and SDKs by providing useful, real-world examples.
Encourage and assist you in building your own applications by providing various common starting points that may mirror your use case.
While we make every effort to create apps at the highest quality possible, we make no claims as to the suitability of these apps to be used directly in production. There is no active support program as there is for Esri's official applications.
These apps kind of sound like more extensive samples of what I can already find in the SDK documentation. Is that all they are?
Not entirely. While it is true that the apps may seem a bit like many samples stitched together into a single application, it’s worth regarding them as much more than that. Whereas SDK and API samples tend to be isolated code snippets, these apps exemplify best practices in application architecture and thoughtful UI/UX considerations when building high-quality, fully-finished applications with Esri’s APIs and SDKs.
There’s a lot of talk on here of GitHub and repositories and forking, pull requests, etc. What if I don’t use GitHub or don’t understand it? Do you have any recommendations for familiarizing myself with Git and GitHub so that I can take advantage of these open source apps?
Be assured that GitHub is less daunting than it may seem. Not only is it a very common code-sharing platform in the world today, it is also one of the primary ways Esri shares its projects with its developer communities. To familiarize yourself with GitHub and Git (the version control system tool that it uses), we recommend checking out this 10 minute GitHub guide. After you're done, head on over to http://esri.github.io/ to see what other cool projects you may have been missing from Esri!