Another reason why it is a constant battle to get Android Studio to do what you want it to do! Calendar class is only available above one API level. Date class is available from a different API level but get and set functions are deprecated above a certain API level. DatePicker is available only above API 11 . . . Jeeessus! Why is this so god damned complicated???? Why, for example, can't Date class be just left alone under all API versions for backwards compatibility. By all means add the Calendar class at higher API levels but leave the Date class alone! I reckon this has got to be a case of too many 'opinions' ruling Android Studio development and no one being prepared to put their foot down and lay down the law. None of this is a problem in MS Visual Studio - all versions of Visual Studio have the same basic set of controls that work under all versions of windows. There are additional more sophisticated controls that work only with certain versions of windows and .net etc but you are not compelled to use them.