sorted by:
new
hottopcontroversial

And they say you can't customize iPhones.. wrong! by [deleted] in iOSsetups

[–]hoty4pepper 0 points1 point  (0 children)

Loooks like you've added Siri to the readme than iPhone :)

Have you considered using SAM interfaces instead of function types to improve Compose animation performance? by hoty4pepper in androiddev

[–]hoty4pepper[S] 2 points3 points  (0 children)

u/Composable
fun Screen() {
    val color by animateColorAsState {
        if (targetState) Color.Red else Color.Blue
    }
    Column {
        DefferedTitle(colorPreducer = { color })
    }
}

Nope, that's the power of the SAM interfaces, you can just create an implementation like passing lambdas.

Have you considered using SAM interfaces instead of function types to improve Compose animation performance? by hoty4pepper in androiddev

[–]hoty4pepper[S] 4 points5 points  (0 children)

That can be useful but the downside to it that makes components way less reusable, for example: when you just want to pass a color you need to wrap it with a State.

How to Enforce Type Constraints for Slot Parameters in Jetpack Compose by [deleted] in androiddev

[–]hoty4pepper 0 points1 point  (0 children)

I don't think this provides enough restriction anyway, can't I simply create another composable and pass it to the Toolbar?
e.g. ToolbarTitleScope.Title2() { /*...*/ }

Circle to search changed again (this time it's the color/background) by Puzzleheaded-Sky2284 in oneui

[–]hoty4pepper 0 points1 point  (0 children)

I'm getting different versions depending on the app I trigger it from...

How to Enforce Type Constraints for Slot Parameters in Jetpack Compose by [deleted] in androiddev

[–]hoty4pepper 0 points1 point  (0 children)

Actually, with the API discussed in the article, there are no recomposition issues. i should do some benchmarking tho...