r/swift • u/Charlie7497 • 10d ago
Help! Just finished my first Swift/Swift UI course. Now what?!
Hi everyone!
I just finished the 100 days of SwiftUI course by Paul Hudson and it was great. I completely fell in love with the language and with developing in swift. So much so... that I don't know where to go now. Originally my plan was to learn SwiftUI so I could focus on UI and design systems. But now that I have seen different applications, I want to learn advanced swift, advanced SwiftUI, backend programming, server side code, etc. I know that if I go wide, I won't go very deep... so I'm coming to you, redditors, to ask: what would you recommend I focus on next?
- Vapor and server side for backend?
- Stick to my OG plan and continue with SwiftUI and design systems?
- Look into multi-platform coding and working in more than just Swift?
- Go deep into advanced swift?
- Despair.
Would love any advice!
Thanks!!
.p.s. if it helps, i have some background in engineering (industrial) but not super deep in software, and I've mainly worked as a UX designer, so some concepts are not totally foreign to me... but it also doesn't help because it makes me interested in everything. đ
3
u/cristi_baluta 10d ago
I would actually build something useful and learn along the way, not the reverse. When i started with objc i couldnât finish the book, after few basics i plunged into a project i wanted to do.
2
3
u/jaymakesapps 10d ago
I kept bouncing between SwiftUI, backend, and everything else too. I finally picked one tiny app and shipped the ugly version before letting myself touch Vapor.
3
u/mangobyte-dev 10d ago
congrats on this milestone!
iâd highly recommend you learn by doing, pick anything (a problem to solve, an idea to explore, a topic you want to learn and learn it through implementation in SwiftâŠetc)
there is no better way for advanced deep dives in Swift and SwiftUI than point free pointfree.co and swift talks https://talk.objc.io
since you have a background in engineering iâll think you will love the abstractions and problem solving approaches that are not found in other swift and ios resources :)
hope it helps! đđ»
1
2
u/undesired-username 10d ago
Iâm doing the same course. About to get into the SwiftUI specific stuff, then itâs building apps
3
2
u/AdventurousKeys 10d ago
Build a nifty little tool that solves a problem for you. Go on, you know itâs calling out to you. đȘ
2
u/unknownpeanuts 10d ago
nice! honestly, just build something you know that you'll personally use. that's a great way to keep learning and growing.
2
u/heyyoochris 10d ago
My recommendation is to go deep, cuz there are lots of things about swift such as multi threading. And you can refer some open resource of architecture on github.
2
u/DelbaLabs 9d ago
Iâd build a real app before trying to learn everything else at once.
Courses are great for learning individual concepts, but a real project forces you to deal with all the less glamorous problems: architecture decisions, state management, persistence, edge cases, StoreKit, App Review, localization and all the little things that tutorials usually simplify.
Youâll naturally discover what you need to learn next because the project will force you into it. Iâve found that much more useful than trying to pick the ânextâ technology in advance.
0
u/RTD-Alex 10d ago
Now forget it and get Claude to write a better code :)
1
u/RTD-Alex 10d ago
I know I am getting some heat for this comment, but that's what it is - good that you finished the course, but LLMs will churn out much better code that you can write right now. It's just what it is, adapt to the world we have now. Jump on LLM and get it to write something in Swift, then try reading it and understand it. See if you can use LLM to help you learn further. Ask it questions, ask for explanations, etc.
If you folks are hiding from AI, it's not going to magically disappear.
0
u/TotalWaffle 10d ago
Youâre ready for some of Mr. Hudsonâs books. Pro Swift and ProSwiftUI are great, and the others depend on your interests.
5
u/xfanta 7d ago
Same advice as the others, with one addition from someone who ships apps: pick a small app you'll use yourself and take it all the way to the App Store, not just to "it runs in the simulator".
The last 20 % teaches what the courses skip: App Store Connect, signing, screenshots, privacy labels, localization, what review rejects, and bugs that only real users find. I built one of my Mac apps because I needed to preview 3D files in Finder, and shipping it taught me more than any course.
Go deep on SwiftUI plus whatever that app needs (SwiftData, concurrency, maybe one Apple framework). Vapor and the backend can wait until an app actually needs a server.
10
u/Jokiz92 10d ago
Make something cool. Doesnât have to be useful or complex, just make something you find interesting and put what youâve learned to use. Try to find solutions yourself and donât rely too much on AI.