ConnectivityService

[HenrikJannsen]

ConnectivityService.ConnectivityStatus is used for the dot at the user icon. This differs from the behavior in Bisq 2 where it displays the user activity. We should not overload this some different message as it would confuse users who come from Bisq 2 (as it confused myself).

The activity indicator for the own profile is not that useful and we might consider to remove that as well in Bisq 2.

I dont think that the yellow state has much importance as even with one connection the app works and its very uncommon to have only 1 connection for longer. More important is to show when there are no connection and that should be alerting the user with some for of overlay/banner and offer a restart option.

[rodvar]

I agree with you that:

• Showing no connection is far more critical than differentiating between 1 vs. N peers, so we could simplify the states and focus UI/UX on alerting users when connectivity is lost.
• For the node, the yellow state might not add much value if the app works fine with a single connection most of the time — we could demote it or even remove it from the user-facing UI. However it makes more sense for the connect apps showing a hi latency connection with the yellow indicator.
• The activity indicator on the profile might be more noise than signal — if it doesn’t give actionable information, we could drop it entirely to reduce cognitive load.

If we move forward with this direction, we can:

• Keep ConnectivityStatus in the shared service for all three apps (since the node still needs this information),
• But adjust the UI layer for the node app to highlight only the meaningful states (e.g., connected vs. not connected) and trigger a restart action when disconnected. It looks like you have already worked that out in your Draft PR adding some kind of overlay reactive to connection loss, is that right?

[HenrikJannsen]

I just tested with my phone a lot and the bugs are gone and its pretty stable. Even after minutes in background the app stays connected but lower numbers. Even with 0 (I get the popup to restart or cancel - I canceled) it recovers in relative short time to have new connections again. I am testing without other apps open, so in real life conditions memory pressure will be harder...

The number of connections is a very important information we need to show on each screen (at least some indicator), as in the case of longer background pause the user need to know how stable it is.

Yes I added an overlay if connections are 0. Its just a quick solution, might require a better UX solution.