Am I crazy or do you also see those lines in widgets backgrounds (especially in dark mode) in iOS 26? I filed a feedback (FB19073555) but it is weird
#ios26 #iosdev #swiftui

Today's attempt to fix a bug by rebuilding concave corners did not go well.

Cork version 1.5.6 is out.

This update includes a complete rewrite of the Homebrew pinning system in Swift for 20x performance gains, pinning from sidebar, manual update checking, and fixes for many crashes.

See https://open.substack.com/pub/corkapp/p/cork-156-out-big-changes?r=2vioyx&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true for more info.

Buy Cork to support its development: https://corkmac.app

Join the Discord community: https://discord.gg/kUHg8uGHpG

See the source code: https://github.com/buresdv/Cork

This god awful top tab bar is still a trainwreck. Why can I not select the Library tab by default in the bigger window but absolutely can in the smaller size where the tab bar is at the bottom?

I don't even have an idea what I should do as a developer here. #UIKit #SwiftUI

New update to my #UltimatePortfolio app.

This release includes a handful of small but meaningful improvements:
- Fixed a small bug when sorting all issues
- Added a delete button for tags in the sidebar context menu
- You can now mark issues as completed, or re-open them later if they need more work

Built with #SwiftUI and #CoreData.
GitHub: https://github.com/eneax/UltimatePortfolio

Here's a shocker from Building a workout app for iPhone and iPad https://developer.apple.com/documentation/HealthKit/building-a-workout-app-for-iphone-and-ipad

import Combine

@Observable final class CountDownManager {
var timeRemaining: TimeInterval = 3
var duration: TimeInterval = 3

private let timerFinishedSubject = PassthroughSubject<Void, Never>()
var timerFinished: AnyPublisher<Void, Never> {
timerFinishedSubject.eraseToAnyPublisher()
}

And the usual heap leak:
@State private var manager = CountDownManager()

SwiftUIKit 6.0 is out! This is a huge clean-up that removes many components that are extracted to separate packages. The future of this package will instead be to extend native types, to make #SwiftUI even more capable. You can read more about this in the release notes.

https://github.com/danielsaidi/SwiftUIKit/releases/tag/6.0.0

New blog post! "Creating amazing loading animations with SF Symbols" shows how to use SF Symbols and the powerful symbols effect to create amazing loading animations for #SwiftUI, without a bunch of custom code.

https://danielsaidi.com/blog/2025/06/19/creating-amazing-loading-animations-with-sf-symbols

How do you enter offer codes in iOS apps?
And how do you implement that as a developer?

I’ve explained both in a short guide using Key/Frame as an example:
https://www.hackingwithswift.com/forums/app-announcements/key-frame-extract-the-best-frames-from-your-video-clips/29669/29886

BadgeIcon 1.2 is out! This is a tiny Swift package for creating #SwiftUI icons that look just like the ones in Settings. This version adds 68 new predefined icons, bringing the total number of predefined icons to 118! It also makes the standard icon builder functions public.
https://github.com/danielsaidi/BadgeIcon

Starting to see the power of the whole vibe coding thing. Yesterday morning I had an idea, wrote it down. After dinner worked with Claude Code while doing dishes and bedtime.

In one hour I went from empty Xcode project to a working Mac app to convert Game Boy screenshots to STLs for 3d printing. #Xcode #swiftui #vibecoding #gameboycamera #3dprinting

Is @ _disfavoredOverload something we shouldn't use?

In ShapeUp I want to have these two subscripts
rect[RectAnchor.topLeft] -> CGPoint
rect[RelativeCorner.topLeft] -> Corner

but when you use:
rect[.topLeft] it's ambiguous

I want it to default to CGPoint and only use Corner if needed by the context. Is there a better way?

Here is a fun one:

if you have a #SwiftUI customizable toolbar and an optional inspector view, when the inspector becomes visible any optional toolbar items being shown will disappear.

It feels like the worst time to be an Apple developer in a long time. So many design and UI framework issues. Honestly I wish I had the time to come up with my own design system and work with that but that would be even worse because of how out of place it would look with the rest of the system.

Liquid Glass was not what was promised when I read the Gurman rumors. This is not a rethink of the fundamentals, it's a pig with lipstick.