I had, a long time ago (over 10 years) developed an application that is connected to my UPS (for solar panels).
Until yet it worked very well, and I didnot have to compute more than making updates of XCode. That was all.
But yet I have swiched to the latest value of switch, and it continue to compile, but it does'not work. I am asking to yo in order keeping my app working as previously. As it does not work, which library is replacing Cloudkit.framework ?
and which library is replacing InsPersistantContainer.framework ?
Have a good day
Guy Desbief
Explore the art and science of app design. Discuss user interface (UI) design principles, user experience (UX) best practices, and share design resources and inspiration.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I’m not a developer - I’m just trying to find out where to post a question I have that might relate to iOS 26.
I am developing an app in Swift Playground (No Xcode). All my Views respond to the navigation call when I click NEXT except one. When I click NEXT the app hangs then crashes. The error message does not identify the cause of the crash. I have research every possible lead with no success. I would like to get some ideas on how to resolve this issue.
I've been playing around with iPad PRO M5 13" as part of my goal to implement some music relating SPH particle simulation effects on it - and this involves utilizing tap events also from the incredible looking fresh screen the device has.
See more information from here, all should be overreactively implemented but the ideas remain (with almost zero cost copy fragment shader) :
`https://youtu.be/ci-GSgQ0wlM`
This attached image shows the tap effects implementation brought just bit a little further than in the video.
What is the step-by-step process to run an iOS application paired with the Mac in my MAUI project?
I am using Windows with Visual Studio 2022 V17.13.5.
Application: Multiplatform;
Language: C#;
Framework: MAUI 8;
Xcode: 16.2;
Objective: Identify and fix the issue to allow the application to run correctly.
Hey, everyone. I'm having an issue with my modal shadows when building for macOS. I've attached an image to show you what's going on.
I have a rounded corner window, and when the In-App Purchase overlay opens, the modal shadow of that rounded window is square (which doesn't make sense, and looks bad).
Can somebody please help me address this? I've tried searching high and low for a solution but I can't find anything :-(
I really appreciate you taking a look! -Logan
Hi,
App Image: What is the best format - jpg, tiff, giff, psd or ai?
What is the maximum and minimum number of items the app can contain?
Please advise.
Thanks
I have many Apple devices, such as macbook, iPad and iPhone. It's very convenient for me to transfer files between devices. However, when I want to send files to my own device in public places, I often click on the wrong recipient because the list avatar keeps changing. I hope the list of recipients can be grouped One group is my own device (or the one I often send to), and the other group is other devices. When the user is about to send, the mouse will be in a relatively fixed and mentally expected area. I feel that this can reduce the probability of sending wrongly
Hi,
is it me or latest beta has pronlem with brightness?
i have iPhone 16 pro, and now i must keep disabled auto brightness , at keep slider more or less at maximum, in order to clearly see the screen.
fabrizio
Hi all,
I wanted to check whether the NFC bottom-sheet UI shown by iOS during an NFC reading session can be customized.
We have a Figma design (attached) for how the sheet should look, but we are not sure whether iOS allows modifying the default NFC UI.
Is UI customization supported, or is the bottom sheet fully controlled by the system?
Thanks in advance.
Hi,
in the Human Interface Guidelines, Apple writes:
Avoid using a segmented control in a toolbar. Toolbar items act on the current screen — they don’t let people switch contexts like segmented controls do.
Along with this image:
Source
I'm confused by this example. The screenshot seems to be showing a segmented control in a toolbar.
Is this saying that the Phone app's All/Missed toggle is different from a segmented control? Under iOS 26 it seems to take a different style compared to a regular segmented control. If so, which component is used to create this filter?
Could you please clarify the guidelines? Thank you.
Some SF Symbols (wifi for example) render fine with the variable. But many, mostly ones with the circle being variable, do not seem to work. The SF Symbols app shows them rendering with a variable fine. But in code it doesn't work. Am I missing something or is there a reason?
var body: some View {
HStack {
Image(systemName: "01.circle", variableValue: 0.5)
Image(systemName: "figure.wave.circle", variableValue: 0.5)
Image(systemName: "wifi", variableValue: 0.5)
}.font(.largeTitle)
}
}
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
In the clock app when making an alarm for myself to wake up, I found this bug where If you swipe left On an alarm without deleting it and then Swipe right it does a goofy visual glitch where it teleports to the top of your screen.
I am working on a Mac App that was developed with Objective C and Interface Builder. In earlier versions of Mac OS the window title was centered. Now in Tahoe it's left-justified. Is there some way to set this? There is no setting for this in Interface Builder and I can't see any way to do it programmatically by reading the developer documentation. Is this even possible?
I'm developing an iPadOS 18+ application that uses a UITabBarController, styled as a sidebar, to serve as the primary navigation interface. This setup includes 20 different tabs, each representing a distinct section of the app.
For the user experience, each tab needs to present a master-detail interface, implemented using a UISplitViewController. The goal is to allow users to navigate between tabs via the sidebar, and within each tab, access related content through the split view's list-detail pattern.
The Problem:
Currently, my implementation involves instantiating a separate UISplitViewController for each tab, resulting in 20 unique split view instances embedded inside the UITabBarController. While this works functionally, it leads to significant memory usage, especially after the user opens each tab at least once. The accumulation of all these instantiated view controllers in memory eventually causes performance degradation or even memory warnings/crashes on lower-end iPads.
The Question:
What is the best approach to implement this type of architecture without running into memory management issues?
Specifically:
Is there a way to reuse or lazily load the UISplitViewController instances only when needed?
Can we unload or release split view controllers that haven't been used for a while to reduce memory pressure?
Would a custom container controller be more appropriate than using UITabBarController in this case?
Are there iPadOS 18+ best practices or newer APIs that support this kind of complex multi-tab, multi-split-view structure efficiently?
Any advice on how to optimize memory usage while preserving the sidebar navigation and split view layout would be highly appreciated.
I just discover that feature (a folder lost in the middle of others desktop folder ).
so with each updates:
-/usr/local is emptied
-somes apps in the Application folder, are deleted, even paid apps ..
-i lost : Docker, python 3.13, latexlive2025, Apache NetBeans, java install, Affinity Publisher 2, all my 3D slicers ... github desktop, Epic Games Launcher, ........
296go of apps
Franckly : c'est la merde !!!
I am using a MacBook Pro 16" 2019
any way to stop this behavior ?
thank you !!!
I have an ongoing activity in progress.
Think of:
a delivery in progress
house internet reboot in progress
some water / electricity / internet / tv outage.
(food) order processing
I want to show a persistent toast message above the tab bar, across all tabs and screens across the app. It could take 15 minutes until the activity is finished.
Obviously there's a challenge of:
accessibility
content overlaying with each other
extra engineering effort.
What we've thought of doing is:
Option1: show a toast message, but when a modal is presented then it presents on top of the toast message. The toast message no longer updates itself. Once the modal is finished, then the toast message re-appears and continues to update.
Option2: keep the toast message across all tabs and modals and work through the challenges mentioned
Question:
What are some other design approaches that could be taken to persist an ongoing activity (much like 'Live Activity', but just across the app when it's in foreground) or what are some design reasons that the two options considered are bad?
Hi everyone, I'm new to building apps on Swift and recently I've been wondering how does Apple get this blur effect behind the control center on Mac OS Tahoe. I think it would be nice to use in an app that I'm making but I can't seem to find it in the docs. Is it available through AppKit? I would appreciate some help on this
Hey there! I'd love to know if theres a way where you can animate items between ZStack and VStacks? Just like the native iOS notifications on the Lockscreen stack at the bottom and if tapped, they convert from a Stack to a List - I have a list with items, displayed in a VStack, and I make the list collapsable when swiping down, where the items stack behind eachother with a progresisve reduction in opacity & scale, but I havent figured out a way to animate the items between the list and the stack - where you can visually see items starting to overlap and stack ontop of eachother when collapsing the list.