It’s not a new feature either. I used it at least 4 years ago. Plugged my phone into my monitor, Bluetooth controller, and I could play games on my nice monitor. It’s even easier now with USB-C I’d imagine, I was using the lightning-hdmi dongle.

Was this article written with AI or just by someone who has no clue what they are talking about?

During his testimony on Thursday and Friday, Bloomberg reports Giannandrea took the time to mention a feature of Safari for iOS 17 that wasn’t reported on for its introduction. The quietly introduced feature allows users to set a different browser when using Private Browsing than the default.

“Different browser”, what they mean is “different search engine”. Even if this author was competent this article is a nothing-burger. Not sure how setting a different search engine in private mode has anything to do with the Google antitrust trial.

I really hope they expand this button in software later. Long press as the only activator is absurd. How about single? Double? Triple? Short-long?

I hate that the only option is long. Also I wish I could change the behavior based on context (is the phone locked, what app is active, etc). I don’t need camera or flashlight if the phone is locked, they are right there but elsewhere that might be nice.

I’m leaning towards camera in video mode as what I set it to, since getting to video mode takes longer than I’d like in most cases, even from the Lock Screen.

This sub sucks. No really, it’s be great if we could actually have conversations about Apple products and decisions instead of it being full of people that just want to dunk on Apple with uninformed and tired takes.

There is a legit way we can talk about the dongle, how it’s existence makes perfect sense, and how there are cheaper/better alternatives on the market. Instead we have “Hur hur hur, Apple expensive, what do you expect? Are you new?”. It’s not intelligent, it’s not right, and it completely ignores so many realities.

I mean it makes sense, the Pro 2’s JUST released a little while ago and some people will want to go full USB-C as soon as the iPhone does. In fact I’m a little impressed with Apple, we will see if the Keyboard and Mouse follow suit.

This might be the most sane take in the this thread.

Yes, ideally it would all match up but I’ll reject PRs that want to rename a bunch of files/fields/properties/columns/etc because marketing/business want to call it something else. Also you have to pick your battles, sometimes it’s just not worth fighting it.

We have some things that were named badly on the backend a decade or more ago, in our API we name them correctly (example “qty” on the backed, “quantity” in the API). We will NEVER go back and change the old name, it’s not going to happen. It would take a massive effort for no real gain.

Also parts of our API are (semi-)publicly available and so we take that as an opportunity to rename certain things for “public consumption” because we call something different internally (with justification) but there is no good reason to make external people learn our internal lingo/concepts.

Lastly I’ve learned over the last 15+ years in the industry that just about every “black and white rule” is a bad one. You shouldn’t have a slavish devotion to a rule just because it is a “rule” that someone slapped down at some point. It’s like the REST purists who bitch and moan about “that endpoint isn’t RESTful”. Get out and write some real software with real business requirements then get back to me.

I’m not saying rules are bad and I believe heavily in the “Chesterton’s fence” concept but you also have to know when to break the rules instead of twisting yourself and your code into a pretzel to stay within the “letter of the rule”.

Within the past few years Apple released a new API to access photos. In the past a developer could ask for full access and you could give it full access OR you could select a few images to give it access to. In both cases the photos you give access to can be read from the app.

The new API allows the app to ask you for a photo without needing to first request permissions. The photo picker that pops up is NOT controlled by the app and it doesn’t have access to it. The app ONLY gets back the image you pick (if you pick one).

A lot of apps that want you to provide a photo only care about that 1 photo and have no desire to have full access to your photos so this new API is great addition and it avoids annoying permission dialogs. There are, of course, legit reasons to want full access but now users have finer grained controls on what they share with apps as full access can revel a LOT of private data about you.

I got mine on release day and I’m at 98% and I don’t ever take my battery or it’s life into consideration.

I almost exclusively charge via Qi or MagSafe, I leave it on the charger for long periods of time, and I alternate between saying between 90-100% all day and occasionally running it down to 10-20% 1-2 times a week.

Obviously I could be an outlier but finding a handful of people online claiming something is a terrible basis for an article like this.

People may complain about not having big changes in each year for the watch, but I think it’s important that Apple release certain products every year even if the changes are minor. Just look at the MacBook/iMac/Mac Pro lines and how much people want an upgrade (available at least) every year. It shows apples dedication to the line and it’s very important in my opinion.

People get work up about this but we’ve already crossed the rubicon once the bump was large enough that it couldn’t sit “flat”, even with a case. At this point I don’t care, take up the whole back of the phone if you want.

The bump annoyed me when it was first announced but I’ll choose better pictures over caring about the bump.

App Review and the unequal application of the rules is the worst part. Make all the rules that you want, but enforce them consistently and for everyone. I hate playing reviewer roulette.

You can save a web page as an icon (In Safari: click the share icon -> select “Add to Homescreen”)