Hi! I just walked through this hands on example, which was super helpful. Thanks to whoever wrote this:

<https://play.kotlinlang.org/hands-on/Targeting%20iOS%20and%20Android%20with%20Kotlin%20Multiplatform/01_Introduction>

I noticed that in this example we create a SharedCode module right inside the same folder as the Android app. Is this approach common, or is it normal to have your shared code as its own project that could be kept in its own git repository? If I do that, I'm not sure how difficult it becomes to link it to my Android app since it's no longer as simple as

implementation project(':SharedCode')

. Just curious what others have done about this.

both ways are common. if you pull it out as a library, it's the same as integrating any other artifact into your app.

Hey @adam-mcneilly 😄, i've played with multiplatform doing this course https://www.raywenderlich.com/1304635-kotlin-native-and-multiplatform And what's @Kris Wong says makes a lot of sense.

We use svn extnerals for linking externally managed subprojects, which is the equivalent of git submodules.

svn!

Thanks @Alejandro Rios! And others - all good ideas to look into. I somehow have not encountered submodules yet but after looking that up that sounds really helpful I'll try to learn more about them. 🙂

yep

Wow! Thanks for sharing that! Really helpful

I just started evaluating Kotlin Native to move the common business logic into a SharedLib, and consume from android and iOS. I found this thread really helpful, thanks!

Note that the mobile shared library template builds JVM and not Android. You’ll need to adjust it some if you want to access Android APIs in the platform-specific implementations of the shared module.

For my project I have a module for each target, and my SharedCode contains an android library implementation that is as bare bones and makes it very easy to build everything multiplatform very stand alone

@russhwolf What kind of adjustments?

@adam-mcneilly Adding

com.android.library

plugin and

android

block. Some publishing stuff too if you need to import from another project. Details on android-specific multiplatform gradle config at https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html#android-support

Y'all are the best, thanks so much! Company hack week next week, I think I wanna peak at this and try implementing a shared network call or model class or something.

i also have a blog post on converting to an Android target within an MPP. there are several steps. if you need it PM me and I can link you to the draft.

I may do so next week if I get stuck. Thanks. 🙂

There’s been a lot of feedback here. I’d say most projects want to have a separate module for shared code rather than having it mixed in to the Android app module, but obviously it’ll work either way. Mentally it’s sort of easier to manage if split out, and it seems like that’s the preferred config, but whatever.

if a project will see a lot of development, it's easy to use a gradle flag to flip between a subproject (for dev), and an artifact in Artifactory or whatever

Yeah I'd like to take up Kris' offer (or anyone else who knows of one of these) on the blog post for adding an Android target within the "Mobile Shared Library" template. The information in the link from Russell is helpful but not quite there and I'm not sure what I'm missing.

What’s the issue you’re hitting?

Well I couldn't figure out how to rename everything from

jvmMain

to

androidMain

but after looking at another project, I tried this magical trick in my build.gradle and it seemed to work:

kotlin {
    jvm("android")
}

Then I realized it already includes a maven-publish plugin, and there's a gradle task to publish it to my local maven repo, which is everything I want for right now! I'm still not sure why the thing above fixed anything. Previously it was just

jvm()

. Is the parameter like specifying a name for that module? I also haven't tried referencing any Android specific APIs but I don't think I'll need to. I just want to build a proof of concept with like a shared networking layer.

try

android()

or

android("xyz")

. The string is just a name. The function call determines the platform it’s building for.

Originally doing that I kept getting something like

Extension with name 'android' does not exist.

. I've put the code away for now, but I can check again tomorrow and see what I did wrong. Thanks for checking though. 🙂 If I'm not using platform libraries, does it really matter then? If I can use jvm on Android then this might not be worth sinking time into.

yeah if you don’t need android APIs you should be fine with JVM.

Yes, but then it will tell you that the plugin can't be found. 😂 I tried adding google's maven to the repositories block and no luck. I'm probably missing something extremely obvious.

@adam-mcneilly This module supports Android, iOS and macOS. It relies on helpers put in

buildSrc

of the root project that allow smooth multiplatform dev in Android Studio or IntelliJ: https://github.com/LouisCAD/Splitties/blob/241a91f582352952813afc5ca0b06555361f74a1/modules/preferences/build.gradle.kts

@adam-mcneilly let me know if you still need that blog post

@Kris Wong share the link please

it's not published yet, so I am just offering to share the draft privately to those who need it

oh, ok