The FoodTruckModel implemented in the Apple’s code example in my opinion can be called Model as Apple is doing; that’s because it is exactly what it is, the Model of the screen. Then, inside the model, several entities describing the different data structures are coexisting. I want to say this model is also implemented as a Façade pattern.
Yes. It is a kind of a Facade that provides data to the entire application. Apple is using a single Model but we can always add more Models for larger apps. Those Models should created based on Apple boundary and not because we added a new screen.
Good one. need more session like this.
code?
The FoodTruckModel implemented in the Apple’s code example in my opinion can be called Model as Apple is doing; that’s because it is exactly what it is, the Model of the screen. Then, inside the model, several entities describing the different data structures are coexisting. I want to say this model is also implemented as a Façade pattern.
Yes. It is a kind of a Facade that provides data to the entire application. Apple is using a single Model but we can always add more Models for larger apps. Those Models should created based on Apple boundary and not because we added a new screen.