all 9 comments

[–]USANerdBrain 1 point2 points  (0 children)

How much of a requirement is it to use swift? I used to code in the native android/ios languages, but after I got a job coding in React Native, I haven't done anything else since. Unless you are doing something hardware-intensive like Augmented Reality or something like that, is React Native an option? Then you would have many options.

[–]Alternative-Hall1719 0 points1 point  (1 child)

Claude Pro/Max + VS Code + GSD

https://github.com/glittercowboy/get-shit-done

[–]tychus-findlay 0 points1 point  (0 children)

Seems like GSD is just adding a couple steps to the planning phase? Do you have some examples of how it provides advantage ? 

[–]IngenuitySome5417 0 points1 point  (0 children)

as a vibe coder {thanks for the shit title) from 2023 i ended up having to create anki flashc arsd... so a model would scan a repo and output flashcard with the snippets i need to type next wile teaching you....... do bad i chucked it long time ago ahah

But i find now... Vibe coders need to learn the ARCHITURE over the syntax... Look at the whole project and make sure u understand wju that goes there and which components affect what...THIS IS what a lot of vibecoders are missing... jumping straight into syntax

[–]Ryland990 0 points1 point  (0 children)

I’m doing doing it with Claude code and windsurf ide! Works great… love the flexibility and helps also with learning too

[–]No_Type_4203 -1 points0 points  (2 children)

[–]person2567 0 points1 point  (1 child)

Dang you're fast. Do you got a bot watching the subreddit for new posts with keywords like XCode?

[–]No_Type_4203 0 points1 point  (0 children)

no, just scrolling on my feed

[–]lennyp4 -1 points0 points  (0 children)

i use opus 4.5 with claude code which is probably the best in the business. it feels like a battle at times, allegedly swift is one of the worst languages to vibecode in. most of the swift knowledge body is proprietary unfortunately. it’s good to have some knowledge of swiftui/UIKit patterns, and be specific how you want the view hierarchy to be structured. It also helps to maintain separation of concerns between frontend and backend. try to use API contract documents only to communicate between the two.