The buttons in your app should load the screens expected of them. This video challenges you to create screen classes.
Now that we've talked all about routes … and the static keyword in detail, … let's finish off the work that we started with the routes. … And I'd like to pose that to you as a challenge. … Can you create static IDs for all of the remaining screens … and replace the strings in our main.dart file? … Similar to how we've done it with the welcome screen. … And as part two of the challenge, … I'd like you to take a closer look at the welcome screen. … Notice that there are two buttons. … At the moment the buttons do nothing, … but needless to say that the top button should send users … to the login screen and the other one should send users … to the registration screen. … As part two of this challenge, … I'd like you to implement this functionality. … Modify the code in the welcome_screen.dart file … so that when a user presses a button, … they can navigate to the corresponding screen. … I'll give you a few seconds to pause the video … to complete the challenge. … Ready? … Here's the solution. …
This course was created by London App Brewery. We are pleased to host this content in our library.
- Refactoring routes
- Customizing Flutter animations
- Setting up a Firebase project
- Authenticating users with FirebaseAuth
- Streaming data from Firestore