You've just finished a massive project, and regardless of how much you have learned you deserve kudos for all your patience. This project required you to follow several long steps before you could see your code run. I hope it was worth it, and I hope in retrospect that you can see why all the code was needed.
Along the way, you've learned all about SKShapeNode
, AVAudioPlayer
, physics speed, CaseIterable
, removeFirst()
, action groups, and more, so you're several steps closer to your goal of being an experienced Swift developer. Well done!
Anyone can sit through a tutorial, but it takes actual work to remember what was taught. It’s my job to make sure you take as much from these tutorials as possible, so I’ve prepared a short review to help you check your learning.
Click here to review what you learned in project 23.
One of the best ways to learn is to write your own code as often as possible, so here are three ways you should try your new knowledge to make sure you fully understand what’s going on:
createEnemy()
method. Instead, define them as constant properties of your class, giving them useful names.SPONSORED Take the pain out of configuring and testing your paywalls. RevenueCat's Paywalls allow you to remotely configure and A/B test your entire paywall UI without any code changes or app updates.
Sponsor Hacking with Swift and reach the world's largest Swift community!
One of the most effective motivators of success is sharing your progress with other people – when you tell folks what you're doing and what you've learned, it encourages you to come back for more, which in turn will help you reach your app development goals faster.
So, now that you've done all the hard work it's time to share your success: tell folks that you've completed this project, either by clicking the button below to start composing a tweet, or by writing your own message from scratch. This will definitely encourage you to keep learning, but it will also help other folks discover my work – thank you!
Link copied to your pasteboard.