If this is something like a solitaire game then making each card its own view will simplify things for you.
I wrote a sliding tile puzzle game as my first app. It has a 5 x 5 grid of tiles. I made each tile its own view and it worked out well. If you don't make each card its own view then you'll be duplicating some of the functionality of UIView for each card. Things l like hit testing and animations to move the cards are simple if they're individual views and complicated if you have to write them yourself.
The only issue I would think might come up is drawing performance. More than 20 or 30 views might take longer to draw or animate. However, you're probably only going to be manipulating one or a few views at a time so it shouldn't be a problem.
There's a class called CALayer that is reported to give faster drawing performance than a plain view but for your first app I'd recommend staying with UIView.
|
