![]() ![]() In my view, that is a very questionable choice, given that data stored using the DataClient API is synced to Google's servers, as per this table and the "synchronize data" section above it. Google's official guide on this uses the DataClient in the Wearable Data Layer API. Tonight, I did some investigation into syncing authentication credentials between the Wear OS app and the Android app (sadly, syncing credentials on iOS is not supported). ![]() Hey everyone! I might spend some time here and there contributing to the Wear OS app. □ If there's something else you're interested in working on though, feel free to tackle that. We might even be able to do a release with WearOS support with only that functionality. My inclination would be to focus on the Now-Playing/Up-Next functionality first since that seems like the core functionality. Our plan was to support offline playback as suggested in #490. ![]() You can do an iOS build yourself to explore the watch app on a simulator, but in case you can't (or don't want) to do that, this is what it looks like. ![]() We're largely looking to replicate the functionality from Pocket Casts' iOS watch app to start-not because we want the WearOS to be exactly the same as the iOS watch app, but more because that seems like the easiest way to create our first iteration for WearOS. We were mostly coordinating on private channels before now, but going forward this thread is probably the best place to coordinate now that we want to do that publicly (I'm open to other suggestions though). Is there some coordination on this effort already? ![]()
0 Comments
Leave a Reply. |