Hello everyone. I want to do navigationTitle (located on the top side on MacOS system) in LiquidGlass style. now my solution look like: just black rectangle. But i want like this: opacity and LiquidGlass. Like in Photo app in MacOS. Please help me, thank you in advance. My code: struct RootView: View { @Environment(\.horizontalSizeClass) var hSize var body: some View { if hSize == .regular { DesktopLayout() .navigationTitle("title") .toolbarBackground(.ultraThinMaterial, for: .automatic) } else { MobileLayout() } } }

I’m working with Reality Composer and noticed that images added directly to a scene appear significantly darker when viewed in AR. This seems different from how other objects in the scene respond to lighting, especially under varying real-world light conditions. Is this expected behavior? Are images treated with a different lighting model in Reality Composer? Is there any recommended way to get more consistent light response for image-based artworks?

This is my first attempt at creating a Wallet pass, actually a generic store card. When I see it with Pass Viewer on macOS, I get 1 look, when I see it with the iPhone simulator or iPhone proper, I get a different view. Neither is what I was hoping for, a simple vertical layout of an address. Could someone steer me in the correct direction? My json: "formatVersion": 1, "passTypeIdentifier": "pass.org.danleys.4KSBarcode", "serialNumber": "__SERIAL__", "teamIdentifier": "----", "organizationName": "4 K.I.D.S. Sake", "description": "4KSBarcode", "logoText": "4 K.I.D.S. Sake", "foregroundColor": "rgb(255, 255, 255)", "backgroundColor": "rgb(255,0,0)", "storeCard" : { "primaryFields" : [ { "key" : "ClientID", "label" : "", "value" : "" } ], "auxiliaryFields": [ { "key": "street", "label": "Address", "value": "339 Remington Blvd" }, { "key": "city", "label": "", "value": "Bolingbrook, IL 60440" } ] }, "barcode": { "format": "PKBarcodeFormatCode128", "message": "__SERIAL__", "altText": "__SERIAL__", "messageEncoding": "iso-8859-1" } } On macOS: On iOS: Thank you. Ed

Hi friends, I need a design and coding team to publish a fintech app. Can anyone help me with this?

I would really like to be able to categorize my contacts. I work for a grocery store and have contacts from various companies. I would like to be able to categorize them by company or group them as I see fit. Currently, I don't see a way to do this. Please add this in a future update. Having all contacts just alphabetically is not efficient enough. Also, I would like to be able to manually adjust the size of widgets. i.e. If I want more stocks to be visible, I would like to be able to lengthen the height/width of the widget beyond what it currently allows to view more information. Thank you. If you have any follow-up questions, please let me know. Torrey

I am requesting a dedicated toggle in Settings > Display & Brightness (or Accessibility) to enable/disable the Liquid Glass UI effects so that I am able to get frosted glass thingy effect that was in iOS 18 back.

Hello everyone, I’m looking for some advice or shared experiences regarding an app rejection under App Store Review Guideline 4.3(b) – Design – Spam. Our app was rejected and, after an appeal to the App Review Board, Apple maintained that the app “duplicates the content and functionality of similar apps in a saturated category.” We strongly disagree with this classification and are struggling to understand how Guideline 4.3(b) has been applied in our case. The app was developed as an original product: Custom-designed content (including original cards and interactions) A unique visual style and UI A distinct interaction flow focused on encouraging social interaction between users This was not a template-based or reskinned app, nor is it part of a series of similar submissions. We fully respect the App Store Review Guidelines and are open to making adjustments to better align with them. However, what we find difficult is the lack of specific, actionable feedback. We have not received clear guidance on which exact elements are considered duplicative or what changes would meaningfully address the concern. Some of the questions we are hoping the community can help with: In your experience, what typically triggers a 4.3(b) rejection in cases like this? Are there specific mechanics, terminology, or presentation choices that reviewers often interpret as problematic? Have others successfully resolved a 4.3(b) rejection without completely abandoning their app concept? We have already invested significant time and resources into this project, and being advised to create an entirely new app is not financially feasible for us. We are genuinely trying to understand how to proceed in a way that is constructive and compliant. Any insights, experiences, or advice would be greatly appreciated. Thank you in advance. — Lars

Hi everyone, We noticed a readability issue with the CallKit incoming call UI on the lock screen in iOS 26. In our case, the “slide to answer” text appears too faint and unclear, making it difficult to read. The arrow button is visible, but the text itself has very low contrast against the background, especially on certain wallpapers or under lower brightness conditions. From the screenshot, you can see that: the caller name is clear, the overall incoming call UI is shown correctly, but the “slide to answer” label is barely visible. This seems to be a system UI / CallKit presentation issue rather than something controlled by the app, since we are using the standard CallKit incoming call flow. We would like to know: Has anyone else seen this issue on iOS 26? Is this considered a known UI regression or contrast issue in the new system design? Is there any supported way to improve the visibility of this text, or is it fully managed by the system? Any confirmation or related reports would be very helpful. Thanks.

I’m developing an app that includes a navigation bar with a centered title and a single right bar button item. I’ve noticed that when both the navigation bar title and the right bar button item’s title are relatively long, the navigation bar title becomes hidden. This issue only occurs on iOS 26. When running the same code on iOS 18, the layout behaves as expected, with both elements visible. Has anyone else experienced this behavior on iOS 26? Is this a known layout change or a possible bug?

Hi everyone, I’m a mixed reality designer currently building visionOS experiences (RealityKit + SwiftUI), and I’m working on a course at Arizona State University where we develop a project in response to a real-world client. I’m looking to collaborate with someone in the visionOS ecosystem who would be open to sharing a simple prompt or brief (nothing confidential), which I can use to create a proposal response. The outcome would include: Spatial concept + storyboard Interaction design direction Rough scope, timeline, and team structure Optional small prototype in visionOS The goal on my side is to better understand how spatial work is framed and communicated in real-world scenarios, especially within Apple’s ecosystem. The ask is very lightweight: 1–2 short check-ins during April or async feedback via email A bit about my work: Built Spatial Synesthesia for Apple Vision Pro Eye tracking interaction that isolates instruments in a live orchestral mix based on color perception Working with computer vision and spatial anchoring in Unity and visionOS Focused on perception-driven interaction and minimal UI systems If you’re a developer, designer, or part of a small studio working in visionOS and this sounds interesting, I’d love to connect. Thanks in advance. Leo

After I upgraded to iOS 26, most of the App icons with white backgrounds appeared blurry, as if they had been blurred by Gaussian filtering. However, some of them were normal. As shown in the picture, if you observe carefully, you will notice that the DeepSeek Chrome Photos icon is blurry, while Expo Go and LightBlue are normal. Is this a bug of the system? Does anyone have the same problem?