Forgive me if this has been asked / answered before but I couldn't find an answer that deals specifically with what I'm asking.
I've been designing an app alongside my wife that's quite image-heavy. Basically it's a character creator of sorts, allowing you to choose hair, clothes etc.
The way I designed it was a bit primative. Each "hair" for example is stored on a different direction of an animation, so each time you choose a new hair, it just points the object to a different direction. So 32 directions X around 6 different animations would mean 192 directions each with an image on it on a single object. It seemed like a good idea at the time but now i'm not so sure!
Problem is, the sheer amount of directions per object is causing a bit of slowdown when exported to android.
Would it have been a better idea to have had hundreds of hair objects separately and simply load each one in when the button for it has been pressed rather than a single object with hundreds of directions?