Perhaps you could decouple content fetching and relay connections from the view’s lifecycle. Hadle connection state separately from view state. Maybe the view doesn’t need to be recreated from scratch each time it becomes visible again.
Discussion
nostr:npub14ya7n7czu3kyq3m2sn6kjawmtq6ll6kerrlm90gz9yzfjmflmsxq8dsn39 I’m not a Flutter dev, but it might be a good idea do add a CONTRIBUTING.md file providing guidelines and steps for contributing to the project. Like setup instructions and prerequisites, development workflow and conventions, code style and testing guidelines, pr process and code review expectations, project structure and build instructions. Or anything you judge necessary. It doesn’t need to be complicated, I guess.