Clarification on the planned removal of UIDesignRequiresCompatibility

In some cases, liquid glass creates problems because buttons take a much larger space.

Here is an example with navigation items.

Prior LiquidGlass (UIDesignRequiresCompatibility = true)

Everything fits without problem.

With LiquidGlass (UIDesignRequiresCompatibility = false)

Text is clipped as there is no more room for it as buttons are much wider.

Adapting a lot of screens may require significant design changes.

In this case, there is an option (not optimal, but working), by adapting the font size (https://stackoverflow.com/questions/62589078/automatically-adjust-navigation-item-title-font-size-to-fit).

        let title = NSLocalizedString("xxx.xxx.xxx.title", tableName: "Main", comment: "") // Retrieve the original title
        let navbarTitle = UILabel()
            navbarTitle.text = title
            navbarTitle.minimumScaleFactor = 0.5
            navbarTitle.adjustsFontSizeToFitWidth = true
            navigationItem.titleView = navbarTitle

Thank you for sharing your experience with Liquid Glass.

I understand the UI issues you described, and they are certainly important for developers planning migration work.

However, my primary question is not about the migration effort itself, but about Apple's current plan for UIDesignRequiresCompatibility.

Specifically, I would like clarification from Apple on whether the statement

"We intend this option(UIDesignRequiresCompatibility)to be removed in the next major release."

still reflects Apple's current plan, and whether "the next major release" should be interpreted as iOS 27.

This information is important for planning the migration schedule of our application.

In fact, it is very clear in Xcode documentation:

Warning Temporarily use this key while reviewing and refining your app’s UI for the design in the latest SDKs.

The system ignores this key when you build for iOS 27 or later, iPadOS 27 or later, Mac Catalyst 27 or later, macOS 27 or later, or tvOS 27 or later.

Thank you, Claude31.

The documentation you pointed me to was extremely helpful and appears to answer my original question regarding the planned removal of UIDesignRequiresCompatibility.

For context, I am responsible for an enterprise VoIP application that is currently scheduled to reach end-of-sale on March 31, 2027.

Migrating this application to fully support Liquid Glass would require substantially more work than simple font-size adjustments and would likely take approximately two months of development and testing effort.

Because the application is approaching its planned end-of-sale date, we are trying to determine whether a full Liquid Glass migration is justified, or whether it would be reasonable to continue using UIDesignRequiresCompatibility until the product reaches end of life.

Because of that, I would like to better understand the exact meaning of the following statement:

"The system ignores this key when you build for iOS 27 or later..."

Could someone clarify the following points?

1. What exactly does "build for iOS 27 or later" mean in this context?

   • Building with the iOS 27 SDK?
   • Setting the deployment target to iOS 27?
   • Or simply running the application on iOS 27 devices?

2. If an application is built using Xcode 26 and the iOS 26 SDK, will UIDesignRequiresCompatibility continue to function when that application runs on iOS 27?

Understanding this distinction is important for our migration planning and end-of-life strategy.

Thank you.