Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/jbolda/finatr

helping you analyze your future cash flows
https://github.com/jbolda/finatr

finance finance-management hacktoberfest personal-finance

Last synced: 19 days ago
JSON representation

helping you analyze your future cash flows

Awesome Lists containing this project

README

        

# finatr
_helping you analyze your future cash flows_

[![Deploys By Netlify](https://www.netlify.com/img/global/badges/netlify-light.svg)](https://www.netlify.com)

[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v1.4%20adopted-ff69b4.svg)](code-of-conduct.md)
[![Discord](https://img.shields.io/discord/711689469606232184?color=7289da&label=chat%20on%20discord&style=plastic)](https://discord.gg/sPazfrt)

Visit the production site at [www.finatr.com](https://www.finatr.com). Visit the upcoming version of the site at [next.finatr.com](https://next.finatr.com).

## Usage
Most apps track your historical information and help you set up a budget. Argueably, budgets don't work for everyone. Even if you maintain a budget, it is still of great value to look to the future. The first version focuses on the near future checking that the inflows and outflows in your accounts are satisfactory. Essentially, will my accounts stay above zero with the planned expenditures. Tied into that, we need to understand a deal with variable debt payments (see credit cards) as future flows are more involved then a simple monthly payment you might see with a mortgage or a student loan payment. The next step from this is returning information regarding these flows such as a daily income and daily expenses. This type of information can be built upon going forward to forecast considerations like FI(RE).

## Help Out
We are working on a big styling update to move to from bulma to a css-in-js solution. This is happening on the `css-in-js` branch. All code PRs (Pull Request aka code changes) should target the `next` branch unless it is contributing to or greatly affected by the switch to `css-in-js`. After that work is complete, `css-in-js` will be merged into `next` and eventually `next` into `master` when everything on [Stable Release](https://github.com/jbolda/finatr/projects/1) is complete.

See the [Stable Release](https://github.com/jbolda/finatr/projects/1) project to track progress or find place to begin helping out. Have something you want to request or help out with that isn't on the list? Feel free to open up a new issue to open the discussion.

## Contributor Covenant
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.