feat: add mobile context communication #196
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability for apps to work on mobile.
Things we had to change:
postMessage
APIs. We can hoverer rely on using thewindow.parent.postMessage
as the mobile app will aliaswindow.parent
towindow.ReactNativeWebView
and the postMessage method behaves the same.window.parent
as there is no real need to "isolate" from other iframes in the native context.mobile
key to theLocalContext
that is set totrue
when the app is embedded in mobile. This could allow the interface to adapt and display a better UI for larger touch targets. This is also used to choose the communication strategy (as stated above).TLDR:
CommunicationChannel
abstraction that allows to use the apps on mobilequery-client
to work on mobile