3. If you have better things to do, than personal finance or planning, you don't need this service
4. documents = bills. I add an entry: electric bill - 100$, but the interface where I pay it keeps only my last 6 bills, not everything, so I want them stored automatically somewhere/
5. I don't need your dropbox/google info. You click a login button, redirect to oauth interface, login on the oauth server then come back to me with a token.
It's not shooting down, it's reality, it's the reason I posted this.
> Apologies I didn't phrase that right. I meant: What if I forget to pay my internet bill, then can't access my personal finance app to see if I can afford to pay my internet bill?
You go to a good friend who'll let you use his computer for 3 mins, check your finance: u have money? pay the ne; no money, ask him :P
The other solution would be to go to the ATM and check your balance :P
1. YNAB is over complicated (just mho), but still has stuccess.
2. Forecasting (more like planning): at this moment I have X in my account. I have a big event in about 90 days from now.
I want the app to "learn" from my past months transactions(expenses & income), create a spending pattern and give me some scenarios: the optimist, pessimist and the probable one.
Currently I am trying this in excel...but doesn't work as planned. I want the app to be able "think" in advance.
Eg. you set a goal: $3,000 cash in next 3 months. Then the app should do: check what you did in the past 3 months, check last year on this time if you have any insurance to cover (car, house...etc, yearly recurring transactions) and the result should be: well, you can't gather $3,000 because you might spend them on: X, Y, Z. If you eliminate one of them, you reach your goal. Some kind of rudimentary artificial intelligence.
3. thanks for OFX, QFX and QIF.
4. Honestly, I want to build something that matters. I think I can support these yearly costs, even with a donate button (no ads).
5. Everywhere the forecasting/planning feature is a paid one.
6. As I initially said, I am trying to plan it as anonymous as possible: the data will be tied to an oauth userID, nothing more.
At least they don't explode...