iccananea
Joined 4 years ago
Joined 4 years ago
Regarding the one-time fee and subscription, 100% agree. I delayed adding account sync because of the monthly / yearly costs. And also, because with the model of recuring rules looking into the future, I tend to use the app on a daily basis to correct things (payment is scheduled on 16th but is cleared on 17th so I need to update it).
When I add bank account sync, I'll have to think how to charge it. I still don't want to have a subscription for it, so need to think about it.
Finally, I don't do client-side encryption. There is encryption in transit (https / tls) and at rest.
I can't open any database without the user's password, so even if someone were able to exfiltrate the user databases, they still would need to know the encryption key used to read the data.
I haven't done it at first because
(1) they all have monthly / yearly costs and I wanted a flat fee;
(2) I can't update the account without the user having logged in because of how the encryption works.
Personally, I don't like subscription-based apps so didn't want to create yet another one.
And I built this around my personal needs so I plan to support it indefinitely.
Regarding long term improvements, there is a number of paying users that once I achieve, any new users are basically profit.
The service was built to be cheap to run and maintain so I could charge a one time fee.
My inspiration for trackm was actually moneywell.app which i bought a license for in 2009.
The "look X years" into the future feature was pulled from it.
I no longer have a mac or ios device, so built trackm to fill the void.
My cousin has a large collection of CDs and the player is being built around his listening habits (listening to disk from start to finsh at home, individual tracks when on the go).
So project Scorpions was born :)