Building our first app

Let's start discussing the main idea of our app and how we're going to start building it. We'll call this app MGA, which is short for My Gaming History. Pretty clever, right? It will only have one screen, and it will act as the welcoming screen once the user is logged in. We'll pretend that the user has already logged into our app, so we'll only code that main screen without looking at authorization, which is a more advanced concept.

By having a clear understanding of what our screen needs to look like and describing our component's purpose, we're building a clear path to our development. In the end, if we weren't doing all this preparation, we'd get stuck during our programming, and we don't want that.

We should start by looking at our design, identifying the main purpose of it, and how to start sectioning our screen into components:

Figure 4.1 – My Gaming History's...