At Insight, we pride ourselves on our ability to create custom solutions that exceed customer expectations. We often design and develop apps in unison for the two major mobile platforms: Android and iOS.
On occasion, a client will have a specific request for both platforms to look and feel identical. Our designers and developers collaborate to conceptualize and create a custom solution to meet the client’s expectations. On one occasion, we were asked to create a login screen that looks and functions like the iPhone lock screen. Here’s how we did it.
We created the Android Login Pad. The pad is similar to the iOS 7 lock screen in that the pad circles and numbers swap colors as the user presses them:
Once the required length is met for the login pin (constant defined inside the activity), the login button animates in next to the pin field:
Note: This section assumes the user has some amount of Android development experience to understand the terminologies and code examples.
Toggling button colors
The color changes on the button presses are done through the use of pressed states and resource drawables. Each button on the pad has its background set to:
This drawable is an XML file found in the res/drawable folder of the project, and it looks like this:
As you can see, the state for pressed calls another drawable, appropriately named ‘login_pad_circle_pressed.’ This drawable creates a circle with a white background and a 1dp border. It looks like this:
Also, the default state calls a third drawable (login_pad_circle_normal) that makes the background blue, with a 1dp white ring to break up the look of the circles on the pad. It looks like this:
The main activity of the app implements the View.OnClickListener, and each button has its own touch listener set to the activity:
Implementing the View.OnClickListener gives us access to the onTouch override, where we toggle the buttons based on the pressed state:
When the on press occurs, we pass the view object and the motion event to the toggleNumberColor function so we can update the text color accordingly. On a down motion, the font is blue to contrast with the white background, and on an up motion press, it’s white to contrast with the blue background:
Note: the button backgrounds are toggled via the drawables we mentioned earlier.
The animation resources reside in the res/anim folder. Each animation (in and out) has its own resource XML. For brevity, we’ll only reference the slide-out animation. The slide-out animation moves the object it’s assigned to from its current X position to the right and off the screen, in the amount of time defined (in milliseconds) in the duration tag:
To make the animation available to an object in the activity, we need to declare:
and instantiate it in the activity:
Once we have the animation object available, all we have to do is call startAnimation() and pass the animation in on the object we want animated. In this case, we’ll use the login button:
Finally, if we want to chain events together after an animation, we can make use of the animation listener on the animation object. For this discussion, we’re cross-fading the “delete” text out of view after the login button is pushed off screen. To make use of the listener, we just set a new instance of animation listener on the object:
The listener gives us a few overridden methods we can make use of: onAnimationStart onAnimationRepeat onAnimationEnd. For cross-fading the delete text off the screen, we’re making use of the onAnimationEnd:
This article originally appeared on Nov. 19, 2014.