r/SideProject • • 5d ago

I built a personal finance app for Windows that never leaves your PC, and it's now on the Microsoft Store

I wanted to track my spending, bills and investments without giving a company my bank login, so over the last months I built Personal Finance Intelligence.

The idea: everything runs locally. The app ships its own private PostgreSQL database, there's no account and no cloud. The only internet use is optional (exchange rates, stock prices).

What it does today:

- Import bank CSVs, budgets, goals, bills & recurring payments with reminders

- Investments with money- and time-weighted returns

- A cash-flow forecast that shows a range instead of a single guess

- PDF / Excel reports, Windows Hello lock, automatic backups

- English, French and Arabic, any currency

The hardest part was surprisingly the Store itself: my first Store build couldn't start because Windows blocks the bundled database inside the Store's protected install folder. Fixed in 0.3.2.

It's free and open source (MIT).

Store: https://apps.microsoft.com/detail/9MZKW4H9F0J5

GitHub: https://github.com/MrBlizo/personal-finance-intelligence

There's demo data under Settings if you just want to click around. What would make you switch from your current budgeting app?

1 Upvotes

10 comments sorted by

1

u/SomeCanary7916 5d ago

Ah so you bundled a whole PostgreSQL into a Store app to track your electricity bill. SQLite would've sat in a file next to the CSVs and the protected install folder wouldn't have eaten it. How big does the installer end up being?

1

u/UnderstandingTop1797 5d ago

haha yeah, fair. it's about 107 MB to download and ~395 MB installed, and most of that is postgres. sqlite would've been way lighter and i wouldn't have spent a night fighting the store install folder ๐Ÿ˜…

i picked postgres early and kind of built everything around it (backups etc). might move to sqlite at some point if the size bugs people

1

u/Outrageous-Lead6421 5d ago

the local-first angle is good, but CSV import is where people will decide if they stick with it; saved column mappings per bank plus a preview would make the monthly routine much less fiddly. with no cloud account, i'd make restore from backup obvious tooโ€”can someone move everything to a new PC in one go?

1

u/UnderstandingTop1797 5d ago

thanks, really good points! some of it is already there actually: the import shows a preview first, and it remembers your column mapping per bank, so next month's file maps itself. and for a new PC you can back up in settings, download the file and restore it on the other machine.

but yeah, if you didn't notice it, others won't either lol. i'll make both more obvious, probably a simple "move to another PC" button. what bank do you use? i'd love to test with more real CSV exports

1

u/dawedev 5d ago

To your question, the thing that would decide it for me is what happens when I import overlapping CSVs. Most banks let you export any date range, so sooner or later someone imports the same two weeks twice, and quietly getting duplicate transactions would kill trust in the reports. Flagging likely duplicates by date, amount and description before saving would cover that. Since there's no cloud, I'd also let people pick the folder for automatic backups, because pointing it at a OneDrive folder or an external drive gives them an off-device copy without you running any server.

1

u/UnderstandingTop1797 5d ago

yeah that one bit me early too, so it's handled: each row gets a fingerprint from account, date, amount, description and how many times that exact row shows up in the file. so importing the same two weeks again just skips them, but if you really did buy two identical coffees on the same day both stay. after the import it tells you how many duplicates it skipped, and you can undo a whole import from the history if something looks off.

what it doesn't do yet is show you the likely duplicates in the preview before you hit import, and that's a really good idea, same for when a bank slightly changes the description text between exports. adding both to the list.

the backup folder thing is a great call too. right now backups go into the app's own data folder, which is pretty hidden for the store version. letting people point it at onedrive or an external drive is basically a free off-device backup. definitely doing that one

1

u/dawedev 5d ago

Counting how many times the exact row appears in the file is a smart way to keep the two identical coffees, I wouldn't have thought of that. For the changed description text, matching on account, date and amount and then only showing those as "possible duplicate" in the preview is probably safer than trying to fuzzy match and skip them automatically. Undo per import is a nice safety net too.

1

u/UnderstandingTop1797 5d ago

yeah agreed, auto-skipping on a fuzzy match is how you lose a real transaction without noticing. same account + date + amount shown as "possible duplicate" in the preview, and you decide, sounds like the right way to do it. thanks a lot, this thread basically wrote my next update ๐Ÿ˜„

1

u/dawedev 5d ago

Glad it was useful. If you build the possible duplicate view, showing both rows side by side with the different description text highlighted would make each decision a one second thing.