Skip to content
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

How the multiscreen app can be design #262

Open
kodysharma opened this issue Aug 3, 2024 · 3 comments
Open

How the multiscreen app can be design #262

kodysharma opened this issue Aug 3, 2024 · 3 comments

Comments

@kodysharma
Copy link

What would be the design of the shell and core for multi screen application ??

@charypar
Copy link
Member

charypar commented Aug 5, 2024

It's quite an open ended question, could you elaborate on what you mean? An app with multiple screens which can be navigated between, or an app which runs across multiple physical screens?

What's true for both is that the view model needs to capture what's going on screen in a way the UI can easily pick up and use - its structure should follow the sructure of the UI.

If you can share details of some specific challenges you're facing, it will be easier for us to help.

@kodysharma
Copy link
Author

I am talking about navigation in the app. My app would have multiple screens so how will the navigation happen?
Core request to the ui using render capabilty that means core decides's what to show on the device screen.
I did not understand how the navigation work with rust crux.

@charypar
Copy link
Member

charypar commented Aug 7, 2024

Have a read through the Tap to pay example https://github.com/redbadger/crux/tree/master/examples/tap_to_pay, that does multi-screen navigation.

It uses SwiftUI to turn a basic description in the view model of what screen should be shown (there's an enum for the different screens) to the UI that should be on screen - like a NavigationStack a sheet and a fullScreenCover.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants