@npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg what factors into the bootup/setup time before the #Lightning wallet is displayed?
(android/grapheneos)
@npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg what factors into the bootup/setup time before the #Lightning wallet is displayed?
(android/grapheneos)
Pulling down the webpage and web assembly files (if using web version)
Checking local state against remote
Pulling down any out of date state
Decryption
Loading all of the channel info
Pulling down and loading LN gossip and scorer
Any plans for clever caching/local storage strategies? Currently taking a long 5 seconds every time I open the wallet.
I think the average amount of time someone will wait for an app before moving on is like 2 seconds.
Really impressed with Mutiny so far.
Is the operation executed in serial? I wonder if concurrency is an option.
Yeah, we definitely want to make it faster. A lot is going on at once and quite a bit that needs to download and compute to even be usable at all (the node is like 10mb).
Backgrounding it and making it look like it is syncing could help a bit instead of showing an empty loading stare.
For sure: coming at it from both angles by improving load time but also eliminating the perception of a frozen/unresponsive dialog.