horologist-datalayer-watch dependencies about horologist

[Tolriq]

So not opening a new issue but:

• composables request androix.wear that is not needed and embed fragment, recyclerview, swiperefresh ...
• media:data same as above
• compose-layout embed androidx.wear but unfortunately it's used for AmbientAware, not sure it's worth a module split.

(Yes I know I'm obsessed with APK size and unneeded deps :) )

[Tolriq]

androidx API had tight dependencies

So do I, in the end until they split media router I doubt most people will care, it's a pain to maintain a fork just to do it, despite not much to do.
But a few other androidX deps should also be updated for better support of full Compose apps, specially when every one says hey now you should do it in Compose. And still force appcompat, fragments and even drawerlayout for no reason and the proguard rules preventing proper stripping.

Anyway just a quick rant :p

[yschimke]

I'll take a look at how this is possible. It's valid and hopefully something to improve.

On the other hand it's convenient to not have more tiny module. Ultimately I wish the androidx API had tight dependencies :)

[Tolriq]

In the same continuation, any reason why tiles have a complication part and all the deps? They seems at first sight pretty unrelated.

[yschimke]

@Tolriq a bad judgement call? I think my thinking was that having a whole another module for 1-2 classes was overkill, and I'd expect apps with Tiles to also have Complications.

Let me review. We can move things around when we bump to 0.7.x.

[Tolriq]

In my case for music it seems the media session already publish the complication data no? Everything seems to work on the watch faces.