Starting KMP project at my new job :tada: Bit of context: - We'll be looking into publishing SDKs f...

# touchlab-tools

[kaeawc]

Starting KMP project at my new job 🎉

Bit of context:
• We'll be looking into publishing SDKs for iOS and Android. While I've seen some threads in this channel and elsewhere about other's experiences, one thing I'm pretty sure we'll be doing is publishing modular SDKs that ship different components. It sounds like the general idea will be to publish iOS and Android modular SDKs for their respective platforms, just want to verify that this line of thinking makes sense.
• We'll be loading some C-libraries that are built and optimized for each platform. I believe it makes sense to ship these in the Android/iOS only parts of the codebase, but would appreciate anyone here who could share their experience doing so.
• We'll be on GitLab and I'm experienced writing CI configs/actions/etc. I saw there was an open question about GitLab support and only GitHub is supported out of the box - when we get ours working I'd be happy to contribute back to the community, where's the best place to contribute that?
Excited to kick the tires on this

[kpgalligan]

"It sounds like the general idea will be to publish iOS and Android modular SDKs for their respective platforms, just want to verify that this line of thinking makes sense." What do you mean by "modular" SDKs?

[kpgalligan]

"We'll be looking into publishing SDKs for iOS and Android" For external folks or for internal app dev?

[kpgalligan]

Can hop on a call if you want to chat and/or have details. Curious as to your plans. I'm right in the middle of all this, so it's very fresh on the mind.

[kaeawc]

It'll be for external folks to consume as a third party SDK. Likewise this is all fresh - its a startup getting into mobile. Happy to hop on a call 🙂

[kaeawc]

Might also be some internal dev use-case

[kaeawc]

but that's less sure right now

[kpgalligan]

Interesting. Supporting CocoaPods and SPM? I will say, for external people, the Xcode config for published binaries is more complex. I don't know about GitLab, but with GitHub, even public repos require setting up GitHub auth for the binary artifacts. https://kmmbridge.touchlab.co/docs/artifacts/MAVEN_REPO_ARTIFACTS#gitlab-packages

[kpgalligan]

You can use the S3 publisher for public artifacts. Not for private, though. S3 has no basic auth option for S3. https://kmmbridge.touchlab.co/docs/artifacts/S3_PUBLIC_ARTIFACTS

[kpgalligan]

However, if you use that for public artifacts, the user of the library doesn't need to config the ~/.netrc file. That config has been a pretty big stumbling block as most people miss it for public repos and assume you don't need it.

[kaeawc]

That makes sense regarding auth for binaries. I think we'll only have public binaries, because if we have an artifact for internal dev I'd like to take the route of making it public so if someone wanted to build their custom UI on top of it instead of ours they have that option.