ok.... I will agree to totally disagree with you....
I've been reading up on MVC(ModelViewController) design implementation, which is a necessity especially in iOS development. It allows high-reusability, ease of debugging, quick modifications.
Essentially a card might have a graphic property. But let's say I have the cards shimmer every few seconds. The controller should be doing this shimmer to the View and it should have nothing to do with the card class itself.
This way if I change how I want the UI to act or what it should look like, nothing in the card class changes. The controller just changes how it has to view draw/animate the card.
Also lets say I have a desktop version, phone version, tablet version. I wouldn't (and shouldn't) need to edit the card class. It should fundamentally be the same across all of the versions. The only thing that changes is how my Controller decides to relay that information back to the user based on their hardware for example.