Architecting for Privacy: Why I Chose Local-Only SQLite Over Cloud Sync

It was a quiet afternoon in the local library when the reporter was deep into a debugging session. Suddenly, the phone emitted a loud notification chime from maximum volume, echoing off the high ceilings. The room turned to look at him, causing a total disruption of collective focus. The reporter felt embarrassed and the sinking feeling of causing a disturbance in a place of quietude.

This experience led him to start building Muffle, an app focused on privacy. The problem with existing solutions is that they often require constant manual input to stay polite, are bloated with features, or demand intrusive permissions. Muffle would be an entirely local-only application, with all data stored on the user’s device using Room, an abstraction layer over SQLite.

This choice was a technical constraint, ensuring that sensitive data like geographical boundaries and time windows never left the user’s phone. The app is fully functional offline and survives reboots due to AlarmManager and WorkManager tasks rescheduled based on the local database state. However, if the user gets a new phone, they cannot simply log in and see their old routines.

The reporter spent weeks fighting with background location updates when paired with strict power-saving modes, resulting in the OS aggressively killing the process if it hadn’t seen activity in the foreground for a while. He also realized the importance of maintaining a privacy-first label by architecting for it and being careful with third-party libraries.

If starting over, he would implement a simple JSON export/import feature for data backup. The biggest takeaway is that constraints often lead to better software, simplifying the stack and removing security bugs.