Apple: Weekly Summary (December 08-14, 2025)

I would describe this week in Apple blogging as a mixed bag. There are legal punches, angry developers, people locked out of their lives, tiny design gripes that somehow matter a lot, and a few bright shiny promises for next year. To me, it feels like watching someone rearrange a well-loved kitchen while the oven is still on — bits get moved, some things break, and someone always yells because the spice rack is now on the wrong shelf. Read the original posts if you want the full drama. The authors link to their work below and deserve the clicks.

Legal pressure, antitrust and censorship — the big-shout headlines

This week had a clear thread about power. First off, Victor Wynne covered the ICEBlock app case. The app got pulled after pressure from the government. The developer is suing, saying Apple helped censor speech. That feels like a headline you could see on any evening news, but it lands differently when you think about the mechanics — app removal, government asks, and a company that usually sells itself as a neutral platform. I would describe the tension as heavy. It is the sort of thing that makes headlines and then sits for months in courtrooms.

Alongside that, Michael J. Tsai reminded us that Apple also has antitrust clouds over it in Europe. Dutch consumer groups are asking for a huge payout — 637 million euros. This is not the usual small fine. It is about how Apple charges developers and whether those fees end up harming users. It links back to the ICEBlock story in spirit. Both are about who gets to decide what is allowed inside Apple’s garden.

There was another, smaller policy tremor too. Michael J. Tsai wrote about iOS 26.2 adding limited support for alternative stores and voice assistants in Japan. Tiny, but important. Little footholds like this can be where bigger changes start. If you watch policy-wise, these bits are the breadcrumbs that lead to larger shifts.

I’d say this week felt a bit like seeing a town council meeting where everyone argues about who owns the public square. You know the square. Everyone uses it, but someone is trying to charge admission.

Developer struggles and the friction of distribution

If you make apps, you could be cheered or cut off this week. Michael J. Tsai shared two separate, very practical headaches: the Apple Developer Program rejection that stalled Igor Kulman, and a guide to dealing with WebKit bugs using internal rdar IDs that actually helps people get unblocked.

The Kulman story is the one that made the jaw drop a bit. You follow the steps, you fill the forms, you hand over information, and Apple says no. No explanation. That’s infuriating and oddly familiar. So he filed a GDPR request to get the reasoning. That feels like taking a very British snap of patience — you file paperwork and wait for bureaucracy to cough up an answer. But the deeper thing is this: the modern app economy still depends on a tiny number of gatekeepers. If you can’t get a yes, you don’t launch.

There were also several technical posts aimed at other builders. Bram.us explained how to find public WebKit bugs from internal Apple rdar IDs. It is a neat trick. It’s like finding the right lane in a confusing supermarket car park. Useful, specific, and the kind of practical help that saves hours.

Then there’s the nitty-gritty dev complaint about macOS screen savers. Michael J. Tsai pointed to problems in the screen saver framework and suggested ways to avoid falling into future traps. It’s an oddly niche topic. But it matters. When the framework behaves like a moody appliance, apps turn into frustrating experiences.

The App Store Awards got a once-over too. Michael J. Tsai didn’t just list winners. He questioned the picks, especially the iPhone app of the year. Tiimo is helpful for people with ADHD, sure, but its absence on the Mac felt like a missed opportunity. The awards felt curated and safe, rather than bold.

So there’s a pattern. On one side developers ask for clarity and fair rules. On the other, Apple’s systems are patchy: a little opaque, sometimes helpful, sometimes maddening. The result: people alternate between gratitude and grievance.

Accounts, gift cards, and the risk of putting all your eggs in one basket

This theme kept popping up in several posts and it made me squirm a bit. There were at least three pieces about people being locked out of long-lived Apple IDs after odd incidents with gift cards or fraud. The stories are raw. Twenty years of apps, photos, and work — gone or unreachable. That is not an exaggeration in the posts by Dr Paris Buttfield-Addison and Michael J. Tsai. Both told of permanent locks and a near-nonexistent support experience.

