For a recent exercise, I messed around with shared element transitions in Android. This type transition is useful for selecting an image from one view that will be shown in another.
With both iOS and Android sporting similar apps and features, it's creative design and clever animations that's driving competition between the platforms. Each platform is constantly updating with powerful tools and components to make up-to-date mobile apps really stand out. With the intense competition in the app stores and waning apathy of users, developing something striking is critical.
It takes an experienced creative developer to handle this challenge, which is a role I've held for the last six years. I'm an Android UX developer.
I learned a very cool method over the weekend which should make managing image resources for my Android apps much more streamlined. Adobe Generator adds asset organization into Photoshop layers, dramatically simplifies the process for creating images, and resolves common human errors.
After working on Android widgets for the last two years I've learned a lot about limitations, inconsistencies, and ghostly parameters in Android XML layout files. Some parameters are simply "overly clever" so I'll offer some standard settings you should use. These suggestions will also help you effectively reduce the plethora of nanny nag warnings in the IDE.
These come in handy so take a moment to review.
While I was working on my first Android app, I found 9-patch (aka 9.png) to be confusing and poorly documented. After a little while, I finally picked up on how it works and decided to throw together something to help others figure it out.
Basically, 9-patch uses png transparency to do an advanced form of 9-slice or scale9. The guides are straight, 1-pixel black lines drawn on the edge of your image that define the scaling and fill of your image. By naming your image file name.9.png, Android will recognize the 9.png format and use the black guides to scale and fill your bitmaps.
Here's a basic guide map: