is there any possibility to somehow affect the order how documents are pushed to the mobile clients? We currently face serious UX issues with increasing application usage and hence increasing number of documents. We already started to discuss workarounds like syncing the last few days, … but all the solutions come with other problematic drawbacks. For the user, a long sync time for the whole data set after login is in general not a problem. But as the newest and most important documents are always synced last, this makes the UX problematic. As I would assume, we are not the only ones with this issue, I wonder if there is any workaround less solution to this problem? Unfortunately, I wasn’t able to find other topics that provide a solution to this issue.
Thank you very much!
You can try assigning documents in additional high-priority channel(s) and have a separate replicator running for these to ensure they are replicated first.
If you’re after most recently changed docs, more than high-priority, maybe it’s enough to assign docs into a channel representing the week or month it was last updated, and have clients pull this channel first before pulling everything?
If you have a large amount of old or static-ish data to sync at initial login, you could also consider using a pre-built database
There’s no way to run the replicator with any kind of generalised different ordering (i.e. reverse sequence order), but it’s an interesting idea that may warrant further investigation. It would complicate our internal checkpointing and bookkeeping required to run reliable replication whilst handling interruptions, so I’m not sure how feasible it would be.