Firefly III: a personal finances manager
Go to file
2014-07-15 17:09:59 +02:00
app Removed my own validation source in favour of Ardent. 2014-07-15 17:09:59 +02:00
bootstrap Made big headway in preference management, accounts, importing stuff, etc. etc. 2014-07-06 15:18:11 +02:00
public Moved some JSON around. [skip-ci] 2014-07-15 07:08:13 +02:00
.coveralls.yml Some attempts at code coverage and coveralls support. 2014-07-02 23:12:31 +02:00
.gitattributes All initial git ignore files. 2014-06-28 09:41:25 +02:00
.gitignore Update ignore file. 2014-07-07 08:20:26 +02:00
.travis.yml Updated compeer for coveralls. 2014-07-02 23:16:31 +02:00
artisan Initial commit. 2014-06-28 09:41:44 +02:00
composer.json Removed my own validation source in favour of Ardent. 2014-07-15 17:09:59 +02:00
ide-helper.sh Updated various classes and tests. 2014-07-02 23:31:59 +02:00
phpunit.xml Fixed tests and added some more. 2014-07-08 21:35:14 +02:00
README.md Updated read me [skip-ci] 2014-07-15 11:02:11 +02:00
server.php Initial commit. 2014-06-28 09:41:44 +02:00

firefly-iii

Build Status Coverage Status Still maintained?

Latest Stable Version Total Downloads Latest Unstable Version License

Firefly Mark III is a new version of Firefly built upon best practices and lessons learned from building Firefly. It's Mark III since the original Firefly never made it outside of my laptop and Firefly II is live.

Changes

Firefly III will feature:

  • Double-entry bookkeeping system;
  • Better budgeting tools;
  • Better financial reporting;
  • More control over other resources outside of personal finance
    • Accounts shared with a partner (household accounts)
    • Debts
    • Credit cards
  • More robust code base (mainly for my own peace of mind);
  • More test-coverage (aka: actual test coverage);

More features

  • Firefly will be able to split transactions; a single purchase can be split in multiple entries, for more fine-grained control.
  • Firefly will be able to join transactions.
  • Transfers and transactions will be combined into one internal datatype which is more consistent with what you're actually doing: moving money from A to B. The fact that A or B or both are yours should not matter. And it will not, in the future.
  • The nesting of budgets, categories and beneficiaries will be removed.
  • Firefly will be able to automatically login a specified account. Although this is pretty unsafe, it removes the need for you to login to your own tool.

Not changed

  • Firefly will not encrypt the content of the (MySQL) tables. Old versions of Firefly had this capability but it sucks when searching, sorting and organizing entries.

Current state

I barely have the basics up and running and test coverage is doing very good. I have some good ideas about user configuration and preferences which was a huge pain in the butt with the previous Firefly.

Current problems include proper time-based navigation (how and when to switch to the next month, previous week, etc) and the best way to display your current financial state, which is something that still needs thinking.

The problem is that most peoples finances are very flexible and Firefly can be pretty static. For example, did you spend all your money? Or do you have money left? Good question: when your rent is due at the 1st of the month Firefly might think you've spent way too much. But marking it as some kind of "bill" will make Firefly ignore it, but it might make Firefly forget that you've got bills coming! So there's a lot to do, and a lot to fix.

If you have an idea, let me know!