I'm trying to figure out how to structure everything so that

fun foo(dep)

isn't exposed to consumers. Right now I have something like this

//commonMain
interface MultiplatformComponent {
  val foo: Foo
}

//androidApp
@Component
interface AndroidAppComponent : MultiplatformComponent, AndroidFooModule, SomeOtherModule

// I'm coming from Dagger, so I didn't really have a better name for these
interface AndroidFooModule {
  fun provideFoo(dep...): Foo {...}
}

Is there a better way to modularize how dependencies are satisfied?

Yeah I'd say that's a recommended pattern. And agree.

so in my MainActivity I can see

appComponent.provideFoo

. It's not the end of the world, I would have just liked to somehow keep that from leaking

You can pass around MultiplatformComponent

hmm yeah, if I don't need Context or something platform specific, I guess I can hide the actual type