Comment by Wowfunhappy
2 years ago
The Pebble was very obviously hampered by iOS limitations. In order to offload any code to the phone, you either had to write the code in Javascript (so it was basically a web app) or direct the user to manually download a separate companion app from the App Store. If iOS killed the companion app because it hadn't been opened on the iPhone recently (because, y'know, you were using it on your watch and not your phone), you had to manually relaunch the app on your phone.
This is all before even getting into things like ecosystem integration.
The Pebble was released in 2013. The two way communication SDK with Pebble was released in May of 2013. In February of 2015, the 2.0 Pebble SDK was released with further integrations.
The first iWatch was announced in September 2014 and released in April of 2015.
The Pebble was discontinued in 2016.
What integrations are you expecting Apple to have released prior to its own release? What functionality did iOS lack that android provided that hampered Pebble's development on iOS?
"The first iWatch was announced in September 2014 and released in April of 2015."
Just a side note: apple has in past started limiting other companies products as soon as they decide to create a competitor and sometimes years before it hits the market.
IIRC Spotify has been bitten by this at least once, which resulted in a lawsuit.
What limitations did Apple place in 2013 (or 2014 or 2015) that reduced the functionality of Pebble in light of a forthcoming iWatch?
If it was a "it worked and then Apple took away this API that we were going to use" that would be one thing. If it was "the iPhone didn't have the functionality for other devices to read messages over BlueTooth until 2015 with iOS 8" - that's a different claim.
17 replies →
The complaint is outlined directly in the document
https://x.com/ericmigi/status/1770832870870827149
Well to begin with, it is my understanding that the specific limitations listed still exist. Can Bluetooth devices remotely start apps now, or keep them in the background? I only used Pebble as an example because I owned a Pebble, I'm not familiar with Garmen's watches.
But seperately, I think it's really bad for innovation if no new product categories can exist unless Apple makes them first! You can imagine a different type of company that would have been delighted to work with Pebble and add functionality to their operating system, because third party compatibility strengthens their core product.
And of course, if this were the Mac, Pebble would not have needed Apple's cooperation...
Bluetooth devices can start apps in the background. I have two that do this, Beddit and <redacted because they famously don't let you mention you have one>.