Planning data flows in the app

This is a part of app development that usually does not fall under the responsibilities of the frontend developer. The clients will often determine what data they want, and that data is organized by the backend developers. However, if you can participate in the way the data flows are organized, you will make your future work easier. Given that we are only building the frontend of an app using example data, we are free to organize it however we like.

We will use the design file again, as the basis for what work needs to be done. Starting with the Home screen, we know we need a list of users and a list of items to be displayed on the Home surface. As per the Conversations surface, we will need a list of conversations with respective usernames and messages. We will also need data for each one of the conversations, so we can display it on the Messaging surface. On the Profile surface, we will need a list of data pertinent to the user (name, avatar image...