I’ve been building a personal finance app that runs fully in the browser (using the automerge crdt and sqlite) for over a year now at https://tender.run.
Recently I’ve been taking more of being able to flexibly run sql against this data, and this past week I’ve been working with d3 to make fancy sankey graphs to show income/expense flows. Quick preview here: https://demo.tender.run/reports/sankey
That looks quite nice and the local first approach was a good idea.
I wonder how it will compare to ActualBudget and its pre/post rules and the GoCardless account data importer.
Side note: The first col of all text overlaps with some other text on mobile devices (both landscape and portrait mode) and thus is unreadable.
Also the inbox didn't work an I can't look at the inbox as the filters stay open.
Edit just noticed that this is a SaaS. If it would be a single payment for a license or sponsored FOSS, I believe it could work. The current way, I would assume that it will meet the fate of all the other apps in this non-market. Good luck though!
Pretty interesting take on a finance app! I like the inbox and filters on transactions. I'm not sure I understand the benefit of storing it all in the browser though. Does the data just live in the browser? Does anything store on a server?
Originally this was a privacy angle - the data is primarily stored on your device, with backend storage that’s treated like backup and sync only. I had plans for e2ee that built on this but it didn’t turn out to be a big differentiating factor.
Working in local-first turns out to be really nice for making the app feel super snappy. The responsiveness you see in the demo is the performance you can expect in day to day usage.
Recently I’ve been taking more of being able to flexibly run sql against this data, and this past week I’ve been working with d3 to make fancy sankey graphs to show income/expense flows. Quick preview here: https://demo.tender.run/reports/sankey