This is the second part of the “Managing Assets” series of posts and deals with asset naming. If you missed the first part, on asset quality, you can find it here.
Asset naming conventions reflect a really simple concept: How to name assets, or parts of assets. However, when it comes to adhering to those conventions, it’s anything but easy. Read More
Today I’m going to talk about the way we work with assets here at Total Eclipse. This first post on asset management will discuss quality, forward planning, and balance.
Maya’s Dress Up is our most recent game, available on iOS devices. It’s a dressup/make over game where the player gets to style up Maya and her friends, using various clothes and accessories. Because we believed that players might like to publish their creations, we included sharing features, such as Publish on Facebook and Email to a Friend, ever since v.1.0.0. The player has been able to send an email to a friend, attaching a screenshot of an outfit she had created, along with a URL to the game’s website.
As part of our next game update, we wanted to let players import an outfit that a friend had sent them. In other words, if the receiving player had the game installed on her device, she could import the styling selections of her friend directly into the game.
The easiest and most obvious way to do that was to use Custom URL Schemes.