Ryan Ashcraft

@ryanashcraft
1.6K Followers
408 Following
2.2K Posts

Good list. I'll add one: make "unsubscribe" links from TestFlight emails remove notifications, not send an email to the developer.

https://mastodon.social/@lapcatsoftware/116318583217133000

dear apple. when i want to choose another card, i will ALWAYS tap the top thing. always. i will never tap the second thing. please fix. thank u love u
Foodnoms as a native Mac app is coming along nicely. What do you think?
How a Layoff and an Ice Cream Bet Launched 2 Indie Apps — Adrian Eves, Pediapal & Auralog

YouTube

It is a bummer because I was banking on these issues being fixed by now.

I have a huge Foodnoms update that is almost ready, but I can’t ship it, because it would break syncing with the Mac app.

I could load up Sequoia and Xcode 16.4, but Apple is going to stop accepting binaries from 16.4 in April. And the UI compatibility plist option isn’t any better. It’s ugly AF.

Mac Catalyst seems dead to me. Five months since Tahoe’s official release and I still have crashes, ugly layouts and glitches that weren’t a problem pre-Liquid Glass.

I see no option other than build an entirely new SwiftUI-native Mac App.

In SwiftUI, if I'm using ScrollViewProxy to scroll to a particular anchor in a List, is there any way to have it take the top contentMargin into account?

Every time I scroll to an item, it ends up behind the top toolbar 😞

Happy payday to my fellow app developers 💰
@ryan it builds, installs, sets some user defaults and mutates the SQLite DB to set up the test. Then runs in Simulator, takes screenshots, analyzes the contents of screenshots to confirm expected text values, uses XcodeBuildMCP to interact with the Simulator and perform various actions - then repeats with a newer build to confirm no regressions. Records results in a markdown file. Repeats for 40+ different scenarios. All autonomous.

I dream of Apple investing more into the iOS simulator (instead of continuing to pour energy into Xcode previews which are still unusable for me).

1. Provide robust, first-party MCP support for interacting with the simulator.
2. Full iOS virtualization instead of a simulation to minimize number of differences between device and simulator.