I feel like I'd have a much easier time reasoning about UIKit's explicit and imperative approach to navigation because I actually know exactly what I've written and what it's doing
with SwiftUI it's more like you give the OS an IKEA manual and hope it figures it out
with SwiftUI it's more like you give the OS an IKEA manual and hope it figures it out
October 24, 2024 at 9:37 AM
I feel like I'd have a much easier time reasoning about UIKit's explicit and imperative approach to navigation because I actually know exactly what I've written and what it's doing
with SwiftUI it's more like you give the OS an IKEA manual and hope it figures it out
with SwiftUI it's more like you give the OS an IKEA manual and hope it figures it out
*stirs the pot*
Friendly reminder that Andy Matuschak once said "React's model for the UI layer is vastly better than UIKit's" in response to the upcoming release of React Native.
Friendly reminder that Andy Matuschak once said "React's model for the UI layer is vastly better than UIKit's" in response to the upcoming release of React Native.
February 10, 2024 at 2:12 AM
*stirs the pot*
Friendly reminder that Andy Matuschak once said "React's model for the UI layer is vastly better than UIKit's" in response to the upcoming release of React Native.
Friendly reminder that Andy Matuschak once said "React's model for the UI layer is vastly better than UIKit's" in response to the upcoming release of React Native.
Checkout UIKit's Accessibility Capabilities: developer.apple.com/documentatio...
And SwiftUI's Accessibility environment variables: developer.apple.com/documentatio...
And SwiftUI's Accessibility environment variables: developer.apple.com/documentatio...
Accessibility for UIKit | Apple Developer Documentation
Make your UIKit apps accessible to everyone who uses iOS and tvOS.
developer.apple.com
December 21, 2024 at 11:58 AM
Checkout UIKit's Accessibility Capabilities: developer.apple.com/documentatio...
And SwiftUI's Accessibility environment variables: developer.apple.com/documentatio...
And SwiftUI's Accessibility environment variables: developer.apple.com/documentatio...
Seems like I once again got bitten by the transition controller in some very weird way causing UIKit’s doc browser controller to break.
It’s super strange, you launch to it, present your document over it in .fullScreen style, close document and try dismissing back to browser. And your app feels […]
It’s super strange, you launch to it, present your document over it in .fullScreen style, close document and try dismissing back to browser. And your app feels […]
Original post on infosec.exchange
infosec.exchange
June 18, 2025 at 4:04 PM
Seems like I once again got bitten by the transition controller in some very weird way causing UIKit’s doc browser controller to break.
It’s super strange, you launch to it, present your document over it in .fullScreen style, close document and try dismissing back to browser. And your app feels […]
It’s super strange, you launch to it, present your document over it in .fullScreen style, close document and try dismissing back to browser. And your app feels […]
I guarantee you, if you actually try to /use/ something in iOS or macOS, anything, you will end up with a pile of radars to file. Just pick any corner of the OS, any API, and start looking it over with a critical eye. I've filed probably a dozen radars on UIKit's Inspector panel alone 😅
August 4, 2025 at 3:40 PM
I guarantee you, if you actually try to /use/ something in iOS or macOS, anything, you will end up with a pile of radars to file. Just pick any corner of the OS, any API, and start looking it over with a critical eye. I've filed probably a dozen radars on UIKit's Inspector panel alone 😅
In SwiftUI, it might be as simple as using the .accessibilityElement(children:) modifier with the .combine accessibility child behaviour.
iosdev.space/@dadederk/10...
If that doesn't quite work as expected, try to tweak the internal views. If not, you can fall back to UIKit's three step process.
iosdev.space/@dadederk/10...
If that doesn't quite work as expected, try to tweak the internal views. If not, you can fall back to UIKit's three step process.
Daniel Devesa Derksen-Staats (@[email protected])
Attached: 1 image
Day 104. Grouping elements in #SwiftUI is extremely easy! You can use the .accessibility(children: .combine) modifier. And that's it! It merges properties. For example, generating a...
iosdev.space
December 7, 2024 at 10:13 AM
In SwiftUI, it might be as simple as using the .accessibilityElement(children:) modifier with the .combine accessibility child behaviour.
iosdev.space/@dadederk/10...
If that doesn't quite work as expected, try to tweak the internal views. If not, you can fall back to UIKit's three step process.
iosdev.space/@dadederk/10...
If that doesn't quite work as expected, try to tweak the internal views. If not, you can fall back to UIKit's three step process.
Day 3 of #100DaysOfCode
Log: github.com/webdavis/100...
🧩 Delegates allow us to Extend the Behavior of a Client (1/5)
This is why UIKit.UITableView includes a DataSource／Delegate.
Here's the architecture:
Log: github.com/webdavis/100...
🧩 Delegates allow us to Extend the Behavior of a Client (1/5)
This is why UIKit.UITableView includes a DataSource／Delegate.
Here's the architecture:
January 15, 2025 at 8:42 AM
Day 3 of #100DaysOfCode
Log: github.com/webdavis/100...
🧩 Delegates allow us to Extend the Behavior of a Client (1/5)
This is why UIKit.UITableView includes a DataSource／Delegate.
Here's the architecture:
Log: github.com/webdavis/100...
🧩 Delegates allow us to Extend the Behavior of a Client (1/5)
This is why UIKit.UITableView includes a DataSource／Delegate.
Here's the architecture:
Will SnapKit continue to live in the future🤔
I think compatibility with Figma is the key to eliminate UIKit's technical issues.
blog.foxicorn.com/ios-layouts-...
I think compatibility with Figma is the key to eliminate UIKit's technical issues.
blog.foxicorn.com/ios-layouts-...
iOS Layouts With SnapKit
Learn how to create layouts with minimum code and maximum efficiency.
blog.foxicorn.com
August 24, 2024 at 8:59 AM
Will SnapKit continue to live in the future🤔
I think compatibility with Figma is the key to eliminate UIKit's technical issues.
blog.foxicorn.com/ios-layouts-...
I think compatibility with Figma is the key to eliminate UIKit's technical issues.
blog.foxicorn.com/ios-layouts-...
new package ⚡ MenuWithAView – a SwiftUI package that lets you add an accessory view to your context menu interactions in addition to the standard menu content, using UIKit's private _UIContextMenuAccessoryView.
github.com/Aeastr/MenuW...
github.com/Aeastr/MenuW...
May 12, 2025 at 10:17 PM
new package ⚡ MenuWithAView – a SwiftUI package that lets you add an accessory view to your context menu interactions in addition to the standard menu content, using UIKit's private _UIContextMenuAccessoryView.
github.com/Aeastr/MenuW...
github.com/Aeastr/MenuW...
I guess that's probably because they want people to write serious apps for Vision Pro, and not be limited by the capabilities of UIKit.
Rather than expand UIKit's capabilities (e.g. for things like window management), which they could have done, they expanded SwiftUI, which is more future-proof.
Rather than expand UIKit's capabilities (e.g. for things like window management), which they could have done, they expanded SwiftUI, which is more future-proof.
June 12, 2024 at 6:22 PM
I guess that's probably because they want people to write serious apps for Vision Pro, and not be limited by the capabilities of UIKit.
Rather than expand UIKit's capabilities (e.g. for things like window management), which they could have done, they expanded SwiftUI, which is more future-proof.
Rather than expand UIKit's capabilities (e.g. for things like window management), which they could have done, they expanded SwiftUI, which is more future-proof.
Kind of annoying that #SwiftUI can only adapt Color.accentColor to the dimmed state (AFAIK). I made a workaround to expose UIKit's dimmed tint color to SwiftUI for this: gist.github.com/juanarzola/5...
Exposes tintColor in the dimmed state to SwiftUI. Use this to adapt any non-accentColor color to the dimmed state.
Exposes tintColor in the dimmed state to SwiftUI. Use this to adapt any non-accentColor color to the dimmed state. - EnvironmentDimmedTintColorViewModifier.swift
gist.github.com
March 17, 2025 at 9:04 PM
Kind of annoying that #SwiftUI can only adapt Color.accentColor to the dimmed state (AFAIK). I made a workaround to expose UIKit's dimmed tint color to SwiftUI for this: gist.github.com/juanarzola/5...
🎉 I just finished Day 93 of the #100DaysOfSwiftUI at www.hackingwithswift.com/100/swiftui/93 via @twostraws.bsky.social
Much better than UIKit's Auto Layout.
Much better than UIKit's Auto Layout.
March 17, 2025 at 9:14 PM
🎉 I just finished Day 93 of the #100DaysOfSwiftUI at www.hackingwithswift.com/100/swiftui/93 via @twostraws.bsky.social
Much better than UIKit's Auto Layout.
Much better than UIKit's Auto Layout.
This is the Open／Closed Principle (OCP) in action! We don't have to change the view controller to extend it's behavior.
If we want to add more behavior to the view controller, then we just add another adapter that implements the delegate:
If we want to add more behavior to the view controller, then we just add another adapter that implements the delegate:
January 15, 2025 at 8:42 AM
This is the Open／Closed Principle (OCP) in action! We don't have to change the view controller to extend it's behavior.
If we want to add more behavior to the view controller, then we just add another adapter that implements the delegate:
If we want to add more behavior to the view controller, then we just add another adapter that implements the delegate:
PSA: #swiftui gestures on iOS are super limited.
UIKit's UIGestureRecognizers, which I've almost never worked with, run circles around the few gestures we can effectively compose in SwiftUI.
Circles, I tell you!
The power of tweaking how many fingers are needed for a pan gesture, or detecting […]
UIKit's UIGestureRecognizers, which I've almost never worked with, run circles around the few gestures we can effectively compose in SwiftUI.
Circles, I tell you!
The power of tweaking how many fingers are needed for a pan gesture, or detecting […]
Original post on mastodon.social
mastodon.social
July 18, 2025 at 5:09 AM
PSA: #swiftui gestures on iOS are super limited.
UIKit's UIGestureRecognizers, which I've almost never worked with, run circles around the few gestures we can effectively compose in SwiftUI.
Circles, I tell you!
The power of tweaking how many fingers are needed for a pan gesture, or detecting […]
UIKit's UIGestureRecognizers, which I've almost never worked with, run circles around the few gestures we can effectively compose in SwiftUI.
Circles, I tell you!
The power of tweaking how many fingers are needed for a pan gesture, or detecting […]
SwiftUI's onAppear is semantically closer to UIKit's viewWillAppear, as it is triggered when a view is about to appear on the screen. Specifically, it is called after the view has completed its layout and before it begins rendering to the screen.
fatbobman.com/en/posts/on...
fatbobman.com/en/posts/on...
March 20, 2025 at 1:16 PM
SwiftUI's onAppear is semantically closer to UIKit's viewWillAppear, as it is triggered when a view is about to appear on the screen. Specifically, it is called after the view has completed its layout and before it begins rendering to the screen.
fatbobman.com/en/posts/on...
fatbobman.com/en/posts/on...
UIKit’s lineage goes back to OSX and even NEXT so of course it’s more stable. SwiftUI is being built for the future unlikely to catch up to UIKit for another ~5 years. Thats why it’s not deprecated. We can/should still use it
April 27, 2025 at 1:42 PM
UIKit’s lineage goes back to OSX and even NEXT so of course it’s more stable. SwiftUI is being built for the future unlikely to catch up to UIKit for another ~5 years. Thats why it’s not deprecated. We can/should still use it
I made a tiny empty sample app for UIKit's inspector pane API, and got three whole radars out of the same Xcode project.
So far.
😅
So far.
😅
August 2, 2025 at 9:57 AM
I made a tiny empty sample app for UIKit's inspector pane API, and got three whole radars out of the same Xcode project.
So far.
😅
So far.
😅
ICYMI, dropped a new article over on my blog...
This time, exploring how you can fill the gaps in Mac Catalyst by using native AppKit components, right in your iOS codebase, with UIKit's private _UINSView class.
sebvidal.com/blog/using-a...
This time, exploring how you can fill the gaps in Mac Catalyst by using native AppKit components, right in your iOS codebase, with UIKit's private _UINSView class.
sebvidal.com/blog/using-a...
Using AppKit in Your Mac Catalyst App
Fill the gaps in Mac Catalyst with Apple's private _UINSView.
sebvidal.com
November 30, 2024 at 9:06 AM
ICYMI, dropped a new article over on my blog...
This time, exploring how you can fill the gaps in Mac Catalyst by using native AppKit components, right in your iOS codebase, with UIKit's private _UINSView class.
sebvidal.com/blog/using-a...
This time, exploring how you can fill the gaps in Mac Catalyst by using native AppKit components, right in your iOS codebase, with UIKit's private _UINSView class.
sebvidal.com/blog/using-a...
when ios 17 dropped, i'm fairly certain that either A. apple changed something to do with temp storage cleanup time or B. something broke in SDWebImage (a library built on top of UIKit's image API) and it isn't cleaning up how it should be.
May 10, 2024 at 2:25 AM
when ios 17 dropped, i'm fairly certain that either A. apple changed something to do with temp storage cleanup time or B. something broke in SDWebImage (a library built on top of UIKit's image API) and it isn't cleaning up how it should be.
I came to the conclusion that #SwiftUI’s MapKit is not yet ready. When building out my app with the Clustering of annotations the limitations became clear.
I switched to #UIKit’s MKMapView using a UIViewRepresentable and clustering is working amazing.
I switched to #UIKit’s MKMapView using a UIViewRepresentable and clustering is working amazing.
January 15, 2025 at 11:05 AM
I came to the conclusion that #SwiftUI’s MapKit is not yet ready. When building out my app with the Clustering of annotations the limitations became clear.
I switched to #UIKit’s MKMapView using a UIViewRepresentable and clustering is working amazing.
I switched to #UIKit’s MKMapView using a UIViewRepresentable and clustering is working amazing.