You give the information on where the setting is, then have an “enable now” button that calls the exact same function as clicking the toggle on the other page does. Having multiple ways to do the same thing isn’t unusual and is trivial with properly designed code.
No. It isn’t. The setting in the modal should act as a convenience component that doesn’t have any of its own data. It only modifies the value in the original source of truth. Once the modal has been used, it should never pop up again, as the assumption will be if the user has interacted with the modal, they are now aware of the setting and can set it themselves from the original source of truth. Unless of course you consider any feature speghettification
Thats how you get spaghetti code.
It’s really not that complicated.
You give the information on where the setting is, then have an “enable now” button that calls the exact same function as clicking the toggle on the other page does. Having multiple ways to do the same thing isn’t unusual and is trivial with properly designed code.
No. It isn’t. The setting in the modal should act as a convenience component that doesn’t have any of its own data. It only modifies the value in the original source of truth. Once the modal has been used, it should never pop up again, as the assumption will be if the user has interacted with the modal, they are now aware of the setting and can set it themselves from the original source of truth. Unless of course you consider any feature speghettification