wear-os-samples VS accompanist

Using DataLayer to transfer data from phone to your watch app. Check here wear-os-samples/DataLayer

Here is a really good repo by Google filled with WearOS sample projects. Helped me a lot with setting up communication between watch and phone. This is also a good starting point to understanding how these apps work. https://github.com/android/wear-os-samples

There are plenty of open source watchfaces out there. Check out this github repo by Google. It contains best practice examples all around wear os including watchfaces.

So I'm looking for good sources on how to use the new jetpack apis. So far I only found this sample project.

I think for Android based smartwatch, you could read something here

Main documentation about how to make watch faces under Wear OS seems to be the WatchFaceKotlin example. This example contains borders around complications. Some installed watch faces don't have borders around complications.

I converted my codebase to Kotlin a few years ago, but I am struggling to move to new wear libraries. There is so much work to do, because Google, in their immense wisdom, decided to change everything. And don't even get me started about the Decomposition API (option to add second hand in ambient mode). I opened this issue almost a year ago and got no answer. https://github.com/android/wear-os-samples/issues/85

Tried this sample from Google: https://github.com/android/wear-os-samples/tree/main/WatchFaceKotlin

The truly disheartening part is that whenever you choose something that works, for example ViewPager1, you need to defend that yes, this thing actually works as intended, yes, there's nothing in it that would "break over time" just because Googlers added the @Deprecated on it, and yes, you still don't want to use Compost for this because you still cannot scroll vertically in a horizontal Pager if your view is a WebView.

Compose on the other hand came out half-baked, significant performance issues, missing features, bugs and bugs and bugs and bugs and bugs and bugs and bugs and bugs and bugs.

Just to add to the list, Accompanist is a collection of compose libraries that helps a lot with some features. I can recommend Navigation-Animationand Permissions. https://github.com/google/accompanist

To give a bit of context, libraries not released as Jetpack libraries as experiment projects. Once they're released as Jetpack libraries, we have stricter release schedule in place and more resources to provide better stability for developers. That's why some Accompanist libraries end up as part of Compose foundation set, while others are still being shipped as part of the Accompanist project.

So you're going to get support for Parcelables in argument passing, animation support without having to fear crashes, and if you drink the ScopedServices koolaid you even get to get DI with lifecycle management and scope inheritance.

Here's a fun bug though https://github.com/google/accompanist/issues/1233

There is a bug the preview is not working when System UI controller is used. See issue tracker here.

👋 I have been using Mobius personally and for work for over two years now. It's a lot of fun to use and I would definitely recommend the community to consider using it. I frequently visit their GitHub repo because they still have their documentation in the GitHub wiki, unlike new repos such as Accompanist. So, I thought what better way to give back than do the grunt work of porting their wiki to GitHub Pages + MkDocs ❤️🔥

Accompanist for unofficial stuff that's still useful