You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey I wonder is there a very rough estimate on when the multi-window features would go live (in dev/beta channel)? Not trying to pressure you guys, just wanted to pace my own project. Thanks! ✨
Hey I wonder is there a very rough estimate on when the multi-window features would go live (in dev/beta channel)? Not trying to pressure you guys, just wanted to pace my own project. Thanks! ✨
Hi there. It's a bit difficult to judge at the moment. The work is moving swiftly now, but there is still a good chunk left to complete. The windowing features are currently live behind the feature flag, which you can enable with:
flutter config --enable-windowing
Most of those windowing APIs are stable. They will only change in response to user feedback (which could include yours 😄).
Reacted by Julian Schmidt, Julian Schmidt, rbmk, Ellet, Aymen and Lukas Gaučas
Hey I wonder is there a very rough estimate on when the multi-window features would go live (in dev/beta channel)? Not trying to pressure you guys, just wanted to pace my own project. Thanks! ✨
Hi there. It's a bit difficult to judge at the moment. The work is moving swiftly now, but there is still a good chunk left to complete. The windowing features are currently live behind the feature flag, which you can enable with:
flutter config --enable-windowing
Most of those windowing APIs are stable. They will only change in response to user feedback (which could include yours 😄).
The windowing APIs cannot yet be used in applications because they can only be run using runWidget. Although it's not shown in the examples, after various attempts and struggles, I found that by using ViewAnchor and ViewCollection, it is possible to use the windowing APIs together with runApp. However, due to the characteristics of ViewAnchor, the app cannot be used normally.
Is there a way to properly use the windowing APIs with runApp? I'd really appreciate any advice or guidance!
@mattkae
I'm able to get it work on macOS (on Windows there is always a LateInitializationError when running example I'm not sure why). The API feels great! I think it could be nice to also be able to set window position and focus in RegularWindowController. Greedy me! 😄
Also, do you guys think there could be some kind of handle/tagging mechanisms so that the windows can be accessed from the native code? I'm thinking more advanced customisations like giving different windows different frames or modes of interactions. Or is this doable with the current API?
@momadvisor did the example run? When working with an existed app, I did find it necessary to remove MainFlutterWindow.swift from the xcode runner, also replace MainMenu.xib and adapt AppDelegate.swift according to the example app. After that my app runs with runWidget following the example pattern.
@rk54rk
I ran the example. It works well and is nice. The example works properly because it depends only on runWidget. However, runWidget cannot be used in production apps. Production apps must use runApp, and in that case the windowing APIs cannot be used in reality. Other than the approach that leverages the previously mentioned ViewCollection + ViewAnchor, I haven’t been able to find a solution. Although the windowing APIs were implemented quite some time ago, in my opinion it will still take a long time before they see a real-world usage.
@mattkae
A bit of update from test driving the windowing API:
I was trying to create an multi-window app with:
different window styles (normal/borderless).
custom borderless window with custom close/maximize/minimize buttons and still draggable.
set window position at creation.
set window position and size after creation.
inform dart side latest window size/position.
The new API currently doesn't support most of these features out of the box, so I was trying to make a custom swift plugin to do these, then communicate with dart using something like:
Then most of the features can be achieved this way.
However, with the current API, I had to match a dart side handle with the native window RIGHT AFTER the native window were created by the engine, by using the swift plugin to do something like "get the current key window" or "find the first NSWindow that we don't yet know about", which can be very fragile and racy.
Also any customise/styling/positioning by the swift plugin have to run AFTER the engine have already created the window. If I want to create a custom window at a custom position right from the beginning, there will be a visual jump which is hard to get rid of.
So I wonder if it is possible to add a mechanism to run the "custom initialisation" with swift code before the engine creates any window – something like MainFlutterWindow.swift, but for multi-window? Also, would it be cool to introduce a way to allow deterministrically match/handle native windows in dart/swift land? Not sure if this makes sense, let me know what you think! 😋
@momadvisor
From my brief test drive it seems my app runs fine with runWidget, not sure why "production apps must use runApp", but I'm interested to know!
currently, regular window, dialog window, tooltips are commited; doesn't it mean there is only context left (is context used for popup menu of right key of mouse);
is it in progress now ? or is there more high priority works which may delay it;
So I wonder if it is possible to add a mechanism to run the "custom initialisation" with swift code before the engine creates any window – something like MainFlutterWindow.swift, but for multi-window? Also, would it be cool to introduce a way to allow deterministrically match/handle native windows in dart/swift land? Not sure if this makes sense, let me know what you think! 😋
We have some ideas about adding initialization customizability (I've been experimenting with this in Linux myself), but it may be a bit of time/work to land them after we get the initial window types and concepts down. This is definitely on our radar though 😄
@momadvisor From my brief test drive it seems my app runs fine with runWidget, not sure why "production apps must use runApp", but I'm interested to know!
runWidget is the only way to make things work for now. In the future, runApp will probably be refactored to spawn a true regular window by default, so that developers can use runApp with other windows.
Reacted by rbmk, xiaobai, Ellet, Aymen, mockturtl, Raj Singh and Lukas Gaučas
I am very new to Flutter and kept hearing Flutter cannot do SDI. This is an awesome initiative. The one and only issue I hit was drag drop from a chiled window to the master. Had to implement a click to place alternative. Would be good to know if this is on the roadmap but otherwies truly impressive addition to the desktop space.
Edit: I think I found the answer in super_drag_and_drop.
I am very new to Flutter and kept hearing Flutter cannot do SDI. This is an awesome initiative. The one and only issue I hit was drag drop from a chiled window to the master. Had to implement a click to place alternative. Would be good to know if this is on the roadmap but otherwies truly impressive addition to the desktop space.
Edit: I think I found the answer in super_drag_and_drop.
Glad to hear its working well for you!
Do you have a code snippet for what's not working there? That might be a good thing to solve as a separate ticket if it's not working with multi window.
Do you have a code snippet for what's not working there? That might be a good thing to solve as a separate ticket if it's not working with multi window.
Super drag and drop solved the issues I was having. I had initial concerns that it was an external package but then read that it is the definitive solution recommended by the flutter team so that was the answer.
Activity
rk54rk commentedon Dec 7, 2025
Hey I wonder is there a very rough estimate on when the multi-window features would go live (in dev/beta channel)? Not trying to pressure you guys, just wanted to pace my own project. Thanks! ✨
mattkae commentedon Dec 11, 2025
Hi there. It's a bit difficult to judge at the moment. The work is moving swiftly now, but there is still a good chunk left to complete. The windowing features are currently live behind the feature flag, which you can enable with:
Most of those windowing APIs are stable. They will only change in response to user feedback (which could include yours 😄).
momadvisor commentedon Dec 14, 2025
The windowing APIs cannot yet be used in applications because they can only be run using
runWidget. Although it's not shown in the examples, after various attempts and struggles, I found that by usingViewAnchorandViewCollection, it is possible to use the windowing APIs together withrunApp. However, due to the characteristics ofViewAnchor, the app cannot be used normally.Is there a way to properly use the windowing APIs with
runApp? I'd really appreciate any advice or guidance!rk54rk commentedon Dec 15, 2025
@mattkae
I'm able to get it work on macOS (on Windows there is always a LateInitializationError when running example I'm not sure why). The API feels great! I think it could be nice to also be able to set window position and focus in RegularWindowController. Greedy me! 😄
Also, do you guys think there could be some kind of handle/tagging mechanisms so that the windows can be accessed from the native code? I'm thinking more advanced customisations like giving different windows different frames or modes of interactions. Or is this doable with the current API?
@momadvisor did the example run? When working with an existed app, I did find it necessary to remove MainFlutterWindow.swift from the xcode runner, also replace MainMenu.xib and adapt AppDelegate.swift according to the example app. After that my app runs with runWidget following the example pattern.
momadvisor commentedon Dec 16, 2025
@rk54rk
I ran the example. It works well and is nice. The example works properly because it depends only on runWidget. However, runWidget cannot be used in production apps. Production apps must use runApp, and in that case the windowing APIs cannot be used in reality. Other than the approach that leverages the previously mentioned ViewCollection + ViewAnchor, I haven’t been able to find a solution. Although the windowing APIs were implemented quite some time ago, in my opinion it will still take a long time before they see a real-world usage.
rk54rk commentedon Dec 19, 2025
@mattkae
A bit of update from test driving the windowing API:
I was trying to create an multi-window app with:
The new API currently doesn't support most of these features out of the box, so I was trying to make a custom swift plugin to do these, then communicate with dart using something like:
Then most of the features can be achieved this way.
However, with the current API, I had to match a dart side handle with the native window RIGHT AFTER the native window were created by the engine, by using the swift plugin to do something like "get the current key window" or "find the first NSWindow that we don't yet know about", which can be very fragile and racy.
Also any customise/styling/positioning by the swift plugin have to run AFTER the engine have already created the window. If I want to create a custom window at a custom position right from the beginning, there will be a visual jump which is hard to get rid of.
So I wonder if it is possible to add a mechanism to run the "custom initialisation" with swift code before the engine creates any window – something like MainFlutterWindow.swift, but for multi-window? Also, would it be cool to introduce a way to allow deterministrically match/handle native windows in dart/swift land? Not sure if this makes sense, let me know what you think! 😋
@momadvisor
From my brief test drive it seems my app runs fine with runWidget, not sure why "production apps must use runApp", but I'm interested to know!
dev-solo-game commentedon Dec 26, 2025
examples\multiple_windows example: creating a new window on windows will result in an error LateInitializationError
ilsubyeega commentedon Jan 7, 2026
FWIW i believe
examples/multiple_windowsshould implement dialog and popup(layer) view, which canonical previously showed before.wanjm commentedon Jan 19, 2026
currently, regular window, dialog window, tooltips are commited; doesn't it mean there is only context left (is context used for popup menu of right key of mouse);
is it in progress now ? or is there more high priority works which may delay it;
mattkae commentedon Jan 20, 2026
We have some ideas about adding initialization customizability (I've been experimenting with this in Linux myself), but it may be a bit of time/work to land them after we get the initial window types and concepts down. This is definitely on our radar though 😄
runWidgetis the only way to make things work for now. In the future,runAppwill probably be refactored to spawn a true regular window by default, so that developers can userunAppwith other windows.jdcryer commentedon Apr 23, 2026
I am very new to Flutter and kept hearing Flutter cannot do SDI. This is an awesome initiative. The one and only issue I hit was drag drop from a chiled window to the master. Had to implement a click to place alternative. Would be good to know if this is on the roadmap but otherwies truly impressive addition to the desktop space.
Edit: I think I found the answer in super_drag_and_drop.
mattkae commentedon May 5, 2026
Glad to hear its working well for you!
Do you have a code snippet for what's not working there? That might be a good thing to solve as a separate ticket if it's not working with multi window.
jdcryer commentedon May 5, 2026
Super drag and drop solved the issues I was having. I had initial concerns that it was an external package but then read that it is the definitive solution recommended by the flutter team so that was the answer.
enable-windowingcauses test failure with'PlatformDispatcher.instance.engineId != null': WindowingOwner[Platform] must be created after the engine has been initialized.#178706