Android Material Library
up vote
0
down vote
favorite
The different Android Versions (even older ones) have still a big marketshare. For consultation I took the Distribution Dashboard into consideration.
When I started with Android Development I thought that the Standard components will have Material Style by default set. But as further as I came, I recognized that the "Standard" and Support Components don't have the "newest" Guidelines implemented.
So I was trying to understand why and found the com.google.android.material Library. I think this is a step into the right direction but I got a bit suspicious when I read the "Getting Started" Guide. Inside the guide it states "download the Android P Preview using the SDK manager".
Now I'm questioning, does that mean, that when I want to support all Android Versions with the biggest marketshares (all Versions till 5.1), I can't use this library, or is it still backwards comaptible?
Further I recognized, that when I want to support "older" Android Versions I need to use the Support Libraries. But I always questioned, isn't this a bit senseless? I mean, most of us want to bring their app to as much customers as possible. Due to the fact that 5.1 and 6.0 have a marketshare of approximately 30% does anyone really drop support for these devices and uses just "plain" Components not contained in the Support Library?
android material-design android-support-library asked Nov 12 at 19:55
LukeFilewalker
513516
add a comment |
up vote
0
down vote
favorite
The different Android Versions (even older ones) have still a big marketshare. For consultation I took the Distribution Dashboard into consideration.
When I started with Android Development I thought that the Standard components will have Material Style by default set. But as further as I came, I recognized that the "Standard" and Support Components don't have the "newest" Guidelines implemented.
So I was trying to understand why and found the com.google.android.material Library. I think this is a step into the right direction but I got a bit suspicious when I read the "Getting Started" Guide. Inside the guide it states "download the Android P Preview using the SDK manager".
Now I'm questioning, does that mean, that when I want to support all Android Versions with the biggest marketshares (all Versions till 5.1), I can't use this library, or is it still backwards comaptible?
Further I recognized, that when I want to support "older" Android Versions I need to use the Support Libraries. But I always questioned, isn't this a bit senseless? I mean, most of us want to bring their app to as much customers as possible. Due to the fact that 5.1 and 6.0 have a marketshare of approximately 30% does anyone really drop support for these devices and uses just "plain" Components not contained in the Support Library?
android material-design android-support-library asked Nov 12 at 19:55
LukeFilewalker
513516
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The different Android Versions (even older ones) have still a big marketshare. For consultation I took the Distribution Dashboard into consideration.
When I started with Android Development I thought that the Standard components will have Material Style by default set. But as further as I came, I recognized that the "Standard" and Support Components don't have the "newest" Guidelines implemented.
So I was trying to understand why and found the com.google.android.material Library. I think this is a step into the right direction but I got a bit suspicious when I read the "Getting Started" Guide. Inside the guide it states "download the Android P Preview using the SDK manager".
Now I'm questioning, does that mean, that when I want to support all Android Versions with the biggest marketshares (all Versions till 5.1), I can't use this library, or is it still backwards comaptible?
Further I recognized, that when I want to support "older" Android Versions I need to use the Support Libraries. But I always questioned, isn't this a bit senseless? I mean, most of us want to bring their app to as much customers as possible. Due to the fact that 5.1 and 6.0 have a marketshare of approximately 30% does anyone really drop support for these devices and uses just "plain" Components not contained in the Support Library?
android material-design android-support-library asked Nov 12 at 19:55
LukeFilewalker
513516
The different Android Versions (even older ones) have still a big marketshare. For consultation I took the Distribution Dashboard into consideration.
When I started with Android Development I thought that the Standard components will have Material Style by default set. But as further as I came, I recognized that the "Standard" and Support Components don't have the "newest" Guidelines implemented.
So I was trying to understand why and found the com.google.android.material Library. I think this is a step into the right direction but I got a bit suspicious when I read the "Getting Started" Guide. Inside the guide it states "download the Android P Preview using the SDK manager".
Now I'm questioning, does that mean, that when I want to support all Android Versions with the biggest marketshares (all Versions till 5.1), I can't use this library, or is it still backwards comaptible?
Further I recognized, that when I want to support "older" Android Versions I need to use the Support Libraries. But I always questioned, isn't this a bit senseless? I mean, most of us want to bring their app to as much customers as possible. Due to the fact that 5.1 and 6.0 have a marketshare of approximately 30% does anyone really drop support for these devices and uses just "plain" Components not contained in the Support Library?
android material-design android-support-library android material-design android-support-library asked Nov 12 at 19:55
LukeFilewalker
513516
asked Nov 12 at 19:55
LukeFilewalker
513516
edited Nov 12 at 21:58
asked Nov 12 at 19:55
LukeFilewalker
513516
asked Nov 12 at 19:55
LukeFilewalker
513516
asked Nov 12 at 19:55
LukeFilewalker
513516
513516
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
The first library you mentioned (Material Components) works on all supported versions of Android, which currently is 14+. It internally uses Support Library and adds on top of their controls. You can use whichever you like and you'll be good on 5.1 and 6.0.
The bad part is that none of these libraries actually fully implement the guidelines nor backport features. When I last checked, there was no cut corners, no backdrop layout, no saturation fade for images, etc. Shadows, ripples and drawing order don't work on API 4.x, colored shadows don't work on API older than 28, etc.
If you need Material Design as in the guidelines, you need a 3rd party library or a lot of work.
answered Nov 13 at 0:18
Zielony
10.2k42734
Flutter addresses this problem by providing the exact same experience throughout all API levels.
– urgentx
Nov 13 at 0:22
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The first library you mentioned (Material Components) works on all supported versions of Android, which currently is 14+. It internally uses Support Library and adds on top of their controls. You can use whichever you like and you'll be good on 5.1 and 6.0.
The bad part is that none of these libraries actually fully implement the guidelines nor backport features. When I last checked, there was no cut corners, no backdrop layout, no saturation fade for images, etc. Shadows, ripples and drawing order don't work on API 4.x, colored shadows don't work on API older than 28, etc.
If you need Material Design as in the guidelines, you need a 3rd party library or a lot of work.
answered Nov 13 at 0:18
Zielony
10.2k42734
Flutter addresses this problem by providing the exact same experience throughout all API levels.
– urgentx
Nov 13 at 0:22
add a comment |
up vote
1
down vote
accepted
The first library you mentioned (Material Components) works on all supported versions of Android, which currently is 14+. It internally uses Support Library and adds on top of their controls. You can use whichever you like and you'll be good on 5.1 and 6.0.
The bad part is that none of these libraries actually fully implement the guidelines nor backport features. When I last checked, there was no cut corners, no backdrop layout, no saturation fade for images, etc. Shadows, ripples and drawing order don't work on API 4.x, colored shadows don't work on API older than 28, etc.
If you need Material Design as in the guidelines, you need a 3rd party library or a lot of work.
answered Nov 13 at 0:18
Zielony
10.2k42734
Flutter addresses this problem by providing the exact same experience throughout all API levels.
– urgentx
Nov 13 at 0:22
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The first library you mentioned (Material Components) works on all supported versions of Android, which currently is 14+. It internally uses Support Library and adds on top of their controls. You can use whichever you like and you'll be good on 5.1 and 6.0.
The bad part is that none of these libraries actually fully implement the guidelines nor backport features. When I last checked, there was no cut corners, no backdrop layout, no saturation fade for images, etc. Shadows, ripples and drawing order don't work on API 4.x, colored shadows don't work on API older than 28, etc.
If you need Material Design as in the guidelines, you need a 3rd party library or a lot of work.
answered Nov 13 at 0:18
Zielony
10.2k42734
The first library you mentioned (Material Components) works on all supported versions of Android, which currently is 14+. It internally uses Support Library and adds on top of their controls. You can use whichever you like and you'll be good on 5.1 and 6.0.
The bad part is that none of these libraries actually fully implement the guidelines nor backport features. When I last checked, there was no cut corners, no backdrop layout, no saturation fade for images, etc. Shadows, ripples and drawing order don't work on API 4.x, colored shadows don't work on API older than 28, etc.
If you need Material Design as in the guidelines, you need a 3rd party library or a lot of work.
answered Nov 13 at 0:18
Zielony
10.2k42734
edited Nov 13 at 0:24
answered Nov 13 at 0:18
Zielony
10.2k42734
answered Nov 13 at 0:18
Zielony
10.2k42734
answered Nov 13 at 0:18
Zielony
10.2k42734
10.2k42734
Flutter addresses this problem by providing the exact same experience throughout all API levels.
– urgentx
Nov 13 at 0:22
add a comment |
Flutter addresses this problem by providing the exact same experience throughout all API levels.
– urgentx
Nov 13 at 0:22
Flutter addresses this problem by providing the exact same experience throughout all API levels.
– urgentx
Nov 13 at 0:22
Flutter addresses this problem by providing the exact same experience throughout all API levels.
– urgentx
Nov 13 at 0:22
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269200%2fandroid-material-library%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
