But not everything is a button. Designers need to be extra careful when displaying non-interactive fields on the same page as buttons if they are going to remov

But not everything is a button. Designers need to be extra careful when displaying non-interactive fields on the same page as buttons if they are going to remove UI chrome. Twitter for Android is an example of how nonintuitive a flat interface can be. When viewing user profiles, you are presented with a list of information (name, bio, tweets, lists, etc). Clicking Name or Bio does nothing, but they are the first items listed and look exactly the same as every other item. (Actually, clicking them causes the item to highlight as if you were clicking a button, but there is not any associated action, so nothing happens.) When looking to see a user's tweets, it always takes a moment to remember that "Oh right, some of these words are interactive." The Settings menu in Android attempts to solve this by greying out fields which do nothing (e.g., the Model field in About Phone). It works there, but the same technique could fail if your app also has potentially disabled buttons or important static information that shouldn't be grayed out.