Fixed
Status Update
Comments
cl...@google.com <cl...@google.com>
ma...@google.com <ma...@google.com> #2
Is there any way to use this while it's not available, without a big if else where we do everything duplicated? Like this example.
val notification = if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
Notification.Builder(...)
.setContentTitle("Title")
.setStyle(...)
// Duplicate everything here!!!
.build()
} else {
NotificationCompat.Builder(...)
.setContentTitle("Title")
.setStyle(...)
// Duplicate everything here!!!
.build()
}
ae...@google.com <ae...@google.com> #3
Hi,
Could you at least tell us if you will add the CallStyle to the NotificationCompat API?
Best regards,
ma...@google.com <ma...@google.com>
ap...@google.com <ap...@google.com> #4
Yes. Our goal is to provide an implementation that uses CallStyle on API 31+ and uses the new fields to produce a usable call notification, based on the device's standard template, on older versions of Android.
lp...@google.com <lp...@google.com>
ap...@google.com <ap...@google.com> #5
Thanks for the answer. Do you have an estimated ETA?
Description
It seems like these are all designed to be used as standalone components (given that all have onClick arguments and Switch can be swiped for example). But all of them have tap targets that are less than 48dp (given that their physical size is smaller than that).
Should their size be increased to account for this?
Or maybe there an equivalent to TouchDelegate that could be used to expand the tap target size?
Otherwise it seems odd that these components have
onClick
arguments, since I think that may discourage people from implementing accessible tap targets properly.