Hello, after i written 500+ characters long boring story, i decided to go with a simpler and easier approach.

I require a tutorial / (example made) to 2d graphics pipeline tutorial, i want to learn how to draw stuff, how textures should be applied/used/managed, and what to do in what order to achieve fastest drawing.
Essentially i am unsure how to manage my objects, i don't know what sizes of my textures should be, should i when drawing, force to draw stuff that requires current texture, or can i freely switch back and forth textures and not worry about it, and much more.

What i just want to know is how to manage my "Entities" and how should i handle their drawing.

If you could suggest a tutorial that explains stuff noted above, i would be gratefull!

What i currently will face is:

//Draw 8 vertices with texture1
//Draw 24 vertices with texture2
//Draw 8 vertices with texture1
//draw 4 vertices with texture3
//Draw 8 vertices with texture2
//Draw 16 vertices with texture2
//Draw 24 vertices with texture1
//draw 8 vertices with texture3

I got few ideas for optimization, but as i stated in the topic name "i just figured out i got no clue what i am doing"

I was working on an iOS game and found that sprite batching made a huge difference in performance. Keep in mind I didn't try sprite batching until I found it to be a bottleneck.

For sprite batching you pack separate images into a single image then define texture coordinates that 'cut' out the image you want from the packed image. When drawing your scene, you create a single vertex buffer that contains all of the images you want to draw. You need to move and rotate the points of the quad you are drawing on the CPU before putting them into the vertex buffer.

You wont want to batch all draw calls, just the ones that make up the largest portion of your sprites. The most obvious one is a tilemap. If your scene contains hundreds of tiles, you don't want each tile to consume a draw call. Instead, you put all of the tiles into the same image then create a vertex buffer that contains all of the tiles. This way you can draw the whole map in a single draw call.

On mobile platforms, it is even faster to repopulate a vertex buffer every frame from pre-transformed data generated on the CPU than it is to have hundreds of separate draw calls.

The disadvantage to this approach is it can complicate your drawing code and you have less control over draw order. If you still need to enforce a specific draw order you can simply use a depth buffer and have the z component of each vertex determine the draw order.

Thank you on suggestions.