What is the primary difference between getCurrentPosition() and watchPosition() methods in the Geolocation API?
The primary difference between these methods is their retrieval pattern: 1) getCurrentPosition() performs a one-time location request, retrieving the user's position just once when called, 2) watchPosition() continuously monitors the user's location, firing the success callback whenever the position changes, 3) watchPosition() returns an ID that can be used with clearWatch() to stop location monitoring, 4) Both methods are asynchronous and accept the same parameters (success callback, error callback, and options), 5) watchPosition() is ideal for tracking scenarios like navigation apps that need to update as the user moves, 6) getCurrentPosition() is more suitable for single-location needs like finding nearby businesses or setting an initial map position, 7) watchPosition() consumes more battery, especially with highAccuracy enabled, as it keeps location sensors active, 8) Both methods trigger permission requests if the user hasn't already granted location access to the site.