Feature request: Any kind of data exchange between datafield & widget (or app)

Former Member over 10 years ago

Hi,

I'm building (actually built already) 2 custom SimpleDataFields that record flight times (off-block and takeoff time + landing and on-block time, based on movement and speed values). These work nicely. I've now realized that it would be very nice to be able to sync that data somewhere off the watch. What I'd like would be to have a widget or an app, separate from the data fields, with which to sync the times collected on the watch to a json service somewhere on the Internet. I probably could do it from the datafields themselves but, as my phone will be in flight mode when flying, the requests will fail. Thus, some kind of a store-and-forward mechanism is needed.

An alternative would of course be to build an app with a "sync now" screen and have that same app publish also the datafields. I've tried reading through the documentation but I am not sure if this is possible/allowed either.

Any ideas?

Best regards,
Samuli Sorvakko

jim_m_58 over 10 years ago

There is no way to have shared data between multiple widgets/apps/etc. Each one has it's own Object Store and they are independent. (widget "a" can't access app "b's" data).

Also, you can't do makeJsonRequests from a datafield (you can't do Comm of any kind from a datafield).....

You probably could do something using Comm to pass info from a widget to app by writing something for your phone, but data fields can't use it.

Former Member over 10 years ago

I know it's not currently allowed, that's why this is a feature request :)

Basically what I'm asking is for allowing some kind of a data exchange / shared storage pool between the various app types. It could even be just a shared object store, with the internal naming conventions being left up to the developers. Basically it would allow for smarter datafields and watchfaces that could be configured/augmented by widgets/apps and report back to them, opening up the possibilities for more user-friendly collections of apps.

HermoT over 10 years ago

I know it's not currently allowed, that's why this is a feature request :)

Basically what I'm asking is for allowing some kind of a data exchange / shared storage pool between the various app types. It could even be just a shared object store, with the internal naming conventions being left up to the developers. Basically it would allow for smarter datafields and watchfaces that could be configured/augmented by widgets/apps and report back to them, opening up the possibilities for more user-friendly collections of apps.

I agree, if this was possible it could help solve issue of non-user-configurability on watchfaces. So a watchface could pull values from a shared memory that was pulled from the internet by a companion app.

Brandon.ConnectIQ over 10 years ago

This has been suggested before in the last, and was something that was conceived in some of the early designs of Connect IQ. As it stands, we don't plan to implement a way to share the object store between apps. That doesn't mean it won't ever happen (as I recall from our discussion when it came up last, shared data was part of AlphaMonkey's original vision), but right now it's not a good fit for the direction we're going and the way the ecosystem has been built.

Dacrosse over 2 years ago in reply to HermoT

Good news. We just released a service that enables communication between apps. You can learn more at https://dacrosse.com

Dacrosse over 2 years ago in reply to Former Member

Good news. We just released a service that enables communication between apps. You can learn more at https://dacrosse.com