You seem to be confusing "programming" with "design". Those are two completely different processes, and it's important to do them in the right order. Design first, program later.
And everything Peter said was about designing your application, not about programming it. Design is the process where you decide what you want your application to do (the first phase) and then where you decide how your application is going to do that (the second phase). Typically there aren't tutorials about how to do design because it's rather a generalized process. You certainly aren't going to find a tutorial about how to design the particular application you have in mind. Have a look at the Wikipedia article
Systems design to see just how far from programming it is.
For a more specific example: when an engineer decides to build a road, the first step is not to fill a concrete mixer with concrete powder and
water. The first step is to decide where the road is going to go; pouring concrete comes much, much later.
If you're new to programming you are probably unfamiliar with the design process. If you re-read Peter's reply you'll see that there a lot of things you have to consider. It seems to me that quite a few of those might be beyond the scope of beginning programming. That means you're going to be handicapped in designing your application because you don't really have any idea of what's possible and what's not, or what's hard and what's easy. But anyway... you could certainly start on a design. Maybe what you come up with won't actually be feasible, but you could say that's part of the learning process. So get out your paper and pencil and start drawing pictures of where the data goes, where it's stored, and things like that.