// the find
dreautall/waterfly-iii
Unofficial Android App for Firefly III, a free and open source personal finance manager.
Waterfly III is a Flutter-based Android companion app for Firefly III, a self-hosted personal finance manager. It covers the core on-the-go use cases — logging transactions, checking balances, monitoring budgets and bills — without trying to replicate the full Firefly III web UI. This is the app you install when you've already committed to the Firefly III stack and want a decent mobile front-end for it.
1. Notification listener for pre-filling transactions from Google Pay or bank apps is genuinely useful — it's the kind of friction-remover that determines whether you actually log expenses consistently. 2. No trackers, minimal dependencies — the privacy stance is real, not just marketing copy; the network security config and no-analytics approach are visible in the repo structure. 3. Active maintenance with a proper release pipeline (Fastlane, CI/CD, Dependabot), 20+ languages via Crowdin, and F-Droid availability — this isn't a weekend project that got abandoned. 4. Material 3 throughout with dynamic color support; the UI actually looks like it belongs on a modern Android device rather than being a web wrapper.
1. Android-only despite being Flutter — the iOS folder exists but it's a shell, and the README makes no mention of an iOS build being available or planned. If you're cross-platform this doesn't help you. 2. Companion-only by design: no rule management, no report generation, no recurring transaction setup. Acceptable if you use the web UI for setup, annoying if you want to do anything beyond day-to-day logging without reaching for a browser. 3. No offline mode or local caching — if your self-hosted Firefly III instance is unreachable (travel, server maintenance), the app is dead weight. For a personal finance app this is a real gap. 4. Single-maintainer project with 58 forks and no documented contributor path beyond translation — bus factor is one, and given it's tracking your financial data, that's worth factoring into your dependency decision.