Refactoring our Restaurants app to fit a presentation pattern
We plan to refactor our Restaurants app to fit a presentation pattern. From our previous comparison, we can consider that MVVM is best suited for our Compose-based app. Don't worry—we will talk about this decision in more detail a bit later.
But before we do that, let's add more functionality inside the application to better highlight how mingling responsibilities can lead to unmaintainable code.
To summarize, in this section, we're going to be doing the following:
- Adding more functionality inside our Restaurants app
- Refactoring our Restaurants app to MVVM
Let's begin!
Adding more functionality inside our Restaurants app
When the Restaurants application is launched, the RestaurantsScreen() composable is rendered. Inside this screen, we are loading a bunch of restaurants from the server, and then we're displaying them to the user.
Yet while our app waits for...
