"How does session management and authentication handle fold transitions on Apple Duo? If the device remains folded for 30+ seconds, could the user session timeout despite the app being active? Should the authentication token be refreshed during or after a fold transition to prevent expiry? Can user login state become invalid if fold occurs while the device is in a folded position? After fold completes, should we re-validate the authentication token before allowing critical operations (payments, sensitive actions)?"

"What are the financial transaction integrity risks on Apple Duo during fold transitions? Is there a risk of double-charging if fold occurs during payment processing? If a user confirms payment and immediately folds the device, how is the transaction status handled? Can we guarantee the payment was processed only once? Can a failed payment retry mechanism cause duplicate payment attempts if fold occurs during the retry logic? If a refund or payment reversal is initiated and fold occurs during the operation, could the transaction be interrupted or processed twice?"

"For payment confirmation and retry flows on Apple Duo: If fold occurs during payment confirmation screen: Should we pause/dismiss the confirmation modal? Can user confirm payment while device is folding? Should we preserve the confirmation state and re-display after fold completes? What if transaction is already processing when fold occurs? For failed payment retry scenarios: Should we automatically retry after fold completes?

"For QR scanner functionality on Apple Duo: Should QR scanner remain accessible during fold, or should it be disabled? If fold occurs during active scanning, what happens to the scan session? Should we use one camera or dual cameras on both screens? How do we handle camera permission state across fold transitions? Should scan result be displayed on the screen where the camera was active?"

"How should our application's components (campaign cards, payment flows, bottom sheets) be displayed on iPad and Apple Duo? Should we adapt our current iPhone-only design to iPad, or create separate layouts? Should layouts work seamlessly during fold/unfold transitions on Apple Duo? Can we reuse the same storyboards and XIBs, or do we need device-specific implementations? Are Size Classes sufficient, or do we need custom breakpoints for these different screen sizes?"

"When implementing SegmentedControl for container navigation on Apple Duo: What's the optimal segment placement when the screen is folded (top, side, or hidden)? How do we handle segment state persistence across fold transitions? Should we use a single SegmentedControl for both screens or separate ones per display? Are there performance implications for frequent container switching on dual screens?"

Should we implement different layouts for iPad (horizontal) vs Apple Duo (dual-screen)? How should we preserve the segment selection state during fold/unfold transitions? Should the segment bar be fixed or part of scrollable content? For dual-screen navigation, is TabBar or SegmentedControl more appropriate on Duo?"

"How should our application's components (campaign cards, payment flows, bottom sheets) be displayed on iPad and Apple Duo? Should we adapt our current iPhone-only design to iPad, or create separate layouts? Should layouts work seamlessly during fold/unfold transitions on Apple Duo? Can we reuse the same storyboards and XIBs, or do we need device-specific implementations? Are Size Classes sufficient, or do we need custom breakpoints for these different screen sizes?"