Summarised β This Year's iPhone Changes
While working on a different blog post, I made a list of changes to the different iPhone models. Instead of just scrapping it, I thought I’d post it here.
Improvements across the line(s)
- Camera Control button added
- Support for Dolby Vision video
- Latest generation Photographic Styles
- Anti-reflective lens coating
- Improved glass
- Faster MagSafe charging
- Lower minimum brightness
- A bit longer battery life
iPhone 15 Pro β 16 Pro
- Larger screen size, from 6.1" to 6.3" / /6.7" to 6.9" (A negative in my book, but not in most’s, I assume.)
- Upgraded chip, from A17 Pro to 18 Pro (Doesn’t seem like the largest bump.)
- Improved thermals
- New ultra-wide camera (Seems substantial!)
- The non-Max also gets last year’s 5x tele lens
- Improved microphones
iPhone 15 β Iphone 16
- Upgraded chip, from A16 to A18 (All-new architecture βΒ more substantial upgrade.)
- More RAM, from 6 GB to 8 GB.
- Support for Apple Intelligence (Due to the last two things mentioned.)
- Added Action button
- New ultra-wide camera (With support for Macro photography β but not as large an upgrade as on the Pro.)
- Support for spatial video
- Thread radio
- 1 whole gram lower weight (π€)
Anything I missed? Feel free to let me know!
My recommendation is that it seems like the iPhone 16 (regular model) is the best buy at the moment. And that the β¬100 higher price compared to buying last year’s iPhone 15 is well worth it. (Where a used 15 Pro fits in the calculation, is a more complicated question!)
I Love My Little Charging Bundle
I recently wrote about not needing USB-A, and mentioned the USB-C Lifestyleβ’οΈ. That reminded me of a little bundle of cables I always keep in my backpack. So here are some β¦
Advice for frustration-free charging
1) Buy extra
Here’s my bundle:
The trick is that I don’t need any of these elsewhere β they are extra. I have other chargers in my office, next to my bed, etc. I get that this is a bit more wasteful than just having one charger that you move around everywhere. But I think this is resource spending that’s worth it β and hopefully the devices you buy don’t come with (sub-par) chargers you don’t need. Furthermore, try to keep chargers for a long time.
2) Think about colour and texture of the cables
These are the cables in the bundle:
- USB-C, 3 meters (black, braided)
- MagSafe for Mac (light gray, braided)
- Lightning, 1 meter (white)
- Micro-USB (black)
As you can see, all of them have a different combination of colour and texture. This makes it easier to pick out the correct one!
3) Don’t buy “original” chargers
In general, buying “original” accessories will give you something that might be pricier, but at least is among the best. But when it comes to chargers, and especially compared to Apple, the third-party chargers are objectively better. The reason being that Apple doesn’t use GaN, a relatively new technology that allows for significantly smaller size to power ratio.
Mine’s a 65 watt Anker charger ποΈ, that I really like. Because while I don’t necessarily recommend getting chargers from Apple/Samsung/etc., I do recommend getting a “name-brand” one. Anker is a brand I’ve always been pleased with, so I haven’t tried many others. But I think Ugreen and Belkin might be decent as well. Would love to hear about it if you have other recommendations I can add here!
4) Get enough wattage, but not more
No, You Donβt Need USB-A on Your Desktop Computer
The first redesign in a decade for the Mac Mini is near. And the rumours point towards Apple removing the USB-A ports on the current models, in favour of USB-C ports. And to the surprise of no one, people are moaning about losing their precious ports, as if they were buying a laptop in 2016.
But, just like Freedom β¦
USB-A isn’t free
First, let me be clear: I’m not discussing the number of USB ports β I’m discussing the types. So, for instance, I’m evaluating 5 USB-C ports vs 3 USB-C ports and 2 USB-A ports.1 So “just keep the USB-A ports” wouldn’t come for free, it would come at a cost of more of the future-proof2 port type.
Another “cost”, is that the longer computer makers ship products with the port, the less pressure Logitech et al. feels to update their peripherals to USB-C.
I know this might sound a bit harsh, my clear advice is β¦
Get over it
“But I don’t want dongles”, I hear you say. Well, I think there are satisfactory ways to adopt the USB-C Lifestyle without becoming a permanent resident of Dongle Town β which doesn’t include buying numerous new devices.3 Yes, I know this comes at the cost of maybe β¬10-30 (depending on your setup) β but just factor it into the cost of the β¬500-1000 computer, and it will be fine. And your life will be better for it!
Here are my two main tips, as someone who’s deep into the lifestyle.
1) Buy some new cables
I have an older Satechi presenter, which charges with Micro-USB (boo) and came with a USB-A to Micro-USB cable.
However, I’ve bought this cursed contraption:
I don’t love having to lug around that stupid cable4 β but it sure works to pull an older device into the USB-C age. All my power bricks ποΈ are USB-C, so I can charge it directly there. It can also charge from my tablet, laptop or the theoretical USB-A-less Mac Mini.
I’ve most often used it with an iPad Pro (with a Magic Keyboard) β and an advantage of bringing things into USB-C, is that it also makes things work better with more “port constrained” devices, like the iPad. So I would, for instance, run things like this:
- USB-C Power brick (in the wall)
- USB-C to USB-C cable
- iPad Pro’s Magic Keyboard (which charges the iPad)
- USB-C to Micro-USB cable (in the iPad itself)
- Satechi remote
That cable would (probably?) also allow the remote to be charged from a newer iPhone!
So, my first recommendation is to see if any of your “USB-A devices” could become “USB-C devices” by just buying a new cable.
2) Buy some adapters
The Beauty of Third-Party Services
and Open Protocols and Standards
I’m very much what you’d might call a software snob. Not only do I care about unnecessary things like how an app looks β I also care about how it feels. I’d also say that apps are an interest/hobby of mine, and I love testing new things. So I love open and portable stuff, so that I’m always able to use the software I prefer. Allow me to explain, with four examples: RSS, Email, Browsers, and Markdown.
RSS
My current RSS reader of choice, is Lire. It doesn’t look and feel quite as nice as Reeder and Unread, but it is still good in this regard. However, I love that I can customise the look, that it caches truncated RSS feeds, and that I can (on a feed-by-feed basis) load an inline web browser. This makes it possible to read blogs with their original design, which I think is neat.
However, my feeds don’t live in one client. They’re synced with Feedbin. This makes it trivial to move between clients, and I can even use several in parallell, as things like sorting and read status instantly sync between them. Maybe I prefer Lire on mobile and Unread on Mac, for instance?
Portability is an important principle here. And if I want to move from Feedbin to Inoreader, for instance, I can easily export my feed subscriptions as an OPML file, which I can then import into Inoreader.
So I’m not locked in anywhere, and I can use the client I prefer everywhere. This reality is what I wish I could have for music streaming as well, as I’ve touched on here. It also shows why I want less bundling and integration.
Notes on cross-platform-ness
My best friend, and fellow nerd, has always been adamant in using cross-platform tools β the reason being that he can be flexible in terms of which hardware he uses. He can easily switch between Windows, Mac, iPhone, Android, etc. However, this doesn't gel well with my software snobbery, as most of the best apps (in my opinion) simply aren't cross-platform. I have the same issue with web apps β I love their flexibility and portability, but I don't love using them. So the approach laid out in this post, is my approach to the same idea. But yes, it would be even more robust if I only used web based and cross-platform tools.Now, as opposed to with RSS, there’s not many good email clientsβ¦ But the same principles apply!
I host my email with Fastmail ποΈ, and I’m very pleased with it.1 But if I still want to switch later, I don’t use an @fastmail.com address. Instead, I use my own domain, hosted on Hover ποΈ β so I don’t have to change address if I change hosting. I can also change where I have my domain without having to change anything regarding my email.
Now, I don’t like the default Fastmail client β but email being email, I can use a client I dislike less instead!
Browser
Please Stop Saying "Telegram Isn't Encrypted"
You’re not helping - draft 2
Telegram is back in focus these days β and, as usual, not for good reasons. I will write more on this later, as I will have to figure out how to deal with the very real concerns I have with the chat app I use the most. But now I wanted to focus on one thing that’s annoying me a lot, for instance in the latest Vergecast episode.
Why it’s a bad idea to say things that aren’t true
I think it’s crucial to get the word out, that Telegram isn’t as safe as Signal1 β and I applaud those who want to shine a light on that fact. The problem is, that many of them (like Nilay Patel) do it by saying that “Telegram isn’t encrypted”. But what happens if someone has heard that phrase, and then later learns the fact: That Telegram is encrypted.2 They will then perhaps disregard the entire notion, and maybe assume that Telegram is as secure as Signal after all.
My issue with that phrase is that it erases the essential distinction between just “encryption” (or “server encryption”) and “end-to-end-encryption”.
Here’s the difference:
A Good Conversation About Apple and APIs
When comments helps you grow
A couple of days ago, I hastily wrote a quite spicy blog post, about the removal of a good Spotify feature on iPhone. I got some pushback from Jason, and it led to a conversation I liked.
Me and Jason often disagree on stuff β but I always find his comments fair, interesting, and leading to me adjusting my opinions. One important takeaway in this for me, was whether or not this was just a case of someone whining, and putting a spin on, an API getting deprecated. Which is something that sometimes has to happen, but will still often lead to complaints which I often disagree with.
His first comment
I mean, it also could be there was an old way of accessing volume controls, Apple built a new way to work with HomePods, AppleTV, and likely Matter devices. They then deprecated the old API in favor of the new one to maintain one pathway, that yes, means access to its products comes along, but also means one, more modern, more standards compliant API to control devices.
I don’t trust Spotify comms for shit, and don’t know that’s what Apple did, but that story is equally like Apple– get rid of an old API for a new one that does more stuff, misses some functions but adds a lot more, etc. It would also line up with Matter and the addition of these devices that didn’t exist when the original implementation was done.
And for what it’s worth, the bugs that Spotify mention are present with the volume rocker over AirPlay. So, I’m not sure it’s not just Apple’s shit not being as good as it should be, period, versus disadvantaging someone.
My first reply:
The thing is, you can point to a million small examples where Apple makes (decently rational) choices that just so happens benefit themselves at the expense of others. Many of them are of the type “We made this choice, because privacy. That it hampers our competitors, is just a coincidence. So is the fact that we didn’t do this other thing which also would’ve been good for user-privacy, but would hurt us.” If you only look at each thing individually, Apple’s behaviour can often be defended β but you have to look at the larger patterns. Hehe, I agree that it’s a good idea to be skeptical of comms β but I don’t trust “Spotify + Sonos combined” less than Apple, I think. And Apple could’ve decided to comment, but has chosen not to.
And for what it’s worth, the bugs that Spotify mention are present with the volume rocker over AirPlay. So, I’m not sure it’s not just Apple’s shit not being as good as it should be, period, versus disadvantaging someone.
This is a good point! ππ» But I still stand by my stance that these things would be better if the behemoths didn’t insist on competing in more and more markets. (I wrote more about this here.) We would have much cleaner incentive structures, if Apple’s “only” focus was on making their platforms (and hardware) as good as they could make them. (And “competition” would be an important ingredient here.)