wear-os-samples VS golang-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

You can find an example of the function code for analyzing the data store on Google Cloud’s Github.

Choose a platform like App Engine. It's auto-scaling. Supports bigtable. And opentelemetry. Manageable from anywhere via Cloud Shell. You can run multiple instances and partition load between them. Even includes a free tier ;)

https://github.com/GoogleCloudPlatform/golang-samples

# Source: https://github.com/GoogleCloudPlatform/golang-samples/blob/master/run/helloworld/Dockerfile FROM golang:1.16-buster as builder # Create and change to the app directory. WORKDIR /app # Retrieve application dependencies. # This allows the container build to reuse cached dependencies. # Expecting to copy go.mod and if present go.sum. COPY go.* ./ RUN go mod download # Copy local code to the container image. COPY . ./ # Build the binary. RUN go build -mod=readonly -v -o server # Use the official Debian slim image for a lean production container. # https://hub.docker.com/_/debian # https://docs.docker.com/develop/develop-images/multistage-build/#use-multi-stage-builds FROM debian:buster-slim RUN set -x && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y \ ca-certificates && \ rm -rf /var/lib/apt/lists/* # Copy the binary to the production image from the builder stage. COPY --from=builder /app/server /app/server # Run the web service on container startup. CMD ["/app/server"]