Currently, the NTP listens for ContentSuggestion changes until it gets the first non-empty result. AFAIK this is so that when you first open an NTP and we don't have snippets yet, we will display them once they come in from the network, which IMO makes sense, but I don't really know how that should interact with the "no cards" card.

Just refreshing the UI is a bit jarring.

I wonder whether we should introduce a "New content downloaded. <a>Show</a> <a>Disable syncing content suggestions</a>" feature to accomplish:

- access to content when it becomes available (without causing a surprise update to the UI).
- better transparency and control for network usage

The "Disable syncing content suggestions" feature would be wired to a sync setting (which technically isn't sync - but it makes more sense to communicate it in that context).

This jarring experience can be due to 1 or both of:
- you have no snippets in the local DB, which should not be too common: mostly first run experience (I assume users will not be heading straight below the fold in that case) or right after enabling the feature (signing in, etc.)
- The signin service is not properly initialized yet, so we don't have all the info about the sync state.

So it should be something that can really only be seen on cold starts.

We were also thinking about having some sort of spinner, or way to tell the user we're doing something in the background. The signin bit can take time and be noticeable even on N6.


> "Disable syncing content suggestions"
Is that to disable the Content Suggestions features entirely?