@creedengo/avoid-high-accuracy-geolocation

February 3, 2026 · View on GitHub

📝 Avoid using high accuracy geolocation in web applications.

⚠️ This rule warns in the ✅ recommended config.

Why is this an issue?

High-precision geolocation typically requires more power from the device's GPS hardware. By requesting less accurate geolocation, you can reduce the power consumption, leading to extended battery life, which is crucial for mobile devices.

Obtaining highly accurate geolocation often involves more complex calculations and processing, which can increase CPU usage. If the application or service does not critically require pinpoint accuracy, opting for a less accurate geolocation can help minimize the strain on the device's CPU.

Web

var options = { enableHighAccuracy: true, timeout: 5000, maximumAge: 0 }; // Non-compliant
navigator.geolocation.getCurrentPosition(
  (pos) => console.log(pos),
  (err) => console.warn(err),
  options,
);

In these examples, the enableHighAccuracy option is set to false (the default), indicating that the application prefers lower-accuracy geolocation to conserve resources:

navigator.geolocation.getCurrentPosition((pos) => console.log(pos)); // Compliant by default

var options = { enableHighAccuracy: false, timeout: 5000, maximumAge: 0 }; // Compliant
navigator.geolocation.getCurrentPosition(
  (pos) => console.log(pos),
  (err) => console.warn(err),
  options,
);

React Native

In this example, we ask the user to turn on high accuracy location mode which enables network provider that uses Google Play services to improve location accuracy and location-based services:

import * as Location from "expo-location";

Location.enableNetworkProviderAsync(); // Non-compliant

Prefer to ask the user to turn on lower-accuracy geolocation to conserve resources:

import * as Location from "expo-location";

Location.requestPermissionsAsync(); // Compliant

Resources

Documentation