Scrolled through first half of the page, learned that this is a web app that allows me to "see my money", that it's private, "makes things simple", and that it "revolutionizes financial management".
Is it really so hard to explain what your product is on the landing page? It's not just this app, it's most of the products promoted on HN. Also every other cloud app promises privacy until private equity shows up.
Yikes I hope lit.money doesn’t go the way of Mint: bought out by giant corporation, enshittified, neglected and finally subsumed/killed.
Personal finance apps need to be trustworthy and be around for the long haul - I need them to just hum along and not take me on a venture-backed roller coaster.
I have used lit.money, and I absolutely love it! Thank you, Mihir, for building something unique and user-friendly. I know the plans you have for this incredible piece of software are big, and I wish you nothing but the best.
Other's have already covered this so for you (OP) this will be redundant, but I do want to chime in regarding the general trend of apps/services everywhere (not just here on HN) focusing too much on the "Sell" of how their mcguffin will improve my life, but not actually saying what the heck their mcguffin actually is/does. To return to the post at hand, as an example, I'd change the byline uptop to say:
> An ethically designed financial management app to be the private and simple way to see your money, finally.
That maintains your pitch while also saying upfront and uptop in the first 6 words what it is/does.
Next, I'm not trying to be negative here, but rather acknowledge a very real problem that others have touched on and that anyone (myself included) launching any product will face in the current era:
Best Intentions != Best Practices. Security is hard. Earning trust is even harder. Especially when it comes to money. It's doubly difficult in early days as building out an app while maintaining security and respecting privacy is no minor task (even if "easy", it's still often tedious and easy to make mistakes), and in the context of finance/banking, there's unfortunately a large target on the app/services's proverbial back and impetus for users to have a far more critical and unforgiving eye given the potential fallout of someone leveraging or publishing an exploit.
There's also the ever looming potential of the original team selling the company/product/service to someone else (eg, Private Equity) who - despite claims to the contrary - rarely share the same ethos or respect for their newly acquired users as the founder/founding team does/did.
As to why people tend to be critical/suspicious: See another recent HN post "Everyone Knows your Location[0]" regarding all the practically systemic and endemic ways that applications/services expose/harvest data, and how difficult it can be to be aware of, mitigate and protect against these things. Exploiting user faith/data is unfortunately the norm now, not the exception, thus people's suspicions.
Wish you luck OP, because the market absolutely could use a privacy/user respecting app in this space.
Thanks for your time and feedback.
- Based on all this feedback, I am going to rework the website content and will focus on writing what it's actually doing.
- You are right, security and trust are ongoing things, and I will keep working on them.
Can you give the web app a try and share some feedback on it?
It's interesting to see cloud service after cloud service launch that promises "never to sell your data".
I'm working on a similar thing, except making sure we can actually live up to that promise: that means making the software entirely feasible to run on-prem (i.e. on your own computer), on your own cloud infrastructure, or provided by a third-party provider of your choice. (We chose AGPL3 to avoid the obvious problems with third party hosting trying to add features or change things and then locking you into their platform.)
Of course, this takes a bit more effort, and some things like Plaid are nearly impossible to use when self-hosted, but we've found some pretty good workarounds for that.
But "I'll never sell the data" is different from "this service will never sell the data". If you sell the service, will you put it in the contract that any subsequent owner can never monetise the data? Will you decline a sale if they decline? How will you justify that to the board? What if they fire you to push the sale through?
Etc etc. "We'll never sell your data" is just empty words to me, except in one case: if you designed a system that never has my data in the first place.
The challenge is after it grows/becomes more successful, something happens that you lose control of the company, or perhaps you take some investment money (which is completely reasonable to do) and then they want you to start changing how you do things. You might not even "sell" the data - you might be forced to give it away.
Is it really so hard to explain what your product is on the landing page? It's not just this app, it's most of the products promoted on HN. Also every other cloud app promises privacy until private equity shows up.
Currently my goal is to get feedback. Yours will be really helpful.
https://lunchmoney.app/
Meanwhile can you check lit.money and share some feedback?
It has demo account option so you can easily check it.
Personal finance apps need to be trustworthy and be around for the long haul - I need them to just hum along and not take me on a venture-backed roller coaster.
Right now my focus is just to talk to people and improve it.
Best luck
But you can mail me, we can plan something.
Other's have already covered this so for you (OP) this will be redundant, but I do want to chime in regarding the general trend of apps/services everywhere (not just here on HN) focusing too much on the "Sell" of how their mcguffin will improve my life, but not actually saying what the heck their mcguffin actually is/does. To return to the post at hand, as an example, I'd change the byline uptop to say:
> An ethically designed financial management app to be the private and simple way to see your money, finally.
That maintains your pitch while also saying upfront and uptop in the first 6 words what it is/does.
Next, I'm not trying to be negative here, but rather acknowledge a very real problem that others have touched on and that anyone (myself included) launching any product will face in the current era:
Best Intentions != Best Practices. Security is hard. Earning trust is even harder. Especially when it comes to money. It's doubly difficult in early days as building out an app while maintaining security and respecting privacy is no minor task (even if "easy", it's still often tedious and easy to make mistakes), and in the context of finance/banking, there's unfortunately a large target on the app/services's proverbial back and impetus for users to have a far more critical and unforgiving eye given the potential fallout of someone leveraging or publishing an exploit.
There's also the ever looming potential of the original team selling the company/product/service to someone else (eg, Private Equity) who - despite claims to the contrary - rarely share the same ethos or respect for their newly acquired users as the founder/founding team does/did.
As to why people tend to be critical/suspicious: See another recent HN post "Everyone Knows your Location[0]" regarding all the practically systemic and endemic ways that applications/services expose/harvest data, and how difficult it can be to be aware of, mitigate and protect against these things. Exploiting user faith/data is unfortunately the norm now, not the exception, thus people's suspicions.
Wish you luck OP, because the market absolutely could use a privacy/user respecting app in this space.
0: https://news.ycombinator.com/item?id=43716704
Can you give the web app a try and share some feedback on it?
I'm working on a similar thing, except making sure we can actually live up to that promise: that means making the software entirely feasible to run on-prem (i.e. on your own computer), on your own cloud infrastructure, or provided by a third-party provider of your choice. (We chose AGPL3 to avoid the obvious problems with third party hosting trying to add features or change things and then locking you into their platform.)
Of course, this takes a bit more effort, and some things like Plaid are nearly impossible to use when self-hosted, but we've found some pretty good workarounds for that.
Also will work on self hosting and offline support once product get mature.
But "I'll never sell the data" is different from "this service will never sell the data". If you sell the service, will you put it in the contract that any subsequent owner can never monetise the data? Will you decline a sale if they decline? How will you justify that to the board? What if they fire you to push the sale through?
Etc etc. "We'll never sell your data" is just empty words to me, except in one case: if you designed a system that never has my data in the first place.
The challenge is after it grows/becomes more successful, something happens that you lose control of the company, or perhaps you take some investment money (which is completely reasonable to do) and then they want you to start changing how you do things. You might not even "sell" the data - you might be forced to give it away.
Our biggest customer wants to pay us to cloud host it for them and manage the whole thing.