wear-os-samples VS architecture-samples

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

Here's an example project on GitHub that demonstrates how to use a ViewModel in practice: https://github.com/android/architecture-samples/tree/master/BasicSample

For me this one is the best: Architecture samples it's easy to understand and covers lots of concepts.

Since I never had a mentor or any courses I decided to follow anyone in their development approaches and my choice was google team. There are repo which is supported and update for years, it changes and might slightly differ in branches. But it could answer your questions.

For merging multiple data-sources, like network and database, I can use Repository backed with NetworkDataSources and DbDataSources. For data manipulation, Kotlin's collection has many useful functions (map, reduce, groupBy, count, etc.). If I want to ensure a data can only be emitted once, a simple modification to LiveData is enough (SingleLiveData

Take a look on Android blueprints https://github.com/android/architecture-samples