Sossoldi review: local net worth tracking across Flutter platforms

Why Sossoldi replaces a net worth spreadsheet

Sossoldi addresses people who want a clearer view of their finances without maintaining a spreadsheet by hand. Its origin is specific: the project began as a mobile and desktop replacement for Mr. Rip's Google Sheets net worth tracker. The intended audience includes users who do not feel comfortable creating formulas or maintaining an Excel workbook, as well as people who want expenses, bank balances, and investments visible in one application.

The core problem is record keeping rather than trading. Sossoldi is intended to answer how much someone owns, what money has moved through their accounts, where spending went, and how those records affect net worth. The README also identifies investors as a possible audience, listing stocks, bonds, crypto, and private equity among the asset classes that the project wants to support.

That distinction matters. Sossoldi is not presented as a brokerage, payment service, or bank. It is a personal finance record and tracking application. Automatic bank connectivity appears on the desired-feature list through Open Banking PSD2 support, but that does not mean Sossoldi currently performs automatic account aggregation. The documented Phase 1 instead calls for manually tracked bank account balances without an API.

Flutter delivery across mobile and desktop platforms

Sossoldi uses Flutter so that the same codebase can target Android, iOS, Windows, macOS, and Linux. The repository layout supports that claim because it contains separate directories named `android/`, `ios/`, `linux/`, `macos/`, and `windows/`, along with a shared `lib/` directory and Flutter project metadata such as `.metadata`, `pubspec.yaml`, and `analysis_options.yaml`.

The app is intended to run as both a mobile and desktop application. The README provides App Store, Google Play, and F-Droid links, while its technical documentation and platform directories cover a wider set of targets. This makes Flutter a practical choice for a small open source project that needs a shared presentation and application layer rather than separate native implementations. The repository also includes a `test/` directory, although the README does not describe test commands or coverage.

The repository's `docs/` directory contains the published setup and contribution guides. Based on the listed entry points, contributors are expected to work through the Flutter project rather than treat Sossoldi as a hosted web service. The documented architecture is therefore centered on a locally built application, not on a server-backed account system.

Installing Sossoldi and completing a first record entry

The README does not provide command-line installation steps or list exact Dart, Flutter, and `fvm` versions in the text available to the reader. It directs users to the App Store, Google Play, or F-Droid for packaged builds. Flutter developers are also directed to the project setup guide for local development, and the repository contains an `.fvmrc` file. Since no exact setup command or version is stated in the README, none should be inferred.

For a first real use, the documentation supports this sequence:

1. Obtain Sossoldi from the App Store, Google Play, or F-Droid. 2. Complete the basic onboarding described for Phase 1. 3. Enter income through the income tracker. 4. Record expenses, including recurrent expenses where supported by the current build. 5. Add a bank account and maintain its balance manually. 6. Open the Dashboard and basic statistics to review the recorded activity.

The project states that Phase 1 includes a Dashboard, Movements page, basic settings, and basic onboarding. However, the README does not provide screenshots with readable field labels, a sample data set, or a step-by-step walkthrough for each screen. That makes the setup guide the appropriate source for exact build instructions. The README also says that a stable release was being worked on, despite the repository listing `v1.0.0` as a recent release. It does not explain whether every Phase 1 item was complete in that release, so users should verify the screens present in the downloaded build rather than infer completion from the version number.

Local storage and the boundary of Phase 1

Local-only data storage is the defining product choice in Phase 1. The desired-feature list says that all data will be stored locally with an option to share it across platforms, while the Phase 1 definition narrows that commitment to data stored only locally. This reduces the need for a hosted account and keeps the early product centered on device-held financial records.

The mechanism behind the storage layer is not documented. Sossoldi's public documentation does not identify a database package, file format, encryption mechanism, backup process, conflict resolution method, or schema migration policy. There is also no documented account recovery procedure. Those omissions matter for personal finance software because local storage can simplify deployment while transferring the responsibility for backups, device loss, and database upgrades to the user or operating system.

