Profile cover photo
Profile photo
Avinash Ananth Narayan R
Avinash Ananth Narayan's posts

Since one on my question asked during the latest Reddit AMA, is not (going to be) answered, I'm going to repeat it here.

How can we use ConstraintLayout with CoordinatorLayout?
i.e., will there be a Helper class with the feature of ConstraintLayout (or CoordinatorLayout) which can be used to mix-and-match features.

Given that the helper pattern is used in percent layout support, this will also be a nice functionality.

+Android Developers+Ian Lake​

Post has shared content
Looks like this should be hung up everywhere.

What would be the preferred way to introduce git to people who hasn't used any version control in their lives?

The reason I'm asking is because I need to teach some of my new colleagues about git. And I'm preparing a simple course for them to follow.

The download link for 2.2 preview 3 (windows causes CRC error while extracting one of the bouncy castle jars. Any idea if this will cause issues?

The issue is while extracting _bcprov-jdk15on-1.48.jar_

Update: this causes issues with gradle build.

/cc +Tor Norbye​​

Post has shared content

Post has attachment

Post has shared content
This morning at #DroidconNYC , +Nick Butcher, +Chris Banes and I delivered a talk titled What's New in Android UI Engineering, covering Android 6.0 Marshmallow, new support libraries, upcoming tooling updates, and more! Check out the slides + videos in this slideshow.

#AndroidDesign #AndroidDev

Post has shared content
Use cold start time effectively with a branded launch theme
Pro-tip by +Ian Lake

When your app isn’t in memory and is launched, that ‘cold start’ can take significantly longer than if your app is already in memory. Depending on the size of your app and what you’re doing in your Application’s onCreate() (as little as possible I hope!), there may be lag between when the user starts your app and your Activity’s onCreate() is actually called. During that time, the window manager makes its best effort to draw a placeholder UI using elements from your theme such as the background and status bar color.

But the background doesn’t have to be a solid color: it can be an opportunity to add a little more personality and branding to your app without slowing down the user through the use of a branded launch screen (, allowing your app UI to focus on content rather than additional branding. The key is creating a custom theme that overrides android:windowBackground, then replacing that custom theme with your standard theme before calling super.onCreate().

Assuming you have a theme called AppTheme, your launcher theme would be:
<style name="AppTheme.Launcher">
  <item name="android:windowBackground">@drawable/launch_screen</item>

This implies that everything about the launcher theme is inherited from your main theme - you’re just changing the windowBackground. One other attribute you may consider changing here is colorPrimaryDark: the status bar color on Android 5.0+ devices. Setting colorPrimaryDark to your main background color can put more emphasis on your branding at the expense of another element changing when transitioning to your final theme.

But drawable/launch_screen can’t be just a simple image, unfortunately - it’ll end up stretched to fill the entire screen. Instead, you can use an XML file such as:
<layer-list xmlns:android="" android:opacity="opaque">
  <!-- The background color, preferably the same as your normal theme -->
  <item android:drawable="@android:color/white"/>
  <!-- Your product logo - 144dp color version of your app icon -->

Make particular note of the android:opacity=”opaque” line - this is critical in preventing a flash of black as your theme transitions.

Then apply your theme to your activity in your AndroidManifest.xml using android:theme="@style/AppTheme.Launcher".

The easiest way to transition back to your normal theme is to call setTheme( before super.onCreate() and setContentView():
public class MyMainActivity extends AppCompatActivity {
  protected void onCreate(Bundle savedInstanceState) {
    // Make sure this is before calling super.onCreate
    // ...

Things to note with this approach:
- No launchpad activity - there’s no delay such as there would be if you were launching a second activity from a dedicated splash screen style activity
- No artificial delays - you’re only using the time that you have, just taking advantage of theming
- No extra overdraw - resetting your theme removes a layer of overdraw compared to having an opaque view with your normal background above the custom windowBackground
- Only for your launcher activity - this isn’t appropriate for deep links into your app or handling a URI, but for launches done through the home screen - the point is to minimize dead time, not to annoy users.
- Fast is best - keeping your app lean and minimizing work done at startup is critical to a good experience, even if that means slightly less time for branding - remember: getting users to the content they care about should be your #1 priority.
- Watch your transition - keep both the number and complexity of your transitions to a minimum by sharing as many elements (colors, etc) as possible to make for a seamless transition straight to content.


Post has shared content
OK, who wants to hear some TCP joke?

Is it against policy to use a variation of play store icon for an app's launcher icon?
Wait while more posts are being loaded