Simon B. Støvring

There are so many things to build as part of this project. I just spent a few hours building a custom font picker 😀

That’d be a harsh immediate response. I’d expect a warning first.

On App Store Connect, there’s this trick where a zero-width whitespace character can be inserted into an app name to claim an otherwise taken name. I just verified that it works.

What’s people’s experience with this? Have you tried it? Does it even get past app review? Bad idea?

This project forces me to build some of the most advanced UIs I've ever built, and I enjoy it so much.

* A text editor is also quite advanced, but not in the UI, really, it's more in the internals.

teamData | Apple Developer Documentation The collection of data an app uses to hold private team information during drag and drop.

Got it! teamData on NSItemProvider seems suitable for storing information about a local object. developer.apple.com/documentatio...

Alternatively, have anyone found a way to associate a local object with adrag and drop operation and reference that object in your implementation of DropDelegate?

Have anyone found a reliable way to detect a drag and drop interaction being starteed on a SwiftUI View with the .onDrag(...) view modifier?

Mac Power Users #808: "The Momentum is Building," with Simon Støvring - Relay Simon Støvring is the developer behind some fantastic apps, including Runestone, Scriptable, Jayson, and Data Jar. This week, he joins the guys to talk about how he works on these apps, his use of Apple's default apps, and how he's thinking about iOS 26.

Super excited to join the Mac Power Users this week! David, Stephen, and I talked about WWDC, iOS 26, and a few of the apps I’ve been building. Listen here: www.relay.fm/mpu/808

I have it disabled too but my auto-conplete is often so slow that it’s useless. Restarting Xcode seems to fix it for a short period off time.

Ugh, I have the AI suggestions disabled, though. They’re utter useless.

😢

Xcode's auto-complete has become so unreliable on my machine over the past year or two that it is practically unusable. I'm hoping that it will get better when I upgrade from an M1 Pro, but who knows at this point.

Me wearing t-shirt and hoodie branded with the circus’ logos in front of the big circus tent.

I'm incredibly excited to spend the next few vacation days volunteering at a circus!

I envy every iOS developer who hasn't had to deal with the UndoManager API.

I'm wasting so much time getting drag and drop working properly with SwiftUI for this project. I don't think the .draggable(...) APIs can do what I need, so I've dropped down to UIKit, but even then it's such a mess to get working properly with SwiftUI 😩

It's how I use it 90% of the time. Although, after Apple has introduced Coding Assistant it has messed up my keyboard shortcuts so this summer has been rough.

My desktop with a Studio Display and a MacBook Pro. Running Xcode. In front of the display is a glass of red wine. On the desk is also a trackpad, a keyboard, and a mouse along with some LEGO.

Friyay 👨‍💻🍷

I've been making great progress on this project today. There are still a number of key interactions that I need to implement before I can show off anything, but I'm slowly getting there 😀

Screenshot of some example code that attempts to achieve what I'd like.

Is there a way to use a custom App Entity type in an App Intent but have it show as a plain text field in the Shortcuts app? I can handle converting to and from a string myself.

I looked into resolvers but they don’t seem to control how input fields appear in Shortcuts.

A key part of this app involves generating both in-app UI and Shortcuts actions (nay, App Intents) from my Swift models. That’s why I’ve been diving deep into Swift macros over the past week.

If we're OK with forwarding the value to another object, we can also just reference a private Observable class inside our property wrapper.

I'd use a macro to make MyModel conform to ExampleObservable so I don't have to think about those ugly _example_access(...) and _example_withMutation(...) functions, of course.

Swift code snippet showing how a property wrapper can be applied to a property while ensuring it remains observable.

Here's a decent workaround, but it’s frustrating that `count` must be annotated with @ObservationIgnored when it is, in fact, observable.

The property wrapper invokes access(…) and withMutation(…) and ExampleObservable exposes those to the property wrapper.

Ugh, I really want to apply a property wrapper to a property that's also made observable with the @Observable macro, alas 😔

🔴 Property wrapper cannot be applied to a computed property

Screenshot of a class named "MyModel" with no properties and the @Observable macro applied, comparing the code from Xcode 16 and Xcode 26 beta 3. It shows that there is vastly more code being generated in Xcode 26.

This took me by surprise. The code generated by the @Observable macro in Xcode 26 beta 3 is noticeably different from what Xcode 16 produced.

Nah.

I’m working on a new Shortcuts-focused tool. It’s not like Scriptable, but it plays in the same space. I’m still wrapping my head around the idea, but I’m incredibly excited. Looking forward to sharing more and hearing if it makes sense to anyone but me 😄

This is why I love cycling. Even while suffering, Evenepoel handed his bottle to a young fan. Look at that smile. He’ll remember this for the rest of his life. In cycling, you get close to your heroes, and they so often choose to act like heroes, even in their toughest moments.

Screenshot of Swift code showing an empty implementation of app intent along with the error from the post.

I’m SO close to generating entire app entities and app intents from models. The last blocker is generating `parameterSummary`.

I keep getting:

"The property 'parameterSummary' must have a compile-time static value and cannot be computed or dynamic"

No idea how to solve it.

Xcode showing a Swift file where an AppIntent is defined using a macro, with a build failure in the report. The error reads: “Static extraction builder failure: The file ‘@_swiftmacro_13PlaygroundKit7Example18AppIntentGeneratorfMe.swift’ couldn’t be opened because there is no such file.” Build fails at the Package PlaygroundKit step.

Noooo! Tried using a Swift macro to generate an App Intent and Xcode fails to compile because it can't find its own generated file (I think?). Tested in Xcode 26b3 and 16.4. I really needed this to work for my new project 😢 (FB18843876)

Example project: github.com/simonbs/App...