pull down to refresh

It's a cool feature - but doesn't this also create a new attack vector?
For example, some parties might be tricked into generating a new quorum/new shares, whereas other parties are still using the old quorum/old shares.
3-of-5 becomes 3-of-4, where 2 shares are stale/invalid: Party A: share A1 Party B: share B1 Party C: share C2 (tricked) Party D: share D2 (tricked) Party E: removed
To mitigate this, I suppose you might want a secure communication channel and a protocol to ensure that either everybody moves to a new set of shares, or no one moves. That and keeping old shares on the devices, just in case. Keeping states is something that you might have to do anyway for the nonces.