npub1pt…4eera on Nostr: jumble is my favorite client in terms of UI, but it definitely has a bit of a loading ...

jumble is my favorite client in terms of UI, but it definitely has a bit of a loading lag—especially during initial startup. I've always thought that Nostr clients would benefit greatly from an architecture where a separate background process handles subscription to relays and manages writing events into a local database. Would the development complexity increase drastically with this approach? Perhaps, but I believe the advantages gained from such a design would be substantial. While completely rebuilding existing clients might not be practical, I hope developers creating new clients will seriously consider this kind of architecture.