Should Android app check if Wear is connected before sending data?
I've got an app that utilizes a Wearable and am using the Listener Service, sending messages and synchronizing DataItems in between. This app does not have to use a Wearable. What I want to know is if my app should always check if a Wearable is connected before deciding if I should send data/messages?. If yes, what is the best way to check if Wearable is connected. Thank you very much!
android wear-os android-wear-data-api
asked Nov 12 '18 at 18:48
David Nuno
82
add a comment |
I've got an app that utilizes a Wearable and am using the Listener Service, sending messages and synchronizing DataItems in between. This app does not have to use a Wearable. What I want to know is if my app should always check if a Wearable is connected before deciding if I should send data/messages?. If yes, what is the best way to check if Wearable is connected. Thank you very much!
android wear-os android-wear-data-api
asked Nov 12 '18 at 18:48
David Nuno
82
I think it is a required step to check if there is any connected device before sendingdataItems. There is a sample - Data Layer Sample, this shows how to work with aWearableListenerService, to produce and consumeDataEventsand effectively work with theDataLayer
– Mr.Rebot
Nov 13 '18 at 21:21
One question to ask yourself is: what is the desired behavior if the user connects a wearable after your phone app has run? Would you want the data from the phone app to appear on the watch? If so, then you do not want to check for connectivity - write theDataItemsunconditionally so that they will available if/when your watch app is run, now or later. OTOH, if your data sync only makes sense if both devices run your app concurrently, then you probably do want to check for connectivity.
– String
Nov 18 '18 at 2:47
add a comment |
I've got an app that utilizes a Wearable and am using the Listener Service, sending messages and synchronizing DataItems in between. This app does not have to use a Wearable. What I want to know is if my app should always check if a Wearable is connected before deciding if I should send data/messages?. If yes, what is the best way to check if Wearable is connected. Thank you very much!
android wear-os android-wear-data-api
asked Nov 12 '18 at 18:48
David Nuno
82
I've got an app that utilizes a Wearable and am using the Listener Service, sending messages and synchronizing DataItems in between. This app does not have to use a Wearable. What I want to know is if my app should always check if a Wearable is connected before deciding if I should send data/messages?. If yes, what is the best way to check if Wearable is connected. Thank you very much!
android wear-os android-wear-data-api
android wear-os android-wear-data-api
asked Nov 12 '18 at 18:48
David Nuno
82
asked Nov 12 '18 at 18:48
David Nuno
82
asked Nov 12 '18 at 18:48
David Nuno
82
asked Nov 12 '18 at 18:48
David Nuno
82
asked Nov 12 '18 at 18:48
David Nuno
82
82
I think it is a required step to check if there is any connected device before sendingdataItems. There is a sample - Data Layer Sample, this shows how to work with aWearableListenerService, to produce and consumeDataEventsand effectively work with theDataLayer
– Mr.Rebot
Nov 13 '18 at 21:21
One question to ask yourself is: what is the desired behavior if the user connects a wearable after your phone app has run? Would you want the data from the phone app to appear on the watch? If so, then you do not want to check for connectivity - write theDataItemsunconditionally so that they will available if/when your watch app is run, now or later. OTOH, if your data sync only makes sense if both devices run your app concurrently, then you probably do want to check for connectivity.
– String
Nov 18 '18 at 2:47
add a comment |
I think it is a required step to check if there is any connected device before sendingdataItems. There is a sample - Data Layer Sample, this shows how to work with aWearableListenerService, to produce and consumeDataEventsand effectively work with theDataLayer
– Mr.Rebot
Nov 13 '18 at 21:21
One question to ask yourself is: what is the desired behavior if the user connects a wearable after your phone app has run? Would you want the data from the phone app to appear on the watch? If so, then you do not want to check for connectivity - write theDataItemsunconditionally so that they will available if/when your watch app is run, now or later. OTOH, if your data sync only makes sense if both devices run your app concurrently, then you probably do want to check for connectivity.
– String
Nov 18 '18 at 2:47
I think it is a required step to check if there is any connected device before sending
dataItems. There is a sample - Data Layer Sample, this shows how to work with a WearableListenerService, to produce and consume DataEvents and effectively work with the DataLayer– Mr.Rebot
Nov 13 '18 at 21:21
I think it is a required step to check if there is any connected device before sending
dataItems. There is a sample - Data Layer Sample, this shows how to work with a WearableListenerService, to produce and consume DataEvents and effectively work with the DataLayer– Mr.Rebot
Nov 13 '18 at 21:21
One question to ask yourself is: what is the desired behavior if the user connects a wearable after your phone app has run? Would you want the data from the phone app to appear on the watch? If so, then you do not want to check for connectivity - write the
DataItems unconditionally so that they will available if/when your watch app is run, now or later. OTOH, if your data sync only makes sense if both devices run your app concurrently, then you probably do want to check for connectivity.– String
Nov 18 '18 at 2:47
One question to ask yourself is: what is the desired behavior if the user connects a wearable after your phone app has run? Would you want the data from the phone app to appear on the watch? If so, then you do not want to check for connectivity - write the
DataItems unconditionally so that they will available if/when your watch app is run, now or later. OTOH, if your data sync only makes sense if both devices run your app concurrently, then you probably do want to check for connectivity.– String
Nov 18 '18 at 2:47
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53268324%2fshould-android-app-check-if-wear-is-connected-before-sending-data%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53268324%2fshould-android-app-check-if-wear-is-connected-before-sending-data%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think it is a required step to check if there is any connected device before sending
dataItems. There is a sample - Data Layer Sample, this shows how to work with aWearableListenerService, to produce and consumeDataEventsand effectively work with theDataLayer– Mr.Rebot
Nov 13 '18 at 21:21
One question to ask yourself is: what is the desired behavior if the user connects a wearable after your phone app has run? Would you want the data from the phone app to appear on the watch? If so, then you do not want to check for connectivity - write the
DataItemsunconditionally so that they will available if/when your watch app is run, now or later. OTOH, if your data sync only makes sense if both devices run your app concurrently, then you probably do want to check for connectivity.– String
Nov 18 '18 at 2:47