There were also two similar opinion posts titled An Apple Disaster You Can Avoid, from AppAddict and Amerpie by Lou Plummer. They push the same idea: diversify. Don’t store every key in one pocket. Use multiple accounts, diversify cloud services, keep copies offline. It reads like sensible house-keeping advice — like telling someone not to keep their passport, house keys, and wallet in the same back pocket when travelling.

I’d say these pieces glow with a mix of anger and practical fear. They are both a cautionary tale and a how-to guide. And the how-to is useful: move critical backups, use alternative email providers, keep developer accounts separate. That sort of redundancy is boring to set up. But it is gold when something goes wrong.

If you like analogies: it’s like relying on a single mechanic for every car you ever buy. One day he retires with your keys. You’re stuck.

Design, UX complaints and the slowly fraying polish

This was a big cluster too — design critiques and quality-of-life gripes. Nick Heer wrote a thoughtful piece about the departure of Alan Dye and how people are quick to pin design failures on one person. Nick argues it’s more systemic: culture, leadership, corporate dynamics. I’d describe that as a reminder that software design is like a group project where the boss gets the credit, and the mistakes get blamed on the one name that’s easiest to say.

There were several smaller, yet sharp, design complaints. Michael J. Tsai took on icons in menus, and the Phone app’s hidden tap-a-call setting. Both pieces asked the same simple question: are we making choices for users or for our own convenience? Icons in menus can be neat. But if they add cognitive load, they are noise. The tap-to-call setting is an example of a feature that feels hidden on purpose, like a sneaky door in a pub.

Passwords also got a look. Michael highlighted how Apple Passwords lacks visible history and syncing safeguards. The comparison with Dropbox keeping timestamped copies was telling. It’s a small thing, but when you lose a password change or a recovery token, small things explode into big headaches.

Then there was Pierre Dandumont’s test of the Magic Keyboard for iPad Pro. He liked the build and the backlight. He didn’t like the small trackpad and the weight. He’d rather use a MacBook Air for serious work. This is the recurring conversation about whether an iPad with a keyboard is a laptop or a fancy tablet. I’d say the keyboard is like a lovely but heavy briefcase — nice to have, but it changes the way you carry your day.

James O’Malley delivered a cheeky list of five petty tech gripes. It’s funny but pointed. Playback controls on iPhones, small UX annoyances, the kind of things that make you mutter while waiting for the bus. These small gripes matter because they are daily. They’re the pebble in the shoe.

The pattern here is clear: Apple’s design shine isn’t gone, but the lacquer is thinner. People notice tiny inconsistencies and they talk about them because they hit every day.

System updates: iOS, iPadOS, macOS tweaks and the little features that matter

There were several posts summarising the 26.2 updates across platforms, mostly by Michael J. Tsai. The updates are a mix of quality-of-life fixes and small new features.

macOS Tahoe 26.2 added Edge Light for video calls, alarms for Reminders, podcast tweaks, and some AirDrop changes. Some posts flagged worries about Local Network permissions. That’s a slowly growing theme: Apple’s privacy gatekeepers sometimes trip developers and users in equal measure.

iPadOS 26.2 made multitasking more flexible. You can drag apps from different sources into Split View and Slide Over with more grace. The description felt like Apple trying to stitch old gestures and new windowing ideas together without throwing away the faithful ones. To me, it reads as Apple trying to have your cake and eat it too — keep what people know, but add the power users’ cake.

iOS 26.2 introduced alarms for reminders, lock screen time opacity adjustments, Live Translation on AirPods in the EU, and the Japan-specific opening for alternative app stores and assistants. Some posts complained about Apple’s policy on downgrading iOS versions, which still annoys people who need older versions for stability.

These updates are incremental, but the sum is meaningful. Little UX fixes, better multitasking, a few privacy tweaks. It’s the kind of summer-mending that keeps your bike rollable for another season.

Market numbers, adoption and what might come next

