help help help! #16 about kampkit HOT 4 CLOSED

Can you describe your setup in a bit more detail? Is the issue that you're hosting binaries in github, and they're too big? If so, you might want to take a look at KMMBridge as an alternative. Or are you worried about the size on-device or when downloading from the store? In that case, you should measure that size directly rather than worrying about the framework size in particular because some unused things will get stripped during the build process.

from kampkit.

thanks @russhwolf ,
my setup like this,

1. a repo for the KMM + Android code
2. a repo for KMM binaries (shared/build/cocoapods/publish/release/*)
3. a repo for the ios code (UI), consume 2nd repo

any change on 1st repo required a push with 74.5MB to 2nd push
then download with 74.5MB in 3rd repo on my colleague

do you think this is an issue of KMM team, they should limit the binaries to less then 3MB

from kampkit.

Git is generally a bad place to store binaries. I recommend looking at KMMBridge which can publish artifacts to other places such as maven repositories, S3, or Artifactory. Our default setup uses a github maven repository.

In any event, this is outside the scope of KaMPKit which is meant as a starter sample for trying out architecture, but doesn't deal with publishing.

from kampkit.

@russhwolf may Allah blees you , we can close this issue

from kampkit.