Open holmesworcester opened 1 year ago
Makes sense to me!
@leblowl does this updated draft make sense?
Notes:
Today Wiktor and Lucas convinced me that #2069 is a more straightforward and direct research question, even if we are ultimately interested in relays more than always-on libp2p/orbitdb nodes. Moving to backlog.
I was able to add entries directly to OrbitDB: https://github.com/TryQuiet/quiet/pull/2190 This is immediate, but how quickly the frontend connects to the backend and actually displays messages after resume seems to be variable. Sometimes its quite quick but other times it looks like it takes up to around 7 seconds.
Our product goal is that a user can open Quiet and see all important messages in less than 1 second.
Assuming we have already fetched recent messages from a relay server and they are on our device (a safe assumption since many apps including Signal work this way) can Quiet iOS display them to the user in less than 1 second after coming back to the foreground?
Here are some cases we care about a lot:
If not, how slow is it? What are the bottlenecks?
Fetched data can be in whatever form is most convenient: OrbitDB entries, IPFS blocks, CAR files, whatever.
If OrbitDB needs several seconds to get started, we can also use another way of displaying new messages to the user immediately, while we wait for OrbitDB.