I get your point but on the other hand... there is absolutely zero added value for using a smartwatch if you are dependant on a phone being connected unless you want to use a sensor on the watch apart from the HR sensor because that can be easily replaced by a HR chest strap, which I guess most people use anyway since they are way more accurate.
So the reasoning makes senses from a marketing standpoint but there is an alternative as well.
Add a developer option that unlocks the wifi as well and have it state in no uncertain terms that this is at your own risk.
At least that would allow developers to use the feature while still protecting the people that have no clue how their devices work.
But I am old enough to realize that companies rather limit knowledgeable people to prevent other people to blame their own ignorance on the company/brand :D
If there is a wifi connection, things like makeWebRequest will use that today. Same with LTE. OAuth needs the phone though, as you need that to interact.
Hey Folks,
It's been a long time in the works, but we've finally opened this up a bit. With the announcement of the 3.1.0 Beta SDK we have finally brought WiFi syncing to Connect IQ. Here is the SDK announcement: https://www.garmin.com/en-US/blog/developer/connect-iq-3-1-beta-now-available/