ArcGIS Maps SDK for Flutter enables you to build mapping applications for both iOS and Android platforms. Follow the steps below to ensure you have licensed the capabilities that your app uses and that you understand associated costs.
- License the capabilities you included in the app. Refer to the License levels and capabilities topic to determine the license level you require, and to the Get a license topic to learn how to acquire a license.
- Esri and data attribution requirements.
- If you deploy content or services from ArcGIS location services, see the FAQ topic in the Mapping and location services guide.
- Learn how to Choose your Apple iOS Developer Program and Deploy local data including Projection engine files.
Esri and data attribution requirements
When you use Esri technology, you must include Esri attribution and data attribution. This includes applications that use any ArcGIS API, SDK, service, content, or data. The attribution is required for applications that either contain a map or do not contain a map. These requirements are outlined in detail in Esri and data attribution.
Choose your Apple iOS Developer Program
An important factor in building your mobile solution for the iOS platform is your deployment and licensing agreement with Apple. The following three steps will guide you to a successful deployment:
-
Enroll in the iOS Developer Program.
If you want to distribute apps through the App Store, join the Apple Developer Standard Program as an individual or as a company. If you want to create and distribute proprietary in-house apps to your employees, join the Apple Developer Enterprise Program.
-
Test your iOS app.
During development, you can leverage your developer program agreement with Apple by testing your iPhone and iPad devices using the Xcode graphical debugger, collecting real-time performance data using Instruments' time line, and contacting Apple technical support when you need help.
-
Distribute your app.
Depending on your choice of a standard or enterprise program agreement, you can distribute your app in one of several ways (through the App Store, by email, or by posting it to a website or server).
Deploy local data
Deploying data locally allows access to that data without a network connection. Local data refers to files that are not part of your application deployment. Some examples of files typically used as offline data are mobile map packages, runtime geodatabases, offline locators and network datasets, and tile packages.
Local offline data can be downloaded while the device has a network connection—for example when tile packages are generated from the device and downloaded, or when using the desktop pattern to create mobile map packages which are then stored in a portal, and downloaded on the device while a network connection is available. Alternatively, data can be copied to a device's internal storage (also known as "sideloading") using tools such as iTunes or the Android Debug Bridge (ADB). Copying to a device can be useful when files are prepared using ArcGIS Desktop or Pro, and when deploying the same files to many devices.
Projection engine files
If your app uses grid-based transformations, you need to deploy the required Projection Engine files to the device. Projection Engine files can be copied (sideloaded) directly onto the iOS device using iTunes.
A full set of Projection Engine files are available on the downloads page.
Export compliance and restrictions on cryptography
When you submit your app to an app store (such as Apple's App Store, Google Play Store, or the Microsoft Apps store) your app may be stored on a server in the United States and is therefore subject to US export laws, regardless of where you or your organization are based. The Bureau of Industry and Security, under the United States Department of Commerce, regulates the export of technology that uses encryption. In some cases, the use of encryption may be considered an export of encryption software, subjecting your app to US export compliance requirements. Because the ArcGIS Maps SDK for Flutter uses encryption libraries provided by the underlying operating system, it does not require the declaration of non-exempt encryption when submitted as part of your app.
It is the responsibility of the app developer (and publisher) to make sure that an app complies with all applicable laws and regulations.
The following links provide more information about US export compliance and restrictions on cryptography: