I'm leaving this as rather a vague question purposefully as I think it applies throughout the area of software. For example, I have found 3 ways of doing one thing across the internet which are defined for vague usage cases, but I have a specific usage case and am staring at these three wondering which to apply?

I tend to sit there staring at all three, not knowing what to do - then doing nothing... Is there a good way of choosing? Should I try all of them?

To be more specific in this usage case for some context, I'm trying to make a very lightweight board game where I need a portion of the screen which I can rotate the board game grid, zoom into the grid, and move pieces on this grid. I had no clue how to do this, but I found things online like Core Animation, Core Graphics, Sprite Kit, and I saw arguments for and against them - for example Sprite kit is high level, but keeps the frame rate at 60, which is a waste of battery when nothing is really moving in the screen. Core Animation etc... was a lower level principle which opposes Apple's use of take the highest level of abstraction. I sit staring at these desperate for something to learn and work on as I'm only doing this out of a hobby, but I don't want to learn 3 things to use one. Is there a way I can choose and get stuck in?

I've posted this question more vaguely without code to provoke answers that are more generalised, and that's what I'd wish, but if in my specific use case you happened to know what I should use, I'm all ears, because I really am desperate at the minute! Thanks.

P.S. Could whoever knows more on this site than me post the appropriate tags? I know this is a niece question, and it neither resides on Stack Overflow nor here, but I thought here was more appropriate.

I have a specific use case, and have found 3 ways of doing it across the internet, which are defined for vague usage cases. I am staring at these three wondering which to apply.

I tend to sit there not knowing what to do - then doing nothing... Is there a good way of choosing? Should I try all of them?

To be more specific for some context, I'm trying to make a very lightweight board game where I need a portion of the screen which I can rotate the board game grid, zoom into the grid, and move pieces on this grid. I had no clue how to do this, but I found things online like Core Animation, Core Graphics, Sprite Kit, and I saw arguments for and against them - for example Sprite kit is high level, but keeps the frame rate at 60, which is a waste of battery when nothing is really moving in the screen. Core Animation was a lower level API, which opposes Apple's guidance of "take the highest level of abstraction". I don't want to learn 3 things to use 1. Is there a way I can choose and get unstuck?

I'm leaving this as rather a vague question purposefully as I think it applies throughout the area of software.