Architecting a Low-Power Geofencing Engine for Android

In a quiet afternoon meeting, the speaker discovered that their phone was disrupting the discussion with loud ringtones. This experience led them to realize that their device lacked the context-awareness needed to manage sound appropriately. The speaker found themselves constantly toggling between sound settings, which led to missed critical calls and distractions during lectures.

Existing solutions were often cumbersome, requiring cloud synchronization and constant battery-draining polling. The speaker wanted a tool that could handle this reliably, focusing on offline functionality, privacy, and battery efficiency. They opted for a geofencing engine, implementing it using the GeofencingClient within the Google Play Services Location API.

This approach offloads monitoring to the system, waking up the app only when a location transition occurs. However, the accuracy of geofences depends on the phone's signal environment, leading to false exits in dense urban areas. To address this, the speaker implemented a hysteresis buffer, introducing a timer to prevent constant toggling of sound profiles.

They also used IntentService to process events in the background and a Room database for persistence, ensuring that the app could recover gracefully if the system killed the background process. The speaker learned that background execution is fragile on modern Android versions due to Doze mode and battery optimizations. They added a feature to trigger a foreground service upon a geofence event, improving reliability.

Additionally, the speaker realized the importance of allowing specific contacts to override silent mode and shifted their storage architecture to store UTC timestamps for time zones. Overall, the speaker emphasizes the need to respect user battery and privacy when architecting background systems, recommending the use of event-based systems provided by the platform instead of polling-based solutions.