3 ms·
>There is no "what if I accidentally clicked no but want to reverse that decision, where do I go" problem. Yes there is, you now can't find the setting, becaus
by rcxdude 2y ago
>There is no "what if I accidentally clicked no but want to reverse that decision, where do I go" problem.
Yes there is, you now can't find the setting, because it doesn't exist, and you need to wait for it to reappear based on some unknown trigger.
- bathtub365 2y agoThis means that there is actually likely MORE state tracking this than if it were a simple setting. You need to store not just the setting for this particular feature, but also potentially the last time they were asked or whatever else triggers them to get asked again. It’s either poor design, or explicitly designed to repeatedly push a feature on a user even if they don’t want it.