I have a web application in which a user can create filters for a news feed.
When the user creates or modifies his filters, everything is saved to the server through API requests (without the need for an explicit 'Save' button).
Requests are throttled and fire when there have been no more actions for 1000ms.
Should I still display a notification when a save request is fired, or keep everything in the background?
My thinking is that it may be annoying for someone who spends a lot of time configuring his filters to see 'filters saved' popping up all the time...
I read in the Apple UX guidelines :
Support Auto Save and Versions, if appropriate. Users expect their content to be saved continuously and mostly without their intervention.
Does this apply to web products, and do all people expect this behaviour or only apple users?