Good day, everyone, and welcome back. Welcome to section 17.
In this section, we're going to review our code and the behavior of the app
to make sure everything's working as it should.
This is something you should get into the habit of doing
before releasing an app to the Play Store.
In an ideal environment,
you'd have a code review whenever you create a new class
or make changes to an existing class.
Explaining to another developer why you've done things in a certain way
and having them review your code really helps to improve the quality
of your code.
If you're working as a sole developer though,
you won't have the luxury of code reviews with other developers.
You also won't have a test team, it's just you.
That doesn't mean you can skip the reviews.
It just makes things a bit harder
and needs more discipline on your part.
Android studio can really help here.
It's getting better and better
at making suggestions about the quality of your code.
The android framework also helps
and identifies potential resource leaks.
Google have made quite a few changes to the framework class functions.
They've annotated the methods and parameters
to make them more Kotlin friendly.
That's caused some of our code to give errors or warnings at least.
You've probably been fixing those as you went along,
but we'll review them in this section.
We're going to review the code in our app to spot potential problems
then look at a few improvements we can make.
So let's get started. See you in the next one.