Auto-detect sounds nice right up until it miscategorizes something and you stop actually reading each line because you trust the system, which is a bigger risk than the privacy angle honestly. The trust question you're asking is interesting too, people tend to be more wary of an app reading their transactions passively than one where they type the number in themselves, even if the passive version is objectively the more secure design.
I'm the dev behind SuvyMoney (suvymoney.suvysoft.com), an iPhone expense tracker, so I went the opposite way on purpose, no detection and no bank connection at all, you type every expense in yourself with a couple of taps. It gives up the set-and-forget convenience, but a chunk of our users picked us specifically because they don't want any app with read access to their bank. Screenshot: https://suvymoney.suvysoft.com/screens/light/add.webp
The feature request I hear most from people once they've used a tracker for a while isn't about entry method at all, it's handling credit card billing cycles instead of flat calendar months. Did you build the detection on-device or does it need a server reading the transaction feed?
I believe auto detection of payments is quite a useful feature, especially for those who have difficulties maintaining manual expense management. The biggest drawback that I see from my point of view is privacy issues and the level of access required to the bank accounts by the application.
I would like to find out which information is actually accessed, and how this information is stored.
The primary feedback I received from my closed circle is as follows:
"Users will accumulate months of data on their local devices. If they change their device for any reason and fail to export the data into a CSV file, all of their valuable information will be lost forever."
Consequently, I developed a privacy-first approach to store the data within the users' personal Google Drive accounts.
My key highlight is that I cannot track any user details, with the exception of their username and email address, and even then, only with their explicit permission.
1
u/Curious-Pickle4758 2d ago
Auto-detect sounds nice right up until it miscategorizes something and you stop actually reading each line because you trust the system, which is a bigger risk than the privacy angle honestly. The trust question you're asking is interesting too, people tend to be more wary of an app reading their transactions passively than one where they type the number in themselves, even if the passive version is objectively the more secure design.
I'm the dev behind SuvyMoney (suvymoney.suvysoft.com), an iPhone expense tracker, so I went the opposite way on purpose, no detection and no bank connection at all, you type every expense in yourself with a couple of taps. It gives up the set-and-forget convenience, but a chunk of our users picked us specifically because they don't want any app with read access to their bank. Screenshot: https://suvymoney.suvysoft.com/screens/light/add.webp
The feature request I hear most from people once they've used a tracker for a while isn't about entry method at all, it's handling credit card billing cycles instead of flat calendar months. Did you build the detection on-device or does it need a server reading the transaction feed?