And why should the user know what's going on replication? What is it you?
In my opinion this is extra functionality, which will overload the Notes client as well as the need to constantly send requests to the server to obtain information about the beginning / end of replication.

@1: The Notes client is already aware that replication (between local and the server) is taking place. It is more like the replicator page integrated in the workspace.

It will make the user more aware of the synchronization process.

It is known only for the current client, that is when the client starts the replication manually. When he does, the move of replication and so visible in the progress bar, so it is also not necessary.
Moreover, the user most of my time working in the databases, rather than considering how beautiful glitter icons...

@3 sure current client only and only of value when scheduled replication or replication on start-up/shutdown takes place.

As I said the added value is very little, but if the workplace is to be re-designed to make it an easier entry point to applications, then in-context progress bars would be nice.

E.g. I dislike the replica stub icons when you create a new replica in the current workspace and that you have to open the progress pane to see if a new copy is completed.

@4: Replicator with open automatically, and you can watch the proceedings.
The whole thing only in the appearance of icons? Maybe it's good, but I believe in LND is more pressing ideas that are close to the critical...

I like the idea, kind of like the "workspace" on the iPhone or iPad when you're updating multiple apps from the app store.

uhm something like this:

{ Link }

Patrick,
and this is all on one icon of the database? :)))
uhm knowingly.

This seems like a major performance issue for workspaces that have many icons. Also, what happens with stacked icons when the local replica is not on top, but inside the stack, the user would not see it and then wonder why they are not receiving data for one application....they would then call the Help Desk and state that "Application<x> is not receiving data," or that "Notes is broken." Also, if you utilize multiple tabs, you will need to change tabs and scroll to see everything...that can waste time.

The replicator page is the best place for this, and will show all the icons with local replicas in a nice concise format.

Nice idea in theory, but in implementation it breaks-down. I will demote as a result...just want to be cordial and provide my perspective with my vote.