[FR]: Add :app:wear to the project

[pitoszud]

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the problem

By adding wear to the project you could cover all form factors (small, medium, large and wear). You could also show an architecture where :app:mobile and :app:wear are sharing :domain:feature modules and :data:some-other-feature.

This could be either a simple or quite versatile wear app, focusing on compose, communication and sharing modules between mobile and wear. We've got some samples covering this in wear-os-samples, but I think nowinandroid is modularized well enough to accommodate :app:wear, so why not?

https://github.com/android/wear-os-samples/tree/main/DataLayer https://github.com/android/wear-os-samples/tree/main/RuntimePermissionsWear

Describe the solution

I would add :app:mobile and update app module to :app:wear. Gradle should be updated accordingly. Perhaps the domain should be moved outside of core. Some, but not all data, should be shared between mobile and wear.

bdw, "domain" is missing in the readme common module representation. https://github.com/android/nowinandroid/tree/main/core/common

Additional context

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[dturner]

What user features would you like to see in the Wear app?

[pitoszud]

Below are some ideas to represent basic data sharing communication between mobile and wear. This could be something very similar to Google Keep

Mobile Interest (visible and controlled in mobile only)

Wear

ForYou

• User can see a full title and shorter description.
• User can save a news item to bookmarks and then read/watch on mobile later.

Saved

• User can browse bookmarked news
• User can tap on "Open on mobile" text/button and open the content on mobile
• Optional (User can unfollow the topic) - mobile is updated accordingly

Notification

• new content (although this would be difficult to implement with a static resource)

Settings

• Limit items to e.g. 10, 50, 100
• Enable LTE (if exists) - this would require the wear to have its own news resource representation
• Bluetooth/Wi-Fi selected by default would share connection/data with mobile after pairing.

[yschimke]

A big hearty +1 - I know product wise it isn't obvious. But in terms of applied modularity and also play store publishing, this will really help to have a wear app.

[mmoczkowski]

Hey folks, check out the prototype I made.

[SimonMarquis]

👋 should we close this issue?

          Hey @LouisCAD, the team decided not to move forward with this feature

Originally posted by @mmoczkowski in https://github.com/android/nowinandroid/issues/455#issuecomment-1326461091