The numbers came from Ofcom via Jonny Evans. Over half of UK smartphone users aged 16 and up are on iPhone. Younger users skew even more. Apple Music is widely used, WhatsApp still rules messaging, and Apple News grew notably. Apple even outsold Tesco online, which felt like a delicious little jab at the retail world.

These stats matter because they show where Apple’s platform power is real. When a company gets that big in a market, small changes ripple wide. If Apple nudges how payments work or what stores are allowed, it matters to millions.

Jonny also mapped a list of 12-plus big Apple announcements to expect in 2026. Folding iPhone, cheap iPhone 17e, M5 chips for MacBook Pro, smarter Siri, HomePad and more. Some of it reads like wishful thinking. Some of it looks probable. I’d say it’s the sort of wishlist you’d tell your mate down the pub and then argue about whether it’s realistic. The mix of hardware and services shows that Apple is trying to hold onto device mojo while growing its services and home ambitions.

Small but satisfying posts — tips, tricks and a few useful how-tos

Not everything was heavy this week. Bramus’ guide about finding public WebKit bugs via internal rdar IDs is one of those posts that instantly feels useful. It’s the kind of technical sleight-of-hand that makes debugging less painful. He even suggests a Chrome Site Search shortcut. I tried to imagine this like a key-finder for a crowded toolbox.

There were pieces about menu icons and small developer how-tos too. These are low on drama but high on utility. If you are building something or fixing something, these posts are the ones you actually bookmark.

Patterns, agreements, and where folks seem to argue

A few patterns kept repeating across the week:

• Friction with accounts and support. Multiple writers are burned by account lockouts and opaque support responses. That keeps cropping up and it annoys people in a way that money can’t easily fix. It is the kind of irritation that turns fans into critics.

• Design criticism is no longer polite niggle. People now point at systemic issues in Apple’s design approach. It is not just one lead designer’s fault, as Nick Heer put it. The critique is more about culture and product management than single names.

• Developer pain is real. From rejections to opaque frameworks and antitrust suits, the developer experience is strained. That is where policy, design, and practicality collide.

• Small features matter. Whether it is the way AirPods do Live Translation, a small password history feature, or a tweak to multitasking, tiny improvements make a large difference in day-to-day use.

People agree Apple is still important. They disagree on how well Apple is handling growth and complexity. Some think Apple must open up more. Others warn that opening too much could ruin the experience. That argument shows up everywhere: law, design, and developer life.

A few human moments worth reading for themselves

If you only read two pieces from this week, I’d nudge you towards the account lockout stories and the ICEBlock lawsuit coverage. The account lockout posts by Dr Paris Buttfield-Addison and Michael J. Tsai are painful in a very human way. People lost access to years of stuff because of a gift card or fraud detection. That is the kind of story that makes you think twice about where you keep your keys.

And Victor Wynne covering ICEBlock points to broader questions about censorship, compliance, and the role Apple plays when governments ask for takedowns. Read that and you’ll have a better sense of why the App Store is not just a marketplace but also a place where politics shows up.

There are useful tech side trips too. Bram.us on WebKit bugs and Michael on screen saver quirks are the kinds of posts that fix real developer headaches. They are practical and honest.

Final thought, meandering a little

There is a common thread through most of these posts: the Apple ecosystem is both a cozy home and a house with a few drafty windows. People like living there. They also notice when something smells smoky in the kitchen. Some stories are about big fights — courts, antitrust. Some are small, quietly angry notes about icons and password histories. Both matter because they show how people are using these devices every day.

If you want the dirty details, the filings, the workarounds and the ranty parts, follow the authors. They did the digging and the writing. For devs, check the technical how-tos. For users, read the account stories and the advice about diversifying. For the curious, the legal posts are a slow-moving train wreck you may want to watch, like waiting for a storm to pass.

There you go. If any one thread here grabbed you — account safety, design, or the laws — dive into the linked pieces. They are worth the read, and they’ll give you the full colour.