New app: ISA Eye (me.dylmye.isa)

Abstract for new app inclusion

Please introduce the functions and usage of your app in summary, and also attach some screenshots.

ISA Eye helps British savers keep track of their tax-free savings accounts (better known as ISAs) across banks in a privacy-first and easy-to-understand way. ISAs offer tax-free interest and gains benefits but come attached with complex and everychanging rules, allowances and types of accounts. The aim of ISA Eye is to make it easy and fun to save, and to make the most of what is provided, through goals, simple visualisations and guides on making the most out of ISAs.

Phone Tablet Desktop
Mobile educational content Tablet insights Desktop insights

Please elaborate why you wrote this app. Please highlight the unique functions it provides over other similar apps in F-Droid.

Many ISA provider's apps provide a way to keep track of the allowance of the accounts savers hold with the provider, but not for their other accounts. This is important because an individual has an annual allowance shared by all of their accounts. Many people hold their stocks and shares with specialised providers, while holding cash or accounts for their children (JISAs) with other providers, and they have no clear way to keep track of everything.

No other app has the goal functionality, the widgets or the educational material that ISA Eye does. The app is offline-first and is designed for all screen sizes, from small mobiles to desktop displays.

Checklist

Policy

  • The app complies with the inclusion policy. Pay special attention to Quality point 6.
  • The original app author has been notified (and does not oppose the inclusion). If you are not the author, please paste the link of the reply from the author. I am the author
  • The upstream app source code repo contains the app metadata in a Fastlane or Triple-T folder structure. The summary and description must be included and images, icon, and changelog should also be provided for better user experience. The en-US locale must be included.

Docs

Merge Request Setup

Metadata

  • Metadata must be put in metadata/<applicationId>.yml.
  • Metadata must be a valid YAML file.
  • Metadata must use LF as line ending.
  • Don't add summary/description/changelog/images or anything that should be provided in upstream repo. Please check the Changes tab to make sure there is no other unrelated files added in the MR.
  • Releases are tagged and auto update is enabled unless there is a special reason.
  • There is an issue tracker and contact info of the author so that we can report bugs and contact the author.
  • An AuthorName must be added. It doesn't need to be the real name.
  • External repos are added as git submodules instead of srclibs. You can update git submodules without opening an MR in this repo and the submodule is covered by our scanner. (n/a)
  • Enable Reproducible Builds. We'll use your signature for improved security/reliability, also allowing users to switch between different channels. Do note that if you don't enable reproducible build then the apk will be signed with our key so you can't enable it later. If you can't enable this, please add the reasons here.
  • Setup abi split if the APK is large and the splitted ones can be much smaller. (n/a - small app, will re-consider if it grows)
  • Only the latest versions should be kept in the metadata before it's merged. If you update the metadata, please replace the old versions with the new ones.
  • Don't add any disabled versions in the metadata.
  • The commit field should be the full hash. Please don't use tag or branch in commit.

Pipeline

  • All pipelines should pass.
  • All warnings and errors in the Reports tab should be fixed or explained.
  • F-Droid CI runners are under GitLab's FOSS program, so there's no need for you to pay for any CI time. If Gitlab starts asking for phone numbers or credit cards don't submit anything, just leave a note in the MR so we know we need to trigger the CI.

Thank you :)


Merge request reports

Loading
Loading