Whether they do have ulterior motives or not, the effect is that innovation is stifled.
Yes, I know the circumstances are different, but I do think it's ironic.
or it was just the typical double speak from Jobs until they were able to launch their walled garden. Anyone else remember when iPhone users were told they were holding the iPhone wrong during Antennagate? [0]
[0] https://www.engadget.com/2010-06-24-apple-responds-over-ipho...
>the effect is that innovation is stifled.
There's no such thing as PWA. There are several dozen of standards, and any combination of them is called PWAs by various people. And quite a few of those combinations work perfectly fine on Apple devices.
What's worse is that too many of those standards are extremely badly designed (service workers) or are pure Chrome-only "standards" rammed through standards bodies (Bluetooth, HID etc.).
They just don't get their cut from it, so, not a priority.
--- start quote ---
Talking about mobile phones and tablets, a Progressive Web App is installable with offline capabilities using the following browsers and app stores:
- iOS and iPadOS
Safari (since iOS 11.3), AppStore (since iOS/iPadOS 14, with some limitations), Mobile Configuration for enterprise distribution.
--- end quote ---
Sounds like you're setting a double standard when Apple also runs ads on their devices[0] as well as selling their user's private data[1]
[0] https://stevestreza.com/2020/02/17/ios-adware/
[1] https://www.macrumors.com/2021/11/26/apple-italy-fine-user-d...
Anyone who claims those are equivalent to what is going on on the web is being dishonest.
Neither of the articles even claims that Apple was “selling user data”, so that’s a straight up lie.
I can’t help you if you are going to post links that don’t say what you claim they are saying.
Why did Spotify and Pax Labs make PWAs again?
Spotify creates native apps for everything. "PWA" aka the web player is there for devices that don't have a native app yet, and for embedding.
Remember that Apple doesn't allow other web browser engines in any application. Imagine if an Electron application on iOS just decided to ship with it's entire, own browser engine. We would have super-bloated apps like our desktops, and if a security flaw was found, good luck getting all those apps to update.
In a way, Apple knows that allowing other browser engines means:
1. Chromium-based browsers just increase their monopoly, Firefox continues stagnation by almost all odds
2. The Electron mess on our desktops will claim new territory on our phones and bring security problems with it
Not very appealing. Limiting competition? When your only realistic competition is Chrome with it's 80%+ dominance, I don't think a regulator would have a problem with that.
I'll admit, though, I'm in the "I really want native Mac apps" minority :)
People only really get active about bad divergence from expectations.
People do voice very positive opinions, but nobody really voices indifference.
Further, even extremely opinionated people are usually only opinionated about a few things. Most people are indifferent to most things.
Plus, security is somewhat less of a concern when the application only accesses a limited site and isn’t for general purpose browsing for untrusted sites.
But they can put those updates out whenever they want, so that doesn't go against the security argument at all.
It started as a Konqueror fork mostly because Jobs wanted a browser on OS X and Ken was initially tasked with it (back then the mac had IE for mac). One person writing a browser from scratch even back then seemed an impossible challenge so he took a look to see if he could use most of Konqueror as an initial starting base.
[0]: The book has some interesting stories, but I find it hard to recommend because it's weirdly written for an extremely non-technical audience (using grandma like analogies to explain basic concepts, the analogies are so basic they do more to obscure than explain - e.g. the filesystem is like a 'cabinet for files'). It doesn't often get into the weeds of the interesting technical details - which is disappointing since 90% of readers are probably technical. The stories in it are still good though and Ken has a lot of insight into the iPhone development story since he was there.
I disagree with this word gymnastics, it is Apple-ogism. It takes just a brief look at other decisions they've made to easily see that it is about user lock-in which fits in with their general philosophy. It is not great that they are stifling innovation at all, conflating it with browser dominance is a separate thing.
Apple sets the rules for its own products. Why didn't "open" win? Why for whatever reason is Apple still #1 in the mobile space?
Perhaps users agree with Apple.
I can write a browser using WXWebView that wastes battery outside the rendering code, and Apple won't stop me. I can write a maps application that wastes battery, and Apple won't stop me. But if I write a web rendering engine that wastes battery, I have crossed a line? A line that is so important not to cross that Apple won't even let me try to write a rendering engine that uses less battery than WXWebView? I cannot believe that anybody would buy that argument without marketing distorting their thoughts.
Ah yes. Everything can be explained by marketing, and marketing alone. Poor, poor Google, and Samsung, and so on, who are struggling to find the money and the power to make people buy Android phones through the power of marketing.
Perhaps, just perhaps, I'm going on a limb here, Apple actually makes a phone that people want?
Apple has been a marketing-driven company for decades now and is better at it than any other tech company by a country mile. It's why they bought Beats, not for their technology, but for their marketing prowess. The other companies you listed pick features that are better on their devices to market. Apple's marketing department figured out long ago that no such restriction is necessary.
Right now, in this very thread I see no such discussion.
> They are also worse for privacy
> They are worse for security
Worse than what?
> The shoe fits.
It doesn't fit, not really. It's gross incompetence and ignorance to explain everything by marketing and people being stupid.
Because what you're saying, is that a good chunk of people on HN are stupid and are "duped by marketing". That I am stupid and am duped by marketing. However, I've seen and tried the alternatives, and I found them lacking.
Look at the first comment you replied to. It's about how Apple restricts how you can browse the web for user lock in but has convinced people it is for the sake of their battery.
> Worse than what?
Worse than Pixels, Android One devices, and ChromeOS devices currently. There are several open source focused devices in the pipeline that have better security design than iOS devices as well but are not yet ready.
> That I am stupid and am duped by marketing.
I did not say you are stupid. I said that people are duped by marketing, and I gave examples. I even pointed out that technologists can be duped, and they are smart in the field they were duped in. Apple's marketing department is smart, and Apple's other employees are smart for supporting their efforts, though when they get caught parroting marketing talking points that are clearly false, it can be embarrassing.
Ah yes. That comment is obviously wrong, and your comment is obviously correct because you are right, and the other person is wrong. Is that how this works?
> Worse than Pixels, ... and ChromeOS devices currently.
So. Pixels and ChromeOS are made by Google. You know,
- 80% of Google's money comes from online advertising. And this advertising relies on far-reaching privacy invasive tracking
- Google's own employees admitted that they have no idea how to turn the various methods of tracking off. Among others location tracking is so intertwined in Google's products that it's impossible to turn it off at all
Yup. These devices are surely worse for privacy than iPhones which go as far as limit tracking at the OS level.
Can't attest to the devices current security. Given Android's spotty track record of updates, I wouldn't hold my breath for AndroidOne. Oh. And Pixel 3 which was released in the ancient times of exactly three years ago will no longer receive any updates. So yeah.
Meanwhile the iOS 15 which was released this September is available on iPhone SE from 5 years ago.
> There are several open source focused devices in the pipeline that have better ... but are not yet ready.
I yes. Imaginary non-existent phones. In that case I have a phone that's better than any of those, and better than iPhone, and better than Pixel 6. Care to buy one?
> I said that people are duped by marketing, and I gave examples.
No, you didn't. What you did, was make overly broad statements that are either pure speculation, or can be easily refuted.
Read my comment in the context of what it was responding to. You seem to have grossly misunderstood it.
> Yup. These devices are surely worse for privacy than iPhones which go as far as limit tracking at the OS level.
iOS devices do not support end-to-end encryption of message backups, do not support allowing a user to run apps on the device without telling Apple, and do not support getting a user's location without telling Apple. Despite what you may infer about each company's motives, each company's actual actions show a very clear difference in privacy on their devices. Apple is motivated to make money by any means it has available. If it can make money by charging users more for devices and violating their privacy by marketing their devices as being better for privacy, it will do so, and we can see that this is happening right now.
> Meanwhile the iOS 15 which was released this September is available on iPhone SE from 5 years ago.
So you admit an iPhone from 6 years ago is insecure. The fact that only recent devices from either vendor are secure is the same for both, so a user who cares about security will only use a recent device. The difference is that recent devices from Google are far more secure than recent devices from Apple.
> Imaginary non-existent phones.
I was just illustrating that there will be more options in the future. Apple knows about the security features offered by current and future devices but despite that hasn't tried to match those security features and instead contents itself with merely marketing security.
> No, you didn't.
Read my first post. You still haven't refuted it.
I've read the comment an the context. It says "that person is wrong, only my opinion on what Apple does its right"
> Despite what you may infer about each company's motives, each company's actual actions show a very clear difference in privacy on their devices.
Indeed it does. And Google is many magnitudes more invasive than Apple. Including, but not limited to "applications which have location tracking disabled can use location tracking information from another Google application" https://www.independent.co.uk/life-style/gadgets-and-tech/ne...
> So you admit an iPhone from 6 years ago is insecure. The fact that only recent devices from either vendor are secure is the same for both
It's emphatically not the same for both:
- Apple: support phones for up to five years.
- Google: supports its own "flagship phones" only for three years.
HN poster: see, they are the same.
> I was just illustrating that there will be more options in the future.
Once again: I'm not interested in fantasies and comparisons against non-existent phones.
> Read my first post. You still haven't refuted it.
I mean, your approach to argument is "I'm right just because I say is right", so nothing will dissuade you.
This is pointless. So, adieu.
Where does it say that? I'll repeat the context right here:
"> Right now, in this very thread I see no such discussion."
The context is that I was pointing out that there is a discussion about what you claimed there was no discussion about. Nowhere did I say that I'm right and they're wrong (though it remains the case that none of my points have been refuted).
> applications which have location tracking disabled can use location tracking information from another Google application
Google does this on iOS as well. In respect to what information applications can share on the server, there is no difference between iOS and Android. The privacy differences that do exist between the platforms are the ones I listed, where iOS does a lot of data collection that cannot be disabled, while Android has no such problem.
> HN poster: see, they are the same.
A user who cares about security only cares about which device provides usable security. None of the Apple devices do. All the Pixels that are receiving security updates do. The choice for a user who cares about security isn't between some five year old iOS devices that provide limited security and other five year old Android devices that provide limited security (worse system updates but better application updates) but between any iOS device (including recent ones) that provide limited security and recent Pixel devices that provide superior security. How long they continue to receive system updates (or application updates) beyond replacement time is meaningless.
> I mean, your approach to argument is "I'm right just because I say is right",
I provided reasons why the battery excuse doesn't make sense. Why do you keep pretending I haven't given any reasons?
Why would this be a believable excuse? you can install a Firefox skin of WebKit on iOS and this skin could maybe be terrible on battery usage. A good default browser like on laptops is good enough for battery, people who care about it will use Safari, the obvious reason Apple is doing this is to prevent competition, so if Apple fucks with WebGL then you can't have say a WebGL based mobile game that would go around the Apple Store.
I wish all phone manufacturers actually understood that
/me glances at my Pixel 3XL with 3430 mAh batt
I switched to a used iPhone and was bummed my 8+ had a "small" ~2400mah battery compared to my Android phone, which was 3100. Then I actually started using it. Even though the Android phone had an OLED screen, it would absolutely melt the battery.
I have so little "battery charge anxiety" now it's not even funny. I don't even bother to charge it above 80-85% most of the time...and the battery life estimator says the battery is down to 82% capacity.
If apple actually went up on their battery sizing they could easily achieve Monday to Friday battery life on something like the iPhone SE.
Current phone has 12GB of RAM which is a bit extreme given I rarely seem to use more than 6GB. More Sub $250 phones are creeping up to 6GB which makes for a nicer experience for those on tight budgets.
Now if only we could solve the lack of updates most Android phones experience.
Why people think Android=Pixel is beyond me.
So I don't buy any of the Apple's excuses when they actively cause anti-competitive harm.