Import and export data are listed as desired features, but the README does not say whether they are implemented in `v1.0.0`. The same distinction applies to cross-platform sharing. It would be unsafe to assume that a record entered on one device automatically appears on another. An adoption decision should therefore be based on the export, import, backup, and recovery behavior of the actual release, not merely on the local-first description.

Unfinished finance features and realistic limits

The largest limitation is the gap between the intended product and the documented Phase 1. Expenses, income, manual account balances, basic statistics, and local storage form the stated first release scope. Taxes, multiple currencies, detailed reports, investment categories, and automatic PSD2 bank connections appear under features the project wants to implement. The README does not say that these items are available in the current stable application.

Even within the investment idea, the documentation does not specify quote sources, pricing updates, transaction types, cost-basis accounting, dividends, or valuation rules. That makes any investment-related evaluation premature. A user who expects portfolio marks to update from market data is looking for a different kind of tool from the documented manual balance model.

Sossoldi is also the wrong choice for users who require server-side collaboration, automatic synchronization, or dependable institutional account aggregation based on the available documentation. There is no documented team model, hosted backup service, or confirmed PSD2 implementation. The app is better suited to an individual who accepts local records and enters balances directly.

How Sossoldi differs from spreadsheets and bank aggregators

A spreadsheet can support formulas, custom reporting, historical analysis, and unusual account structures, but it requires the owner to design and maintain those calculations. Sossoldi aims to replace that work with predefined screens for onboarding, movements, accounts, and net worth tracking. The practical difference is therefore not richer financial logic; it is a finance-specific workflow on mobile and desktop platforms.

A bank aggregator takes a different approach. It connects to financial institutions, imports balances and transactions, and reduces manual entry. The automatic import and Open Banking PSD2 connection in Sossoldi are listed as desired features, while Phase 1 explicitly uses account balances without an API. Compared with an aggregator, the documented Sossoldi path is local and manual. It may suit someone who does not want to grant bank access, but users should not choose it expecting current balances to arrive automatically.

Sossoldi also sits between a static net worth sheet and a full accounting package. It targets visible wealth and spending history, but the README does not claim double-entry bookkeeping, reconciliation workflows, tax calculations, or configurable financial reports. That narrower focus can be an advantage for a simple personal dashboard, while making it insufficient for accounting or tax work.

Sossoldi release activity, contribution scope, and MIT terms

The repository is not archived, and its last push was on 2026-10-15. Recent releases listed for the project are `v1.0.0` on 2026-08-20, `v0.3.2` on 2026-02-21, and `v0.2.2` on 2025-12-04. This shows recent repository activity and a move from version `0.2.2` to `v1.0.0`, but it does not by itself establish feature completeness or compatibility with every listed platform.

The README invites contributions and points new contributors to the issue tracker, Discord, setup guide, pull request guide, design file, UX research, and information architecture. The repository includes Android, Apple, desktop, web, test, and documentation directories, so contributors may encounter several platform-specific areas. The documentation does not state the supported Flutter version, dependency upgrade cadence, database migration policy, or long-term support period for platform releases.

Sossoldi is distributed under the MIT License. That permits broad use, modification, distribution, and sublicensing subject to the license conditions, including retention of copyright and license notices. It is not evidence that hosted financial data collection is available, since the documented storage direction is local. Any redistribution should preserve the required MIT notice; this is a statement about repository terms, not legal advice.

Editorial conclusion

Individuals who want a mobile and desktop net worth record and accept manual account updates should evaluate Sossoldi. Users who need bank aggregation, confirmed investment pricing, synchronization, or tax and accounting functions should choose a different tool. Verify the downloaded release's onboarding, local backup behavior, import and export support, and platform-specific stability first, because the README still distinguishes Phase 1 from desired features.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. RIP-Comm/sossoldi on GitHub