Modern smartphones, including both iOS and Android devices, are equipped with sophisticated location capabilities. These capabilities utilize signals from satellites and ground-based cellular towers to determine a device's position with varying degrees of accuracy. The operating system exposes APIs that allow applications to access this location data.

Privacy and Permisions

Location access is a sensitive privacy concern. On iOS, an application must obtain explicit user authorization at runtime to retrieve location data. Furthermore, the user must have the system's location services enabled. Failure to meet these conditions will result in the application being unable to access location information.

For iOS development, configuring location permissions requires adding specific keys to the Info.plist file. The exact configuration can be extensive and varies across OS versions. Android permission configuration is often more complex due to significant fragmentation across device manufacturers and OS versions.

Third-Party Location SDKs

Many mobile applications integrate SDKs from major mapping providers like Baidu Maps or Amap (Gaode Maps), which offer Flutter plugins. A common question arises: why use these SDKs when the device's operating system provides native location APIs?

Several factors contribute to this choice:

1. Platform Fragmentation: Handling the nuances and differences between iOS versions and, more significantly, the vast array of Android OEM implementations can be a substantial development burden. Third-party SDKs abstract this complexity by providing a unified interface.
2. Coordinate Systems: Location coordinates (latitude and longitude) are not standardized globally. There are multiple datum and coordinate systems in use:
   • WGS84: The international standard. This is the default system returned by iOS location services.
   • GCJ-02 (Mars Coordinate): A Chinese standard that applies an obfuscation algorithm to WGS84 coordinates for use within China.
   • BD-09: A coordinate system used by Baidu, which applies a further transformation on top of GCJ-02. Using WGS84 coordinates directly with Chinese map data will result in significant positional inaccuracies. Third-party SDKs for the Chinese market typically handle the conversion to GCJ-02 or BD-09 internally.

Managing these platform-specific details and coordinate transformations introduces significant development and maintenance overhead, which often makes relying on established SDKs a pragmatic choice, despite potential licensing costs.

Flutter Community Packages

The Flutter community offers packages like location (pub.dev/packages/location). While popular, its implementation can be problematic. The basic usage pattern involves checking and requesting service enablement and permissions before fetching data.

import 'package:location/location.dart';

Future<LocationData?> fetchUserLocation() async {
  Location locService = Location();
  
  // Check if location services are enabled.
  bool isServiceActive = await locService.serviceEnabled();
  if (!isServiceActive) {
    isServiceActive = await locService.requestService();
    if (!isServiceActive) {
      print('Location service request denied.');
      return null;
    }
  }

  // Check location permissions.
  PermissionStatus currentPermission = await locService.hasPermission();
  if (currentPermission == PermissionStatus.denied) {
    currentPermission = await locService.requestPermission();
    if (currentPermission != PermissionStatus.granted) {
      print('Location permission not granted.');
      return null;
    }
  }

  // Retrieve the current location.
  try {
    LocationData currentPosition = await locService.getLocation();
    return currentPosition;
  } catch (e) {
    print('Failed to get location: $e');
    return null;
  }
}

In practice, this package has been reported to cause UI freezes on certain iOS versions (e.g., iOS 16), despite its seemingly straightforward API. These issues highlight potential instability compared to more mature commercial SDKs.

A critical limitation for applications targeting China is that the location package returns coordinates in the WGS84 standard. To use these coordinates with Chinese maps or for geofencing, conversion to GCJ-02 is necessary. While libraries exist for this conversion (e.g., JZLocationConverter for Objective-C), a Dart implemantation is required for Flutter.

Below is a utility function for calculating the distance between two geographic points using the Haversine formula, which assumes a spherical Earth model and may have minor errors over very large distances.

import 'dart:math';

class GeoPoint {
  final double latitude; // in degrees
  final double longitude; // in degrees
  GeoPoint(this.latitude, this.longitude);
}

class GeoCalculator {
  static const double earthRadiusKm = 6371.0;

  /// Calculates the great-circle distance between two points on Earth
  /// using the Haversine formula. Returns distance in kilometers.
  static double calculateDistance(GeoPoint p1, GeoPoint p2) {
    double lat1Rad = _degreesToRadians(p1.latitude);
    double lon1Rad = _degreesToRadians(p1.longitude);
    double lat2Rad = _degreesToRadians(p2.latitude);
    double lon2Rad = _degreesToRadians(p2.longitude);

    double deltaLat = lat2Rad - lat1Rad;
    double deltaLon = lon2Rad - lon1Rad;

    double a = pow(sin(deltaLat / 2), 2) +
        cos(lat1Rad) * cos(lat2Rad) * pow(sin(deltaLon / 2), 2);
    double c = 2 * atan2(sqrt(a), sqrt(1 - a));

    return earthRadiusKm * c;
  }

  static double _degreesToRadians(double degrees) {
    return degrees * pi / 180.0;
  }
}

// Usage example:
// GeoPoint newYork = GeoPoint(40.7128, -74.0060);
// GeoPoint london = GeoPoint(51.5074, -0.1278);
// double dist = GeoCalculator.calculateDistance(newYork, london);
// print('Distance: ${dist.toStringAsFixed(2)} km');