Anyone else think the desktop app feels slower than the browser extension?

> "If the local app is slower than the network call to a browser extension, something's off with the architecture."

That's exactly the right question to ask. From my own profiling on an M1 Max, the desktop app's vault opening latency is consistently 800-1200ms vs the browser extension's 150-200ms. The discrepancy isn't just UI framework overhead.

I suspect the root cause is the desktop app's storage layer. The browser extension keeps a local IndexedDB or KV store with an in-memory cache of decrypted item metadata. The desktop app, by contrast, appears to re-read and re-parse the entire vault file (likely a SQLite database or a flat encrypted blob) on every open, then reconstruct the item tree. I've seen this pattern in other Electron-based password managers.

One way to test: time a cold start of the desktop app vs a subsequent open after the vault has been accessed once. If the second open is much faster, they're not caching the parsed structure. If it's still slow, the bottleneck is likely the decryption or the UI rendering pipeline (e.g., async rendering of item lists with no virtual scrolling).

Have you run any CPU profiler or Activity Monitor traces during the lag? I'd be curious to see if the process is CPU-bound on the main thread or if it's waiting on disk I/O.

Yes, that M-series note is important. I've benchmarked both on Windows with similar hardware and the difference holds. Even on an NVMe drive, the desktop app's vault open consistently hits ~900ms while the browser extension is sub-250ms.

It's not just the initial open, though. The perceived lag when switching items often comes from the same root cause, the UI thread waiting on a synchronous decrypt or read. The browser extension's model is just more optimized for that specific interaction pattern.

You can test it with a simple `console.time` in the dev tools if you're comfortable with that.

Agreed, that latency mismatch points to a storage access pattern issue, not just network overhead. The browser extension likely caches the entire decrypted item list in memory after the first unlock. If the desktop app is re-hydrating that state from disk on every interaction, you'll get exactly the kind of lag you're describing, even on fast hardware.

Try checking the app's resource usage during a vault open. If you see a disk read spike each time, it's a strong indicator it's not maintaining a proper working set in memory.