4 ms·
None of those are intrinsic to sideloading. Those private APIs also mean Apple gets to play favorites with its own apps in a lot of ways, which they have. > A
by jorvi 3y ago
None of those are intrinsic to sideloading.
Those private APIs also mean Apple gets to play favorites with its own apps in a lot of ways, which they have.
> And I assure you that it wouldn't be a tiny percentage of users if companies like Facebook would use it to do a run-around Apple's privacy controls.
This was addressed by my Fortnite example already.
All in all, if you don’t like sideloading, you’ll never have to engage with it.
I hate this kind of attitude, and it’s the same as the office lovers trying to prevent WFH as much as possible. Stop trying to lock us both in the cage because you’re too afraid to step out of it.
- threeseed 3y agoI will have to engage with side-loading though. Apps like Facebook, Instagram, Twitter etc will immediately move because they would be able to side step Apple's privacy controls. Billions are on the table here. Outlook will move because they can tie the app to Edge which will now be able to use JIT. And a bit hypocritical to say that I should stop locking us both in a cage when it's your choice to be in there. Support companies who allow side loading. Win win for everyone.
- jorvi 3y agoI will refer you to my Fortnite example for a third time. Good day.
- Sevastopol 3y agoEpic and Meta are not the same size.
- scarface_74 3y ago> Those private APIs also mean Apple gets to play favorites with its own apps in a lot of ways, which they have. While I shouldn’t be surprised, I’m always surprised that a technical audience brings up the “private APIs” bugaboo. Once you make an API public, you have to continue to support it warts and all. Apple should dog food their own stuff before they make it public. On the other hand, do you expect Apple to make every API available to random developers?
- goosedragons 3y agoShould Apple be allowed to kneecap competitors products (e.g smartwatches?)? They pretty clearly keep APIs to themselves to make their own products seem better. It's one thing to keep an unpolished rapidly changing API out of view and another to prevent competitors from doing the same thing on your platform that your 8th generation product does.
- scarface_74 3y agoDo exactly which private API is used to “kneecap” competitors?
- goosedragons 3y agoThings like replying to messages via. the watch. On iOS the ONLY watch allowed to do this is of course the Apple Watch.
- scarface_74 3y agoThis is not true. You can reply to messages from Slack on your watch and it use to be better when they had a Watch app 5 years ago. https://www.techradar.com/news/slack-is-dropping-its-apple-watch-app-but-youll-still-get-messages-to-your-wrist https://www.techradar.com/news/slack-is-dropping-its-apple-w...
- goosedragons 3y agoWhere did I mention Slack? I say "messages" and you assume Slack? Seriously? Also WTF does that article have to do with non-Apple smartwatches being unable to reply to message notifications on iOS? You can not reply to SMS or iMessage notifications on non-Apple smartwatches. It's not allowed.
- scarface_74 3y agoWhat are you talking about then? Using a third party app that can reply to your iMessages or SMS? Why in the heck would I trust a third party for my SMS messages? But as far as third party watches replying to SMS/iMessages, they could do it just like you respond to messages from cars before CarPlay was a thing - you support the appropriate Bluetooth profile. Microsoft did it on computers without official Apple support https://www.theverge.com/2023/3/24/23654672/microsoft-phone-link-hands-on-imessage-ios https://www.theverge.com/2023/3/24/23654672/microsoft-phone-...