A modern programming language that makes developers happier.

kotlinlang

Hi folks! I usually develop Android apps using Jetpack Compose and am currently investigating whether it can be ported to Compose for iOS. We sometimes use LocalContext in Jetpack Compose for Android, but I think that Context depends on android.content. What should we do in Compose for iOS? Should we not use Context?

I would ask - why do you need it? If you need resources I think compose mpp has solutions. If you need to launch android specific things, I might make abstractions for each platform around that usage rather than rely on context

I can see why original compose has support for it, but at same time it could propagate usage of that god object 

I looked into the code and found that it was used in PSharedreference. I believe this is an Android-dependent feature, so should we consider implementing it differently?

And using in DatePicker.

```MaterialDatePicker.Builder.datePicker()
                .setSelection(date?.toEpochMilli() ?: Instant.now().toEpochMilli())
                .build()
                .apply {
                    show(context.supportFragmentManager, "DatePicker")
                    addOnPositiveButtonClickListener {
                        setDate(Instant.ofEpochMilli(it))
                    }
                }
        }```

Hello, we have a solution for this right in our main sample, called imageviewer:
```on common:
expect class PlatformContext
@Composable
expect fun getPlatformContext(): PlatformContext

on Android:
actual class PlatformContext(val androidContext: Context)
@Composable
actual fun getPlatformContext(): PlatformContext = PlatformContext(LocalContext.current)```
<https://github.com/JetBrains/compose-multiplatform/blob/1d955a2e6da60f695aee1efb0f1e121177ae88b0/examples/imageviewer/shared/src/androidMain/kotlin/example/imageviewer/filter/BitmapFilter.android.kt#L30|https://github.com/JetBrains/compose-multiplatform/blob/1d955a2e6da60f695aee1efb0f[…]dMain/kotlin/example/imageviewer/filter/BitmapFilter.android.kt>

After that you can also create
```@Composable 
expect fun PlatformDatePicker```
```@Composable 
actual fun PlatfromDatePicker {
    with android implementation
}```
and some different one for iOS

Thanks! I'd like to try it later!

I believe there are differences due to the OS, but are there any efforts to bridge these gaps in Kotlin Multiplatform?

In other words, I'm talking about Jetpack Compose becoming independent of Android. It would be nice if DatePicker could achieve this. I understand that running SharedPreference in Jetpack Compose might be difficult since it's impossible to avoid the OS differences, but it would be nice if Kotlin Multiplatform could provide a solution.

I found DatePicker in Compose Material3 v1.10-Beta!

<https://developer.android.com/jetpack/androidx/releases/compose-material3?hl=en#1.1.0-beta02|https://developer.android.com/jetpack/androidx/releases/compose-material3?hl=en#1.1.0-beta02>

<@U01L7P76USW> did you try it? I also noticed that it’s available now with the exception of the TimePickerDialog but there’s some code for that on Stackoverflow. However I couldn’t find a way to select dates in UI tests. Anyone know if it’s possible or do they still need to add the semantics? Talkback can read the dates just fine so I would have thought that at least something like this should work but it doesn’t. Nothing is visible in the layout inspector inside the DatePicker so I think it’s not quite ready yet. so close though. also clearly it’s in progress but the material design page just says “planned”.

```composeTestRule.onNode(hasContentDescription(value = "Tuesday, 12 October 2021")).performClick()```
