I’ve been playing with the TestFlight build and it’s really solid. Can you share any under the hood details of how the system is able to accurately map the loose prompt to fully native SwiftUI components. Mostly curious because I’d love to also build internal data dense apps typically better suited for desktop.

Great work and I hope to become a paying customer soon!

▲

jacobx 9 days ago | parent [-]

Yeah, the prompt is just asking Claude to generate a SwiftUI iPhone app. The recent models have been able to generate really good Swift code, so we just have a set of best practice instructions we've been accumulating (telling it to make an app with @main, pointing it to/away from some APIs, encouraging it to persist things in UserDefaults, etc).

I think most of that would work pretty well for making SwiftUI desktop apps too.

	▲	w10-1 9 days ago \| parent [-]
		It would be lovely if the community had this knowledge about API's to avoid and approached to adopt. SwiftUI programming is a tightrope walk of stuff that works over a chasm of time lost to testing.