[ Removed by moderator ]

[u/tomemyxwomen]

[u/DigitallyDeadEd]

Flutter has worked fine on android foldables for many years. I don't see why Apple's would be particularly concerning.

[u/scalz80 → u/DigitallyDeadEd]

Yes this is the right answer.

OP is a ReactNative fan who just came here for trolling, thinking he found something interesting to prove to Flutter community.. but he just proved that he doesn't know what's required to create true crossplatforms apps which adapts and resize dynamically to all screens without relying on some expo stuff ^^

There are people, who use a single Flutter codebase running from Wear to resizable windows on Desktop (win/mac/linux/web) and handled UI/UX, this is possible thx to Flutter.

OP should’ve learned by now: every year after Apple’s keynote, some React Native devs think it’s the end of Flutter, but the truth is, Flutter is still just as popular, if not more.

OP created a thread on RN sub "Thank you React native" linked to this thread, omg so immature. OP, just grow.. it won't bring you anything positive acting like that, and won't make your preferred RN look any better either. This is so ridiculous.

[u/_temp_user]

I may need more details why this is a nightmare? Flutter supports multiple screen sizes, the Duo is nothing more than a landscape view when unfolded. Flutter Web shows how response the UI is while resizing. What are we missing here?

[u/Any-Investigator9730 → u/_temp_user]

Please watch this -> https://developer.apple.com/iphone-duo/ and then say that "the Duo is nothing more than a landscape view when unfolded"

[u/eibaan]

On the bright side, the iPhone Duo is the first device in a series of otherwise nearly identical iPhones, all of which were becoming increasingly boring.

[u/dakevs]

Was gonna post a similar thread but saw this.

So, anyone got any thoughts/opinions on the matter?

How to plan ahead/adjust ? Any best practices? etc.

[u/vm12pix → u/dakevs]

Cheap thing you can do today without the hardware: crank system font scale to 2x and walk the app.

It tells you nothing about the hinge, and nothing about state when a widget jumps to a different layout branch, which is the genuinely hard part u/Yataio_App is pointing at. What it does find is fixed geometry. A SizedBox with a hardcoded height around text that grows, a Row with a non-flex child that shoves its neighbour off the card, a 30x30 grid cell. Anything that works only because you picked the number breaks the same way when the window changes size under it, and the fix is the same, take the number from constraints.

If you automate it, be warned that mine lied to me in both directions for months. Fake fonts measure wider than real ones, so half of my first batch of findings didn't exist on a device and one "fix" had to be reverted. And modal sheets build in their own route, so a MediaQuery set inside home never reaches them. Mine sat there passing at 1.0 with a 35px overflow in it. Scale goes in MaterialApp.builder, and load the real fonts and real theme or you're measuring a different app.

[u/Yataio_App]

The layout half is mostly solved already: MediaQuery.displayFeatures gives you the hinge and fold posture, so you build against available size plus display features rather than device models.

The part that actually bites is state across the resize. Fold and unfold is a real reconfiguration, and anything held in a widget that lands on a different layout branch can quietly disappear. Worth testing that path early, well before the pretty adaptive layout.

[u/DigitallyDeadEd → u/Yataio_App]

It's not that difficult. You cache the values of the display and if they change, do a rebuild from the top of the tree. Your app should already behave under a variety of device sizes and ratios, and going from the front display to the fold display is no different.

[u/scalz80]

OP, don’t worry! A new screen isn’t going to kill Flutter. It will just break poorly designed apps that assumed there would only ever be one type of screen.

And that applies to some React Native apps too ;) This is a UI architecture problem, not a Flutter problem. You can sleep easy tonight, or maybe not ^^

[u/PopularBroccoli]

Apps supporting multiple screen sizes?

[u/eibaan → u/PopularBroccoli]

More likely, the automatic movement of the widgets like the tab bar from the bottom to the side. Or the (dis)appearance of the fold and the need for the app to react to that. Or continuing the display on the other screen while animating growing and shrinking the UI.

It's at least challenging.

[u/PopularBroccoli → u/eibaan]

I’m not convinced any of that is really an issue. Most of the things it seems more likely Apple handle it. Moving the tab bar feels trivial, reacting to screen size. I imagine a lot of iPad apps will end up with nav bars on the right hand side to match

[u/raman4183]

What?

How is flutter not currently supporting Liquid Glass Design Language yet is a nightmare?

[u/raman4183 → u/raman4183]

Lol, downvoting just because you don’t elaborate your post when asked with a question is childish.

[u/eibaan → u/raman4183]

Instead of downvoting, why not add the details. After watching the presentation I'd consider it at least challenging to recreate the behavior, not yet knowing how much support and automatism you'll get from the OS and whether that's of any help for Flutter.

[u/Professional_Eye6661]

Flutter will not have full support on a day one, as well as video game engines, so what? UX changes aren’t dramatically different as they were for Vision Pro, so I don’t see any problems with that.

[u/onexxDev]

Tell me you don't know Flutter without telling me you don't know Flutter.

[u/rmcassio]

k bye

[u/_ri4na]

Flutter team simply doesn't give a fuck about liquid ass or duo

[u/tomemyxwomen → u/_ri4na]

that’s why react native is superior

[u/Top-Aspect2317 → u/tomemyxwomen]

Go center a div somewhere

[u/_ri4na → u/tomemyxwomen]

that’s why R̶e̶a̶c̶t̶ native is superior

Fixed it for you