Proper use cases for Android UserManager.isUserAGoat()?

I was looking at the new APIs introduced in Android 4.2. While looking at the UserManager class I came across the following method:

public boolean isUserAGoat()

Used to determine whether the user making this call is subject to teleportations.

Returns whether the user making this call is a goat.

How and when should this be used?

• java
• android
• usermanager

Share

Improve this question

edited Sep 7, 2018 at 8:21

Luca Kiebel

9,39577 gold badges3030 silver badges4343 bronze badges

asked Nov 14, 2012 at 8:34

Ovidiu Latcu

71k1515 gold badges7474 silver badges8484 bronze badges

• 8
  If can be used to avoid some Java warning, as an easter egg, and as a test to see who read the API. And it's a reference to an easter egg in Chrome.

  – Dorian

   Nov 14, 2012 at 20:53 
• 16
  This might be related to when Google use goats as a mower in their Mountain View Headquarters. 

  – John Isaiah Carmona

  Nov 15, 2012 at 4:58
• 5
  googlers seem to like goats for some reason, no wonder they made an easter egg out of it. there is also a serious (!) investment in goats: - as blogged in googleblog - mowing with goats - goats are baaaahk - and recorded in youtubeafter all they are native lawn movers, efficient as well.. 

  – none

   Nov 15, 2012 at 10:21
• 29
  There are also constants for the gravity on the first death star developer.android.com/reference/android/hardware/… and on the island of the tv show Lost developer.android.com/reference/android/hardware/… which is of course, the numbers. 

  – Fernando Gallego

   Mar 29, 2013 at 22:09
• 12
  They even updated the documentation after Lollipop: "As of LOLLIPOP, this method can now automatically identify goats using advanced goat recognition technology." 

  – Patrick

   Apr 25, 2016 at 7:49 
• 1
  "As of Build.VERSION_CODES.R, this method always returns false in order to protect goat privacy." 

  – HelloWorld

   May 5 at 16:22 
• Maybe to track how many times a user ended up in an unexpected/unhandled situation by calling this method. 

  – NSaran

  Jun 2 at 17:19