Document the recommended way of producing multiple embedded Flutter UI / navigation states #37644
Comments
|
#30701 seems like a possibly related feature as well. |
|
Brainstorming doc go/multiple-flutters (google shared for now) |
|
Also consider de-globalizing any states in the FVC when going through this (context #52456) |
|
@xster : Hello, I'm interested in this multiple embedded flutter navigation, could you please offer more info, such as the road map, design doc, or discussions? Thanks! |
|
It's in our plans. Aaron is doing some prototyping this week. I'll send a doc shortly. We want to make sure we capture all the scenarios flutter_boost needs to solve as well. |
|
https://flutter.dev/go/multiple-flutters is a doc listing the constrains and requirements. Please take a look and check whether we've listed the needs correctly. The community's existing experience with this topic is highly valued. |
|
"customer: headline" recently mentioned that they're also very interested in this especially from the memory performance perspective. |
|
no update for a long time any updates? |
|
I've been working on a proposal for a Flutter plugin that will encapsulate best practices for most scenarios outlined in the multiple flutters doc. It isn't published publicly yet. It's still a work in progress but you can see my design here: There is a working prototype here (also a work-in-progress): https://github.com/gaaclarke/host_router |
|
when will it be made public |
|
@wanjm https://docs.google.com/document/d/1L_tiTeZpZuJstJmwt6sN6b-79Qy0LzMibCpCmxbtVfU/edit?usp=sharing I'm still working on it for clarity. |
|
The new design doc for this that supports concurrent views is at https://flutter.dev/go/multiple-engines |
|
That's pretty freaking cool @xster I do not mean to be pushy or anything, and I've seen the Release Plan on the document, but is there any chance we see this new API on stable by Q1 2021? |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
add-to-app cases adding Flutter as not a single contiguous navigation segment will want to preserve multiple Flutter instances' states and navigations stacks such as 2 Flutter tabs or a Flutter->native->Flutter navigation stack.
This involves first fleshing out the details of #37643 and deciding on a multi engine approach or a single engine approach.
This will likely be scheduled for 2020. Until then, using something like https://github.com/alibaba/flutter_boost (a single engine approach) seems reasonable.
The text was updated successfully, but these errors were encountered: