10
4
u/Cayenne999 Jun 26 '20
P o w e r O v e r w h e l m i n g
3
u/_reykjavik Jun 26 '20
The swarm being the bugs, unity being stackoverflow and ultralisk being bugs that ultimately take you down
2
2
2
u/cwbrandsma Jun 26 '20
Heck, that is me when I realize the phone has to be on iOS 14 for much of that to work...when a good chunk of my users are on iOS 9 still.
1
1
u/Ezra_Black Jun 26 '20
Relax everyone. Keep learning! Companies sometimes take years to integrate new features and the foundations of swift are still strong!
1
1
1
1
0
Jun 26 '20
[deleted]
46
u/GTR128 Jun 26 '20
I just started Angela Yuâs course yesterday. Iâm assuming the new stuff will come easier if you have a decent grasp of the older material/basics. Hopefully.
26
u/_Bad_Dev_ Jun 26 '20
Angela Yu's course is awesome 100% reccomend
4
u/depicc Jun 26 '20
Yeah definitely a lot of beginners like myself enjoyed that course. Beautifully paced.
4
u/toepicksaremyfriend Jun 27 '20
I loved her courses. Sheâs very good at explaining things, and as a bonus, her accent is awesome.
9
1
u/Electrizendo Jun 27 '20
The one on Udemy?
4
u/Snoop8ball Beginner Jun 27 '20
I think thereâs two different version, the one on Udemy, and the one on her website, AppBrewery. The one on Udemy usually has more sales, so buy the one on Udemy. Plus you do a refund within 30 days if you donât like it.
2
u/GTR128 Jun 27 '20
Thatâs it. Udemy has sales all the time so just keep an eye out for one and you can probably get the course for around 10-15$ I think.
2
13
u/zivaviv55 Jun 26 '20
Same. I want to start learning iOS but there seems to be so much of everything and no clear start point :(
6
u/mmnml Jun 26 '20
Start by building, even as an experienced dev my approach to WWDC is "oh this looks cool / this is something I actively work on, let me learn more about this topic"
Apple provides a huge amount of tools to work with their hardware and ecosystem, but it doesn't mean you as a developer HAVE to learn it all :)
3
u/Xaxxus Jun 27 '20
Right now is a very strange time to start iOS development.
There was one major transition in iOS development in the past (when swift first came out). Right now weâre in the middle of the next major transition (UIKit -> SwiftUI).
In a few years, UIKit code is going to be the objective C code of today. Everyone has it, and nobody is going to want to touch it.
5
0
12
u/carbonatedbeans Jun 26 '20
All the new changes to SwiftUI are additive, so all previously written SwiftUI code or tutorials still work great. Iâd recommend checking out Paul Hudsonâs 100 Days of SwiftUI, starting on day 60 or so he starts getting into integrating UIKit with SwiftUI, and how to use MapKit. He also goes over how to use a workaround for if let (it wasnât previously supported), but now SwiftUI now has both maps and if let. Iâd skim over whatâs new in SwiftUI and trying to integrate that with what youâre learning.
2
u/treitter Jun 28 '20
I started learning iOS development 18 months ago and launched my first app a few months ago. Hereâs my advice.
Getting into it this late can be really intimidating. Stick with it and some day you will suddenly realize youâve got a decent handle on the basics.
Donât bother with Interface Builder. Do everything programmatically. You can only do some things programmatically, IB obscures important details, and IB makes a mess of your git commits (especially if you have other team members working in parallel branches). If youâve already got some UI laid out in IB, leave it as it is. You can redo it later if needed.
The way layouts work on iOS are different than the other few UI toolkits Iâve worked with (which are mostly similar to each other). Theyâre unintuitive but they will eventually click with enough experience. Just expect to have some frustrating sessions trying to understand why your layout doesnât work the way you expect. Thereâs probably some flag youâre not yet familiar with.
Some of the most common views have special behavior depending on their parent view. When you want to add a child to a view, you add it to the subviews. Unless itâs a UIStackView, in which case that will quietly not work like you expect. Add them as an arranged subview.
Always include âswiftâ whenever you look up any tutorial. If itâs not in Swift, itâs outdated in at least a few ways.
Donât bother with SwiftUI for the next couple years (or any other brand new component until itâs had a few major releases). This means you wonât get featured in the App Store but you werenât going to be anyhow. The upside is youâll save yourself a lot of headache dealing with unpolished API and UI in Xcode.
Good luck!
2
u/P5YCH0D3 Jun 26 '20
If you have any question donât be afraid to reach out to me, Iâll help you where I can or we can learn together.
0
Jun 26 '20
[deleted]
9
u/mmnml Jun 26 '20
Anything specific from WWDC that makes you feel that way? I don't make use of 90% of what's discussed in the talks, but its cool to know its out there and resources are available if I want to dive in!
0
Jun 26 '20
[deleted]
7
u/mmnml Jun 26 '20
Oh for sure, its very exciting! SwiftUI feels very much in its infancy still, but I'm keeping a close eye on it. Love everything about Catalyst and ARM Macs. Xcode looks to be getting better (fingers crossed..)
I wouldn't feel like you're missing out..I know iOS devs still supporting insane legacy code and older iOS versions. So in a way you're already ahead of what they work on every day :D
41
u/monkeydoodle64 Jun 26 '20
WWDC is not where you start learning iOS. Its where you stay ahead.