--- title: Architecture Decisions Behind Building a Simple Personal... description: A backend engineer documents the architectural decisions behind building a local-first personal desktop/mobile app using Flutter and SQLite. The post walks... canonical: https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Architecture Decisions Behind Building a Simple Personal Software Tool | daily.dev og:description: A backend engineer documents the architectural decisions behind building a local-first personal desktop/mobile app using Flutter and SQLite. The post walks... og:url: https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4 og:image: https://api.daily.dev/og/posts/piWLYEZW4.png og:image:alt: Architecture Decisions Behind Building a Simple Personal Software Tool og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Architecture Decisions Behind Building a Simple Personal Software Tool **[DEV](https://daily.dev/sources/devto)** · 13 min read · 75 upvotes · 3 comments ## Summary A backend engineer documents the architectural decisions behind building a local-first personal desktop/mobile app using Flutter and SQLite. The post walks through choosing Flutter for cross-platform code sharing without a server, designing a debounced sync strategy using cloud storage (iCloud/Google Drive) as a courier rather than a backend, handling conflict resolution with Last-Write-Wins timestamps, managing SQLite schema migrations across app versions, and how the local-first architecture naturally enabled a one-time purchase business model instead of SaaS subscriptions. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can you sync data across devices in a local-first app without running a backend server? Use cloud storage like iCloud or Google Drive purely as a file transport, not a database. Each device keeps its own local SQLite database, and the cloud only carries changes between them without validating or querying the data. Writes are debounced for 30-60 seconds before syncing, with a final sync on app close and a metadata check on startup to detect newer data. _Anyone weighing local-first sync approaches can find grounded architecture discussions like this through daily.dev._ ### What conflict resolution strategy works for syncing data between multiple devices without using CRDTs? A last-write-wins approach using a last_modified_at timestamp on every record is a simpler alternative to CRDTs for low-conflict scenarios like a personal expense tracker. When two versions of a record meet, the newer timestamp wins. It isn't perfect for simultaneous edits, but the probability of that happening is low enough to skip the added complexity of CRDTs. _Developers deciding between CRDTs and simpler timestamp-based sync can track these trade-offs via daily.dev._ ### How do you handle database schema changes across app versions without breaking existing users' data? On startup after an update, the app checks the local database's schema version and automatically runs migrations if it's outdated, applying incremental changes like adding columns or reshaping tables one version step at a time. This lets a database created under an old app version safely evolve to match the newest expected schema without requiring users to export and reimport their data. _Developers building schema migration logic for local-first apps can follow similar architecture writeups on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@jenueldev** · 1 upvotes > Local-first Flutter + SQLite is a compelling fit—the cloud-as-courier sync model keeps the architecture refreshingly simple. **@trevorsuna** · 1 upvotes > Using cloud storage as a courier instead of a backend is a strong way to keep the local-first model honest. The tricky edge is Last-Write-Wins: clock skew and simultaneous edits can silently discard valid changes. Per-record versions, tombstones, and selective field-level merging would add resilience without turning the app into a distributed-systems project. **@dcorto** · 0 upvotes > nice read i really enjoyed 🔝 ## Similar posts on daily.dev - [Why We Picked Flutter Over React Native for an App That Had to Work Offline](https://daily.dev/posts/why-we-picked-flutter-over-react-native-for-an-app-that-had-to-work-offline-gvf1othfr) · Medium · 1 upvotes · 0 comments - [The Architecture Of Local-First Web Development — Smashing Magazine](https://daily.dev/posts/the-architecture-of-local-first-web-development-smashing-magazine-fi6dhffcw) · Smashing Magazine · 6 upvotes · 1 comments - [Offline-first frontend apps in 2025: IndexedDB and SQLite in the browser and beyond](https://daily.dev/posts/offline-first-frontend-apps-in-2025-indexeddb-and-sqlite-in-the-browser-and-beyond-djyieqljy) · LogRocket · 1 upvotes · 0 comments - [Key Technical Design Decisions for Building an Educational App with LLMs](https://daily.dev/posts/key-technical-design-decisions-for-building-an-educational-app-with-llms-7dtdca1mw) · freeCodeCamp · 2 upvotes · 1 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#career](https://daily.dev/tags/career), [#architecture](https://daily.dev/tags/architecture), [#flutter](https://daily.dev/tags/flutter), [#sqlite](https://daily.dev/tags/sqlite), [#local-first](https://daily.dev/tags/local-first) [View this post on daily.dev](https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Architecture Decisions Behind Building a Simple Personal Software Tool","url":"https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4"},"datePublished":"2026-07-12T10:37:51.623Z","dateModified":"2026-09-13T20:03:36.377Z","description":"A backend engineer documents the architectural decisions behind building a local-first personal desktop/mobile app using Flutter and SQLite. The post walks...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/67f6d5449b4544c34b5a02c1f685ead8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/67f6d5449b4544c34b5a02c1f685ead8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DEV","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DEV","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/devto","url":"https://daily.dev/sources/devto"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":75},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"aws,career,architecture,flutter,sqlite,local-first","timeRequired":"PT13M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DEV","item":"https://daily.dev/sources/devto"},{"@type":"ListItem","position":3,"name":"Architecture Decisions Behind Building a Simple Personal Software Tool"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4","comment":[{"@type":"Comment","text":"Local-first Flutter + SQLite is a compelling fit—the cloud-as-courier sync model keeps the architecture refreshingly simple.","datePublished":"2026-07-14T01:55:51.366Z","url":"https://daily.dev/posts/piWLYEZW4#c-7MUCfB10W","author":{"@type":"Person","name":"Jenuel Oras Ganawed","url":"https://daily.dev/jenueldev","image":"https://media.daily.dev/image/upload/s--BadmiNyj--/f_auto/v1787625077/avatars/avatar_JJtZr4Sjm?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"Using cloud storage as a courier instead of a backend is a strong way to keep the local-first model honest. The tricky edge is Last-Write-Wins: clock skew and simultaneous edits can silently discard valid changes. Per-record versions, tombstones, and selective field-level merging would add resilience without turning the app into a distributed-systems project.","datePublished":"2026-07-15T01:50:24.853Z","url":"https://daily.dev/posts/piWLYEZW4#c-WylSlR0fX","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"nice read i really enjoyed 🔝","datePublished":"2026-07-21T14:26:19.901Z","url":"https://daily.dev/posts/piWLYEZW4#c-NJsiwrJKZ","author":{"@type":"Person","name":"David C.","url":"https://daily.dev/dcorto","image":"https://media.daily.dev/image/upload/s--EPnTZZFw--/f_auto/v1784418453/avatars/avatar_tT4BuvxaHeTxyE5fH41si?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/architecture-decisions-behind-building-a-simple-personal-software-tool-piwlyezw4#faq","mainEntity":[{"@type":"Question","name":"How can you sync data across devices in a local-first app without running a backend server?","acceptedAnswer":{"@type":"Answer","text":"Use cloud storage like iCloud or Google Drive purely as a file transport, not a database. Each device keeps its own local SQLite database, and the cloud only carries changes between them without validating or querying the data. Writes are debounced for 30-60 seconds before syncing, with a final sync on app close and a metadata check on startup to detect newer data. Anyone weighing local-first sync approaches can find grounded architecture discussions like this through daily.dev."}},{"@type":"Question","name":"What conflict resolution strategy works for syncing data between multiple devices without using CRDTs?","acceptedAnswer":{"@type":"Answer","text":"A last-write-wins approach using a last_modified_at timestamp on every record is a simpler alternative to CRDTs for low-conflict scenarios like a personal expense tracker. When two versions of a record meet, the newer timestamp wins. It isn't perfect for simultaneous edits, but the probability of that happening is low enough to skip the added complexity of CRDTs. Developers deciding between CRDTs and simpler timestamp-based sync can track these trade-offs via daily.dev."}},{"@type":"Question","name":"How do you handle database schema changes across app versions without breaking existing users' data?","acceptedAnswer":{"@type":"Answer","text":"On startup after an update, the app checks the local database's schema version and automatically runs migrations if it's outdated, applying incremental changes like adding columns or reshaping tables one version step at a time. This lets a database created under an old app version safely evolve to match the newest expected schema without requiring users to export and reimport their data. Developers building schema migration logic for local-first apps can follow similar architecture writeups on daily.dev."}}]} ```