Initial data sync workflow and UX redesign #2678
Replies: 3 comments 9 replies
-
In reference to my comment above, I think we can have the new workflow take the said approach. That is, on app install and launch:
Attached is an example of how this progress dialog would look like: 
Here are some other great ideas. |
Beta Was this translation helpful? Give feedback.
-
User shouldn't at any point be kept on login screen until sync completes. We can log the user in, show some of the synced data and progress of the remaining data to be synced. We should avoid to keep the user waiting, it's a very frustrating User experience.
We should never block user from accessing the app because of a sync. We can should some already synced data as the rest keeps syncing for better UX. A lot of users might get frustrated with this kind of experience especially if they have very slow internet connection. @ndegwamartin what timelines do you have on this, I can take a look at it in detail and share more thoughts when I get a moment. |
Beta Was this translation helpful? Give feedback.
-
|
@pld for your first question checkout a screenshot on the link here |
Beta Was this translation helpful? Give feedback.
-
|
Cool, I think as is in that screenshot is better than sitting on the login page. Even better would be to more selectively disable stuff in stead of the whole app, but that gets very tricky, and maybe there's not enough you could do during an initial sync to make that worthwhile |
Beta Was this translation helpful? Give feedback.
-
|
🥲 Are we able to allow user maybe access features that have been synced as others are still in sync, related to @pld's question of split sync? |
Beta Was this translation helpful? Give feedback.
-
|
I concur with pld, that would (most probably) be complex to implement, maintain and scale |
Beta Was this translation helpful? Give feedback.
-
|
yes, we're actively looking into reducing the sync time |
Beta Was this translation helpful? Give feedback.
-
|
Here are some related guidelines by OHS that can inform the discussion here as well |
Beta Was this translation helpful? Give feedback.
-
Overview
Currently the implementation of initial sync is such that once it fails to complete it blocks the user with the sync progress dialog even after all the default retries are complete.
From the conversation here sounds like the consensus is to block the user from using the app until all data in the initial sync has successfully been synced down.
The above leads to a poor user experience given that the app appears stuck with no possible user actions. The idea is to come up with the final design and subsequent implementation to improve the UX above.
Here is a collation of discussion points ideas that have gone into this conversation.
[@joyce-x-chen ]
Desired UX cc design-team @pms, @tpms
Can we try to think of reasons why initial sync would fail so we can provide more context/instructions? For example:
When is the next retry cycle ? Is it the same as normal remote sync, i.e. every 15 minutes and what is the “start” of the 15 minute interval? The generic sync failed error looks ok for this until we have more time to workshop and test other error messages.
[@ndegwamartin ]
It should be the same periodic sync triggering process thus recurring every 15mins after a user logs in and enters the pin
[@ellykits ]
That's correct periodic sync is by default scheduled to run every 15 mins; the duration can however be overridden via app configuration but should not be less than 15mins as required by Android system.
[@joyce-x-chen ]
What are the user’s possible actions after seeing the sync failed error?
I have some apps on my phone that force an update before I can use it…and it usually stays on a “startup” page before allowing me to enter the app. I wonder if it’d be more intuitive for initial sync to happen during the initial login process rather than AFTER successfully logging in. So the user stays on the login page during initial sync, and only after successful initial sync, can they enter the app. Cc: @pld
[@ndegwamartin ]
For the items above
On the suggestion for sync before the Login page redirects I think I agree it can lead to better UX. The user will never get past the Log in page if sync doesn’t complete so it won’t be confusing for the user on whether they should interact with the app or not.
[@dubdabasoduba ]
I agree on keeping the user on the login page until the initial sync is complete. We however need to account for the following things.
[@AnnieMungai ]
@ndegwamartin if sync fails - can we add the different reasons for the failure? Example
Sync failed- no internet connection.
Sync failed - XYZ other reason. Can we know the reasons for sync failure and give brief instructions on what the user should do?
[@samkanga ]
I am in support of blocking the app use until we get a successful sync retry or manual sync. We are bound to run into more issues if we allow user to proceed without a successful initial sync or sync retry. These would include:
[@dubdabasoduba ]
I agree on keeping the user on the login page until the initial sync is complete. We however need to account for the following things.
Resources
Beta Was this translation helpful? Give feedback.
All reactions