Every major release version bump ( v1.x to v2.0.0 ) feels like a victory lap.
You tag the release commit in Git, bump versionCode in Gradle, generate signed Android App Bundles, and update release notes.
What release notes never show, however, is the graveyard of rejected ideas .
Software architecture is not defined by what you choose to build; it is defined by what you deliberately choose not to build. For every feature that ships in a production release, a dozen tempting shortcuts, popular third-party SDKs, and user feature requests had to be rejected to protect the integrity of the application.
Here is an honest retrospective on the hardest technical trade-offs we made while releasing FinLedger v2.0.0 ( commit 44048d4 ).
The Feature Prioritization Matrix
During the v2.0.0 release cycle, every proposed capability was evaluated against our core manifesto: Privacy, Accounting Accuracy, and Offline Resilience .
quadrantChart title FinLedger v2.0.0 Prioritization Matrix x-axis Low Technical Debt -->…