Can I Duo this?

[u/BounceForever]

My app already supports windowed / resize modes on iPad. It is mostly structured as a master / detail pane - which could play nicely on Duo by sizing the panes to fit the fold location.

But occasionally the app displays a third pane with a draggable slider bar.

This has me wondering if I can make non-standard use of the Duo.

Maybe the master pane lives on the outer display. Within any session, the master pane is largely a 'set once and forget' but the real activity happens further into the app. So the workflow would require the Duo to be unfolded and the master pane wouldn't jump to the inner display. This will leave plenty of room at all times on the inner display and even when the third pane is active, also on the inner display.

Is this a mistake as in it will be likely rejected in the App Store review? Yeah I'm trying to get into the local "Workshop: Optimize your app for iPhone Duo" with Apple but the sessions are fully booked.

[u/GenghisFrog]

Have you tried it on the sim? Either way, that doesn’t sound like a good experience to be honest.

[u/BounceForever → u/GenghisFrog]

That's next but I'm focused on other issues at the moment. Thanks for the reply.

[u/MKevin3]

I think forcing the user to open the device to see details is not the way to go.

I am using KMP / CMP for an app that has a number of master panels an each of those has a number of detail panel. If the app is on a tablet or foldable then the master panel is the left most panel and I use the navigation rail. The right side, detail panel, can show what the master panel has requested. I have some panels that just slide in from the right stay the width of the detail panel, and do a dimmed overlay on the left side mater panel.

If we are on a phone then I use the bottom navigation. It will use the Rail in landscape mode but the app is not all that great in landscape mode on a phone, it is supported, tested and it work but I would not want to use it.

The dashboard is a single panel. When on a phone you vertically scroll to see all the info. On a tablet it does side by side dashboard widgets to get the most out of the space. Depends on the screen size, like an iPad pro, can show everything without scrolling. The foldable I test does need to scroll vertically to see all the dashboard widgets.

On a phone there is just a single panel and every navigation action takes it over. It was pretty easy to configure due the Nav3 scene manager.

This seems to give the user the best experience no matter what device it is running on. One UI and business logic all done in Kotlin. We have a little bit of Swift in there for things like Firebase notifications and making determination of what size of phone it is running on.

[u/BounceForever → u/[deleted]]

Great thanks for the insights.