Skip to content

FinTrack v1.2

Choose a tag to compare

@Agumuzi Agumuzi released this 23 Oct 05:28
· 139 commits to main since this release
1084dd5

FinTrack v1.2 · Performance, Usability & Reliability Improvements

Features & Improvements

  • Reduced redundant calculations in category management, the overview dashboard, and budget summaries, improving responsiveness when working with larger transaction datasets.
  • Standardized transaction filters using category icons and names. Category options now adapt to the selected income or expense scope. Improved transaction table column widths, amount alignment, and pagination controls.
  • Improved date selection with consistent keyboard navigation. Financial goals now support flexible deadlines: no date, year only, year and month, or a complete date. Target dates and completion status are managed independently.
  • Standardized feedback for imports, exports, backups, and restoration, with clear success, informational, and error messages. Result dialogs can be dismissed using buttons, Esc, or by clicking outside.
  • Simplified the first-launch experience by opening a built-in empty ledger. Existing installations retain their application identity and ledger storage locations.

Testing & Verification

Isolated Release Regression Tests

  • Model tests: 214 passed, 13 conditionally skipped, out of 227 test methods.
  • Critical UI tests: 47 passed.
  • Additional performance tests: 5 passed.
  • Import and extended UI tests: 2 passed.
  • Build verification: Universal build and code-signing checks passed.

All tests were conducted against the same frozen source baseline.

Conditionally skipped tests included explicit network access, real API credentials, post-release verification probes, and fixture-generation utilities.

No real financial ledger was used as test data.

Known Limitations

  • Some page transitions may still experience brief pauses. This release does not claim that every interaction completes within 250 milliseconds.
  • Existing loan net-worth calculations continue to follow their established scheduled-payment accounting rules.
  • Legacy CSV files without unique record identifiers retain their previous reimport behavior. Importing the same file again may create duplicate transactions.
  • Category merging and ledger restoration involve multiple local storage components. Consistency safeguards remain limited if these operations are interrupted unexpectedly. Avoid force-quitting FinTrack until the operation finishes.
  • Comprehensive VoiceOver accessibility testing, physical Intel and macOS 15 device testing, and extended use with real financial data remain outside the completed verification scope.

Compatibility & Data Safety

  • Requirements: macOS 15.0 or later.
  • Architecture: Universal (Apple Silicon / Intel).
  • Signing: Ad-hoc signed; not notarized by Apple.
  • Data safety: Create a full backup before upgrading.
  • Downgrade compatibility: Older versions are not guaranteed to read ledgers modified by newer versions. If you need to downgrade, restore a backup created before upgrading using the corresponding application version.
  • API keys: Remain stored in the macOS Keychain and are not transferred through ledger backups.

Download & Installation

The release package and corresponding SHA256.txt verification file are available in the attachments below.

Users running v1.1 can check for, download, and verify this release through the official signed in-app update feed. Actual installation requires user confirmation.

If the in-app download times out:

  1. Download the ZIP archive and SHA256.txt directly from this GitHub Release.
  2. Verify the downloaded archive against the provided checksum.
  3. Quit FinTrack and manually replace the existing application.
  4. Relaunch FinTrack and verify your financial records.

During isolated testing, the older application successfully detected v1.2 but encountered download timeouts on two attempts. Direct downloads of the public ZIP archive, SHA256 verification, and signed manifest verification were independently successful.

Actual installation, restart rollback, and verification against real financial records remain the user's responsibility.