Live data from Hacker News

Apple restricts Pebble from being awesome with iPhones

ericmigi.com

501–510 of 1001 posts

Re: Apple restricts Pebble from being awesome with iPhones

#501

Earlier quoted context omitted.

Think about why they ask for access in the first place - it's because camera access or screen access might be unexpected for the app you've just started. Or maybe you don't trust the app with your camera (looking at you, Instagram). QuickTime Player is already on your Mac and you already know what it does when you launch it.

I sure didn't know QuickTime Player could read my screen or listen to my microphone...

There are millions of ways you implicitly trust Apple software to not violate your trust when you use their products. The whole point is Apple can gauge whether it is appropriately stewarding that trust in first party code much better than it can with third party code.

Re: Apple restricts Pebble from being awesome with iPhones

#502
post #448

Earlier quoted context omitted.

You can thank Apple for the Lightning connector and App Store too, for all the good it does everyone in the EU. If a company uses their power to prevent competition with their own products or services, the market's jurisdiction reserves the right to restore competition to their market and prevent the harms inherent to monopoly abuse.

I probably dont get your sarcasm. But I never had a problem with Lightning. In the long run, I like the switch to USB-C... But when I got my first iPhone, USB-C wasn't invented yet, so... Also, I like the AppStore for its reviews, and would actually NEVER activate an alternative appstore. No need to weaken my security on purpose. I know, its apparently an unpopular opinion here, but that is mostly because many people…

You can't run an ad-blocker and you browse the web with JS turned on in Safari, but your Iphone is secure?

yeah ok

Re: Apple restricts Pebble from being awesome with iPhones

#503

I have a very capable smartwatch and it's ridiculously bad how hobbled it is on iOS. I'm glad to see this article specifically highlight the issues, and how it's 100% Apple's intention to make non-Apple wearables on iOS terrible.

I too have a very capable smartwatch (fitness watch - Garmin Fenix) and it's remarkable how different my experience with messages and actions are relative to the experience of Garmin users with Apple phones.

Garmin Connect always runs in the background on my Android phone, watching for notifications, pulling data from and pushing data to Garmin servers on my behalf even when I'm not using the app. It's third-party, but it's reasonably well-written and doesn't nuke my phone battery or data plan - Android doesn't need to protect me or their reputation from Garmin. I can always check the weather or look at my daily workouts or whatever on my watch and trust that it's recently been upodated by the phone app phone. Garmin users with Apple phones complain that "Garmin doesn't work" after every iOS update that further hobbles the Garmin background service.

I get text notifications on my watch for any Android apps that provide notifications, and relevant ones (like text messages, whether SMS or RCS) provide an option to reply from the watch. I tap the top right button on the watch and scroll to "OK" or "Thanks" or "Can't talk right now" or whatever one of a half dozen canned responses covers 90% of my needs in this mode, and don't have to dig my phone out of my backpack or otherwise interact. Emails, calendar appointments, clock stuff, music controls, etc. all work over the watch. It's just as privileged as the phone, I'm not concerned about my Garmin intruding on my privacy as protected by Android, I wear the watch 24/7 and it has more data on me than the phone!

Re: Apple restricts Pebble from being awesome with iPhones

#504
post #299

Earlier quoted context omitted.

It doesn't need to be a plugin ecosystem - no third party code needs to run within the iMessage processes/sandboxes/containers. In fact, no third-party code needs to run at all on the phone - all that's needed is to expose an API over BLE that allows previously authorized external devices to query/send messages.

In defense of the "it's security!" position (which is not mine): I think they mean a similar vulnerability could exist on the client side of the API. As in someone sends manipulated media that targets a vulnerability on the third party device, the media gets forwarded through the API, now that compromised third party device does bad things over the API. Personally, I think that it's really just a convenient third par…

Following that line of reasoning, the Apple should ban WhatsApp and other messaging systems because they can add potential vulnerabilities.

Re: Apple restricts Pebble from being awesome with iPhones

#505
post #179

Earlier quoted context omitted.

And GP is saying that that’s totally okay.

I am saying folks who use Linux do not know how to utilize their time well. It’s tongue in cheek at the commentary to the GP but hope that makes more sense to you.

[flagged]

Re: Apple restricts Pebble from being awesome with iPhones

#506

I have a very capable smartwatch and it's ridiculously bad how hobbled it is on iOS. I'm glad to see this article specifically highlight the issues, and how it's 100% Apple's intention to make non-Apple wearables on iOS terrible.

it's pretty frustrating how "apple people" just don't care that it's apples fault. i routinely hear my wife mutter "i hate google so much!" when a google maps integration is being intentionally hobbled to keep her using apple maps. or when she has trouble managing rcs conversations because somebody in our social world has the gall to be on an android phone.

I don't like that iMessage = lock-in, but everyone else needs to make a better standard first. We got cross-platform encrypted covid chat before we got this. RCS has an FBI "do not use" warning on it because there's no E2EE. And the reason people don't want green bubbles is cause they always screw up the group chat.

Re: Apple restricts Pebble from being awesome with iPhones

#507
post #293

Earlier quoted context omitted.

Couldn't you make that argument for literally any anticompetitive practice? Like in the 1990s: "Microsoft isn't making an OS for people that want to try different browsers"

I honestly don't care about Microsoft bundling a browser. The real problem was that they intentionally broke web standards to push websites to "work best on Internet Explorer," so even those who chose not to use Windows were caught up in it. Whereas, Android users aren't affected by what Apple does here. They still bundle Edge, and keep setting it to default. But idc, it's just one of 1000 reasons I don't use Windows…

Apple do this too with their products - but in more subtle ways.

For instance, try to play a video game on MacOS. While Vulkan is available on every playform, it's not available on MacOS or iOS despite the fact that it would take an engineer at Apple a weekend to implement (figuritively speaking). Apple are also killing off OpenGL support for MacOS.

Generally, Apple deliberately build a "dependence ecosystem" for their consumers on the product side while also actively preventing engineers from using portable technologies on their platforms.

The fact that MacOS is as open as it currently is is a miracle and I am sure executives hate that.

They create the fastest and most ergonomic mobile hardware on Earth but, outside of web browsing, video editing and some engineering workloads, there's very little you can actually do on it.

Re: Apple restricts Pebble from being awesome with iPhones

#508
post #321

Earlier quoted context omitted.

I like the ecosystem. If you don’t, choose another ecosystem.

"Love it or leave it" - why not make it better?

Allowing support for a rich ecosystem of mediocre smart watches does not move the needle on making it better for me personally. And Apple probably has done the market research to confirm most of their customers are like me and not like Pebble users.

Re: Apple restricts Pebble from being awesome with iPhones

#509

I have a very capable smartwatch and it's ridiculously bad how hobbled it is on iOS. I'm glad to see this article specifically highlight the issues, and how it's 100% Apple's intention to make non-Apple wearables on iOS terrible.

I honestly don't think Apple products are a smart choice for tech savvy people anymore if they ever were. You are paying a premium for easy to use, convenient servicing, and the aesthetic.

Re: Apple restricts Pebble from being awesome with iPhones

#510
post #399

Earlier quoted context omitted.

Why can't people choose which prescription drugs they want to use?

They should be able to.

That would be a good way to reduce the efficiency of the remaining antibiotics very quickly.

(But also, this kind of thing is exactly why the analogy doesn't even make sense.)

Post reply on HN