Make Simplifi's "automatic" actions subject to user control in Settings

DryHeat

Several issues raised about different parts of Simplifi relate to one particular design principle. Namely, that a feature can be so useful that "Everyone Will Want This" (EWWT for short).

Based on EWWT, Simplifi changes the Payee to a "Quicken name" even for users who don't want that done. Simplifi supplies a Category for downloaded transactions even if a user would prefer to do it manually. Simplifi matches Transfers without giving the user a chance to say if the match is correct. Simplifi excludes certain transactions from the Spending Plan or Reports and won't let the user change that. (I'm sure there are other examples I'm not thinking of at the moment.)

I'm not saying that these automatic actions are not useful. Some of them I like very much. But they are not useful for everyone, or for every account. So I propose the following:

Make Simplifi's automatic actions optional by adding an "Automatic actions" subpage to the Settings page and allowing users to turn each such feature On or Off individually.

The default setting for each could be On, because probably EWWT. But the option to turn features Off would at least stem the flow of complaints from users for whom the automatic action just doesn't work.

EL1234

I think this is a great idea! Upvoted.

Jenny T

I'm supporting this mainly because I've experienced negative impacts from several of the example use cases mentioned in the original post and see this as a viable workaround solution. While it offers users flexibility and could achieve the desired outcomes, it might lead to more manual input than desired. Some examples (like the original payee name) function as simple on/off switches and wouldn't add extra effort for the user. However, others (like default categories and transfer matching) could require a lot more manual "hand-holding" within the system. While it's arguable that this would just shift which tasks I need to manage manually, I would only enable them because I wasn't getting the expected or desired results from the automation. I wouldn't want this feature to replace automation improvements that truly simplify the user experience. In other words, if users are disabling the EWWT features, that would be a sign that those features likely need fixed or improved.

DryHeat

@Jenny T

I wouldn't want this feature to replace automation improvements that truly simplify the user experience

I agree. That's why I suggested that users be able to "turn each such feature On or Off individually."

[EDIT] I don't want to glaze over your point about different features being easier or harder to turn off. I think turning off default categorization is not too hard … just mark all new transactions as "Uncategorized" or "Pending Categorization" and let the user deal with it. Turning off automatic linking of transfers (but retaining the ability to manually link transfers) would require some better plumbing than we currently have.

if users are disabling the EWWT features, that would be a sign that those features likely need fixed or improved.

That's a good point. It's not uncommon for software to provide developers with usage metrics on various features. (Low usage is often the reason given for discontinuing a particular feature.) Similar data from EWWT settings would be good feedback for developers on how well different features are being received.

mluhring

I would prefer not to have Simplfi try to categrize my transactions. If they are uncategorized then it gives me the oppotunity to make sure its put in the right place. Many times Simplifi is just plain wrong and it's a pain to have to look at categorized transactions to see if they are in fact correct. I would think the default for this would be OFF.