101–110 of 208 posts
very true, and why I got out of mobile app development when I noticed like a decade ago, scrubbed my whole resume of it to switch to other kinds of dev
I'm surprised there is still demand for that though, but I've found other solutions to be good enough, when a phone is involved
Earlier quoted context omitted.
If you use this CSS liquid glass effect in your app, Apple will reject it from the App Store. If Apple uses this CSS liquid glass effect in their apps, it'll pass App Store review just fine. Do you see the issue now?
>it'll pass App Store review just fine. Do you have any evidence of this claim? It's possible that neither Apple or third party developers are able to ship apps through the app store with it.
Earlier quoted context omitted.
I wanted to be outraged at apple, but I really can't. Read WinAPI documentation and try to count all "reserved" parameters for example. OS developers build features just for internal use all the time. Granted, this is just UI tweak so I'm not convinced it has to be private, but they probably just don't want to have to maintain that forever.
The key distinction is the withholding from your competitors part. WinAPI may have a ton of features labelled "pls no use thx" but MS doesn't block you from distributing a program that uses them anyway.
Spent so much time trying to repro some functionality only to realize that Windows has an allow list for what apps it listens to for certain APIs.
Earlier quoted context omitted.
>it'll pass App Store review just fine. Do you have any evidence of this claim? It's possible that neither Apple or third party developers are able to ship apps through the app store with it.
Why would Apple go through the App Store review process for their first-party apps?
Earlier quoted context omitted.
I wanted to be outraged at apple, but I really can't. Read WinAPI documentation and try to count all "reserved" parameters for example. OS developers build features just for internal use all the time. Granted, this is just UI tweak so I'm not convinced it has to be private, but they probably just don't want to have to maintain that forever.
Yeah, this seems reasonable to me. The better thing to get annoyed at Apple for is being slow to implement web standards. I guess you could make the argument that they are choosing to work on stuff like this instead, but I think that’s a weak argument.
Now that Safari supports the HTML5 date picker (since iOS 14.1 - five years ago), this is more of a meme than fact-based reasoning. Unless you believe Google including something in Chrome automatically makes it a "standard."
I have a list (unfortunately on a device I can't access now) of web standards that are supported on Safari and Firefox, but not on Chrome. I need it because one web site I work on is 100% Safari users (about 800 people), and another is mostly Android (about 70%). So I need a cheat sheet of which does what.
Earlier quoted context omitted.
Wait so are all non-standard CSS attributes "anticompetitive"? This seems like wild hyperbole. Is Google's "-webkit-tap-highlight-color" also anticompetitive? Should we ban the current practice of shipping proprietary CSS attributes while sometimes also proposing them for standardization? It's just really hard for me to read that as a legit complaint.
If you use this CSS liquid glass effect in your app, Apple will reject it from the App Store. If Apple uses this CSS liquid glass effect in their apps, it'll pass App Store review just fine. Do you see the issue now?
Citation needed.
The blog article speculates this, but there is no proof.
Earlier quoted context omitted.
> Private/secret APIs in Windows were a prominent part of the US and EU antitrust lawsuits against Microsoft in the 90s/00s. It mattered because Microsoft had 95% of the operating system market at the time and was using its monopoly position to take over the web, even after signing a decent decree with the US government.
Edit: It can probably be argued that Apple is a acting like a monopolist in one or a few areas though? The current web monopolist (Google) was coincidentally founded 2 months after the US antitrust lawsuit against Microsoft was decided (july - september 1998). Similarly meh results with US vs Google two weeks ago.
I don't think that's a credible argument. Apple, at best, has about 55% smartphone marketshare in the United States--and significantly less in most other countries.
Remember, having a monopoly isn't itself illegal; it's using the monopoly to disadvantage competitors, especially in emerging markets, which was what the Microsoft case was all about.
I don't think there's a legal justification for suggesting that Apple creating a private feature only they can use--for now--gives them unfair advantage in the market.
I wouldn't be surprised if Apple makes it a public feature in a future release of iOS 26.
My guess would be that the App Store apps on iOS and macOS and the Music app rely on these seamless web views for a lot of their dynamic layout content.
Providing an OS feature only to first-party programs is a plainly anticompetitive practice. Using your privileged position in one market (cell phones/cell phone operating systems) to gain an advantage in another market (smart phone applications) that you withhold from your competitors is a textbook case.