Duncan Babbage

@babbage@iosdev.space
467 Followers
527 Following
1.4K Posts
Senior Mobile Engineer at Basis. Indie dev of https://intro.app, a personal CRM tool for things you want to remember, for iOS, iPadOS and macOS. Cognitive accessibility++. PhD fwiw. Auckland, New Zealand. he/him
Indie devhttps://intro.app
Githubhttps://github.com/babbage
Stack Overflowhttps://stackoverflow.com/users/842106/duncan-babbage
Profilehttps://about.me/babbage
Duncan Babbage13h ago
daniel:// stenberg://21h ago

Death by a thousand slops

https://daniel.haxx.se/blog/2025/07/14/death-by-a-thousand-slops/

#curl #AI #bugbounty

Death by a thousand slops

I have previously blogged about the relatively new trend of AI slop in vulnerability reports submitted to curl and how it hurts and exhausts us. This trend does not seem to slow down. On the contrary, it seems that we have recently not only received more AI slop but also more human slop. The latter … Continue reading Death by a thousand slops →

daniel.haxx.se
Duncan BabbageJul 7
Colin CornabyJul 6

I wrote about my experiences using LLMs + Claude Code. Both the good and bad. These tools can cut both ways on efficiency. But my biggest concern is I'm worried developers won't know when to put them down. One takeaway I have: devs who use LLMs should have a surface understanding of how they work.

https://www.colincornaby.me/2025/07/llm-coding-and-the-sunk-cost-fallacy/?utm_source=mastodon&utm_medium=jetpack_social

LLM coding and the Sunk Cost Fallacy

On my weekends I’ve been going through LLM coding workflows. I’ve used web assistants like ChatGPT and full integrations like Claude Code.

Random Thoughts
Duncan BabbageJun 30
too many namesJun 30

Well that's definitely an interesting choice from Microsoft

https://support.microsoft.com/en-us/account-billing/changes-to-microsoft-authenticator-autofill-09fd75df-dc04-4477-9619-811510805ab6

Changes to Microsoft Authenticator autofill - Microsoft Support

Duncan BabbageJun 23
Steve Troughton-SmithJun 23

The great part about iPad's new windowing model is that you can't hide from it if you're a developer. Users are going to window your apps, layouts are going to be resized, and your menu bar is going to be investigated.

The menu bar API, which is shared with Catalyst, should be your first port of call, as it's something that apps shipping today, built with the older SDKs, now show in the OS. There are plenty of iPad apps that never filled out their menu bar, and you can/should fix that right now

Duncan BabbageJun 19

I wonder if those #iOSDev indies who adopted version numbering of 2025.1 etc are having buyers remorse they didn’t go with 25.1 so they could now match the operating systems.

Non devs won’t know that you can iterate app version numbers on the App Store however you like, with the one limit that the number can only ever *increase*. So adopting a 202x.x numbering scheme is forever. No backsies.

Duncan BabbageJun 18

This might be a case where Sherlocking is a blessing. I’ve thought for years that macOS should probably have a clipboard manager, but I’ve never taken action despite knowing that third party options exist. Once I get my first use free, I might want the harder supply.

From: @simonbs
https://mastodon.social/@simonbs/114706031280599276

Duncan BabbageJun 17
I’ve seen in app purchase pricing that looks pretty bad but this takes the cake. Hey #iOSDev don’t put a price in one currency in your in app purchase name as it may cause you problems on the App Store in other locales.
Duncan BabbageJun 13
Joe Rosensteel 🏳️‍🌈Jun 12
I can’t believe that none of the tech journalists have used the headline “Apple Will 86 Intel Next Year”
Duncan BabbageJun 11
Got a `dyld_shared_cache_extract_dylibs failed` error in trying to prepare for building to a physical iPhone running the iOS 26 developer beta? Turns out, might not be a complex Xcode 26 beta bug. Could just be Sparkling Lack of Disk Space on your Mac. 🤦🏽 #WWDC25
Duncan BabbageJun 11

Apps built with Xcode 16 when run on the iOS 26 Beta still display iOS 18 chrome, even when that app with unmodified source code converts to Liquid Glass elements when built with Xcode 26.

This should cut down a lot on developers getting bug reports from general users who install iOS public betas and then find the Liquid Glass implementation isn’t complete yet in your app… though they might send general “please update to Liquid Glass UI” requests I guess. #WWDC25