Which default locator service should be used in Search component?

[yo1995]

arcgis-maps-sdk-swift-toolkit/Sources/ArcGISToolkit/Components/Search/LocatorSearchSource.swift

Lines 17 to 35 in 6566b1b

	/// Uses a Locator to provide search and suggest results. Most configuration should be done on the
	/// `GeocodeParameters` directly.
	public class LocatorSearchSource: ObservableObject, SearchSource {
	/// Creates a locator search source.
	/// - Parameters:
	/// - name: The name to show when presenting this source in the UI.
	/// - locatorTask: The `LocatorTask` to use for searching.
	/// - maximumResults: The maximum results to return when performing a search. Most sources default to `6`.
	/// - maximumSuggestions: The maximum suggestions to return. Most sources default to `6`.
	public init(
	name: String = "Locator",
	locatorTask: LocatorTask = LocatorTask(
	url: URL(
	string: "https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer"
	)!
	),
	maximumResults: Int = 6,
	maximumSuggestions: Int = 6
	) {

We are currently using the public service for the default locator. However, in 2021 we started to move away from the public service endpoints and use the "Citra" API-metered services instead. See examples in Esri/arcgis-runtime-samples-ios#1055 and Esri/arcgis-runtime-samples-ios#1075. i.e.,

old/public
https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer
new/Citra
https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer

However, this would require API key/Auth for the toolkit. Sometimes user may not want to set the global API key to the environment, so it could be a hassle for some usecases.

• A similar discussion for the public vs Citra route solving service: common-samples/issues/2653
• There is a discussion in swift-kotlin-sync channel, and this suggestion is from @rchintapalli