Difference between an AppCompat view and a normal Android view

Question

What is the difference between an AppCompat view component and a standard/default view component?

For example, the difference between an AppCompatEditText, and an EditText, or between an AppCompatButton and a Button.

Looking at the developer docs for android.support.v7.widget, the AppCompat view components are described as "tint aware", but is this the only difference, and what exactly does this do?

Answer 1

What is the difference between an AppCompat view component and a standard/default view component?

AppCompat View Component supports compatible features on older version of the platform.

the AppCompat view components are described as "tint aware", but is this the only difference, and what exactly does this do?

Although most of the AppCompatView only difference is it allows dynamic tint and background tint. Tint aware is not the only difference, each AppCompatView has its own differences, for example.

• AppCompatEditText vs EditText

Allows textAllCaps style attribute up to Gingerbread.

• AppCompatSpinner vs Spinner

Setting the popup theme using popupTheme.

You can dig down each view difference in Android docs.

However, as Sid / Docs says, you don't have to specify this on your layouts since it will automatically converted to AppCompat views. But, if you want to create custom view, you should use AppCompat Views, or else this bug will happens.

Answer 2

well one of differences that i have noticed , in order to change the background of a normal Button , you have to modify the XML ( to NoActionBar.. android:theme="@style/Theme.AppCompat.Light.NoActionBar" to android:theme="@style/Theme.MaterialComponents.DayNight.NoActionBar"

whatever all i want to say is it difficult to work with buttons than the AppCompat version ).

so the use of androidx.appcompat.widget.AppCompatButton is somehow considered good because you will avoid a lot of little problems using the androidx library.