Back to work on my current app project. The inspiration I took from #wwdc was stick to stock everything.
I don’t normally wander too far into custom navigation or components but I’m redoing a few things to be simpler.
To be fair I had forgotten some of last years newer #SwiftUI stuff and while digging around in the developer app I was reminded of some better ways to do things.
This way when I dig into the new UI style around beta 3/4 my life should be easier.
One of the more tedious things to do with #Xcode and #SwiftUI is to set up previews for complex scenarios such as things with deep #SwiftData schemas.
Its also one of the more rewarding things. It's worth it 99 out of 100 times.
Not only can you iterate on views and components but it helps you think about your apps architecture. I almost always consider different structure to my code when I get stuck on creating a preview.
I have a question for the seasoned macOS devs.
Looks like I’ll have to redesign Cork for this next release. How do I go about redesigning it, without having to drop older system versions? I really don’t want to implement the same feature twice, once for the old design, and once for the new design.
@swiftlang There should be a ‘macOS App’ button as well! Don’t forget macOS please! #macOS #macOSDev
I restored my #SwiftData backing store via Time Machine today. Sometimes this stuff still works.
I keep corrupting the store by double clicking documents that open an older schema version from the trash. sigh.
As I prepare to release a macOS app, I'm wondering if adding Swift 6 concurrency is important enough to delay the release. Note: app seems to work fine as-is.
I haven't learned concurrency yet, so it may take a couple weeks to get up to speed.
By the way, I've been working on this client project for macOS, and it's taking me up and down the stack from launchd, via XPC, all the way to SwiftUI and back. I had to read some of the "Archived" OS X docs, and you know these are good and leave you with a "hopeful for the future of technology" kind of feeling 
.
Anyway, I'm loving every minute of it ^_^
Next Saturday, June 7, 11:30am Pacific, 18:30 UTC
Group-learning session focused on use of actors in Swift Concurrency.
#SwiftConcurrency #SwiftDev #iosDev #macOSDev
On the Swift Dev Chat Discord:
https://discord.gg/sGM552KyMn?event=1378456030488301598
When clicking a hashtag in #Oliphaunt, which behaviour would you prefer?
• System contextual menu: supports keyboard navigation, blocks scrolling
• Custom popover view: doesn’t support keyboard navigation, allows scrolling
Your feedback is much appreciated!
Upcoming online #SwiftDev / #AppleDev / #iosDev / #macOSDev events this weekend:
Coding Dojo: Learning Together Saturday, May 31, 3am Pacific, 10:00 UTC
Ensemble coding to learn more coding skills together. Working through coding kata, applying test-driven development.
https://discord.gg/sGM552KyMn?event=1375514797994545302
1/4
I'm looking for people to try out a new version of Base, my SQLite editor for macOS.
If you'd like to give it a go, send me a private message with your email address (only used for TestFlight, no junk).
Boosts appreciated.
I'm pretty happy with writing for my current client in Objective-C. Looking back, I wonder what I would need to see it thrive in the future.
Maybe better enums, tuples, better structs and maybe a better async approach than blocks or delegates.
#objectivec #swift #iosdev #macosdev
“Specifically, sunsetting our use of TCA and SwiftUI to make Dia lightweight, snappy, and responsive.”
Looks like the Browser Company moved away from SwiftUI. Personally I never used TCA but why does it lead to sluggishness?
#iosdev #macosdev #swift #swiftui
https://browsercompany.substack.com/p/letter-to-arc-members-2025
Custom notarisation has become a lot easier in the last couple of years. As a reminder to my future self, here are the steps to prepare for manually notarising an app:
#Xcode #Swift #iOSDev #macOSDev
https://iamkonstantin.eu/blog/preparing-certificates-for-notarisation/
Poll: What should happen when double-clicking a post, hashtag, user, etc. in #Oliphaunt?
Originally, double-clicking did nothing. The latest build now opens items in a new window.
For Cartographer, I redid how you move a location. The prior method was pick a point on the map and the location was updated.
The new way is drag and drop. Locations are locked by default to prevent accidental moves. Much nicer.
Probably a good stopping point for the week.
(the video is a little flashy on the map redraws)
one little mistake can prevent a lot of code from being run:
#.if os(MacOS)
….
#.endif
should be macOS. Lowercase.
oops.
easy fix once you see it.
