What would be the best way to add firebase to a KMP + Compose Multiplatform App that targets Android and iOS. I want to use the firebase official android and iOS libraries with a custom expect and actual implementation... What woukd be the right architecture to do this?

I was able to use batch insert for exposed, but when I am adding

transaction {
            addLogger(StdOutSqlLogger)
            SomeTable.batchInsert(data = listOf(1,2,3,4)) {
                this[SomeTable.someColumn] = it
            }

SQL logger shows multiple sql inserts(number of insrets = list.size) Should not it be one insert with multiple values? Or is it StdOutLogger problems?

Is there a way to get the current size of a screen (width and height) in Compose for a multiplatform approach? So at best for Android, iOS and desktop with one common API that can be used in a shared composable.

Hi, does anyone know how to solve "No such module composeApp" error

hi all. how to switch off in compose LazyColumn overscroll effect like android:overScrollMode="never" for RecyclerView

Hi! I’m having pretty hard time debugging KMM common module on iOS. I can make app compile and run, debugger attached, however it: • ignores all line breakpoints • only possible to break on function entry points • when it finaly stops I get into Assembly view • stop on exception in Xcode works (also in assembly view usually) • Kotlin native library APIs usually opens in as Kotlin code when debugging I have debug symbols in kotlin module and in iOS app. Everything looks good, yet it does not work from Android Studio neither. From what I have found out it looks like there is some kind of problem with dSYM debug symbols for llvm generated code from the kotlin library. All .swift files are readable. Most of Kotlin standard library is readable. I have tried to fiddle in Xcode with optimization, linking optimization, debug symbols stripping, etc. Everything is turned off. I have

embedBitcode("marker")

enabled for my binaries. What do I do wrong? This is so frustrating.

gradle:7.4.0, OpenJDK@11, Android Studio 2022.1.1, Xcode 14.2, MacOS 13.1 (ARM)

One of the biggest downsides of Compose for me is the performance. Eventhough I have R8 enabled and I’m running in release build (which is also a downside cause it takes hours to build and heats up my laptop) it is still a poor experience. HorizontalPager + LazyVerticalGrid with 3 columns = 10 FPS Same setup on XML = extremely fast.

How do we flatten a JSON with nested elements into a single class? E.g. I’ve to following OSM data that I need to have in just one class, without creating a subclass for `tags`:

{
      "type": "node",
      "id": 66917229,
      "lat": 52.5167295,
      "lon": 13.3797732,
      "tags": {
        "addr:city": "Berlin",
        "addr:housenumber": "4a",
        "addr:postcode": "10117",
        "addr:street": "Pariser Platz",
        "amenity": "cafe",
        "brand": "Starbucks",
        "name": "Starbucks",
        "website": "<https://www.starbucks.de/store-locator/store/2099/pariser-platz-pariser-platz-4-a-berlin-be-10117-de>",
        "wheelchair": "yes",
        "wifi": "free"
      }
    }

I am using custom Serializer but I’m a bit lost on how to unwrap the nested values in the

deserialize

function for the nested tags element. Any help is highly appreciated.

What is

iosX64()

for? Are there some x64 ios devices? I though it was all arm always?

🆕K🦜 📣 Kotlin 1.8.20-Beta brings many new features: • New Kotlin K2 compiler updates • New experimental Kotlin/Wasm target • New JVM incremental compilation by default in Gradle • Update regarding Kotlin/Native targets • Preview of Gradle composite builds in Kotlin Multiplatform • Improved output for Gradle errors in Xcode • Experimental support for AutoCloseable interface in standard library • Experimental support for Base64 encoding in standard library 📣 The K2 Compiler is going stable in Kotlin 2.0 We’ve been working on a new frontend for the Kotlin compiler (code-named “*K2*”) for quite a while. The new frontend is already available for preview – we’re continually polishing and stabilizing it and plan to make it the default compiler frontend in a future Kotlin release. We’ve decided to name this future release Kotlin 2.0. Learn more about the release roadmap and what to expect from Kotlin 2.0 Try out the new compiler frontend and give us feedback! Starting with Kotlin 1.8.20-Beta you can enable a preview of the Kotlin 2.0 language version via the regular Kotlin language version flag.