open-portfolio / flowworthapp Goto Github PK

Needed where:

• users who don't have Xcode installed, or are unfamiliar with its use
• users who cannot/don't use Mac App Store
• Mac App Store releases are delayed
• Binaries needed for both FlowAllocator and FlowWorth

Also, update docs to reflect availability.

Rather than a rough annualized percent (based on period), instead calculate a CAGR (compound annualized growth rate).

Applies to the delta views, including forecast.

Dietz-based performance not affected (at least yet).

Needed:

• for Homebrew-based installation of apps
• for users who don't/can't use Mac App Store
• where Mac App Store releases are delayed

Both FlowAllocator and FlowWorth should each have their own cask.

Also, update docs to reflect availability.

May be dependent on #3, a workflow to create binaries.

At present, both FlowAllocator and FlowWorth assume all accounts are in a common currency, where the currency symbol (and formatting method) is chosen from the locale.

Provide a way for the user to select an alternative currency which will be stored in the DisplaySettings of the document (allocatz/worth) file.

Implementation detail: the unused CurrencyCodePicker in FlowAllocatorApp could be used. Relocate it to FlowUI.

Additional implementation detail: on file load, or when user changes the explicit currency, see if it's possible to make an app-wide change to the locale in the environment to reflect the user's preference. Ideally, the formatters should automatically pick this up.

Presently uses customized version of 3rd party charting library that isn't being updated.

Currently only macOS is supported for the apps, but there's strong potential for supporting iPadOS/iOS.

There is a relatively small amount of platform-specific code, such as for file selection and saving, that would need equivalent support on iPadOS/iOS.

Once supported, the builds can be made available to users in the iPadOS/iOS App Store, much as the macOS ones are now.

Evaluate recent updates to SwiftUI capabilities to determine whether or not the current KeyWindow dependency is still needed.

If not needed, remove the dependency and make appropriate code changes.