-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mobile: use single webview & handle native/webview navigation ipc #3284
Conversation
…s, store last messages/groups location
…ng to keyboard open/close, fix active tab stutter and misfires
79965b7
to
4a32e67
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting approach! Looks to be working well - nice to not see loading spinners as I navigate around 🙂 I'm concerned about the fragility of all the state management and webview context, and it's hard to follow as a newcomer to the code. I think adopting a reducer pattern for that context could help a lot. I'd also like to see what the dev local mode is doing on your end - will schedule some time to walk through it with you.
…l with them blows up
@alecananian addressed the points we spoke about this afternoon 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks great
This moves from a webview per-tab architecture to a singleton webview overlay simplifying state & navigation required for moving between the two runtimes. Back buttons, internal tab navigations, etc. should work correctly now.
There are a few remaining items related to this work, but I'd like to get it merged so we can try it against the test build. I logged issues in Linear for tracking the following remaining items:
dev:ios:local
script that simplifies running against the local dev server. Needs to be fixed, hardcoded right nowFixes LAND-1504