2:15 Thank you for introducing innovativative form factors. Exactly what we needed!

I have the feeling that google is too optimistic on the complexity to support foldables. True that config reload, view state persistence or aspect ratios are the foundation to support foldables. But it is not hat easy. Imagine a case with a typical master/detail view case: When screen folded, app shows the list and jump into detail when user clicks. When screen unfolded, app displays master and detail side by side. In the example you can clearly see that folding/unfolding screen is not as simple as rebuild UI with a different layout. It changes the navigation. More tricky case that it even hit on navigation history. What would you do if user unfold the screen when dived on detail screen? What about the back behaviour? By showing detail that was not shown previously, it means the app need to load more data. So the app might not work properly if it just restore the view state from bundle or use the existing data in survived view model Or the app might need to recalibrate the scroll bar progress as the visible content size changed.... From this simple example you can see there are plenty tricky cases might need to be handled right after the app resumed back from the saved instance state. They’re not easy to handle properly. But they’re critical for delivering a smooth experience on foldable devices. In reality, as there are so little foldable devices in market there, developer is very likely ended up to ignoring these cases. For user, who had spent premium grade of money to get the device but seems not likely to get premium level of experience. Why people still buying these expensive toys? I have to say foldable definitely has the potential, but to make it really accessible for general users, Google need to take this problem more seriously. For now, I don’t see a clear reason that strong enough either to drive general people to buy a foldable or to drive general developer to take foldable experience optimisation as high priority task.

The emulator has tons of issues. It can't even reach various settings screens without crashing. How could we try it for foldables if it's so unstable?

How will Pixel 3 support this when it doesn't output over HDMI?

@visceralcinema

5 жыл бұрын

USB-C to HDMI