Normal view

There are new articles available, click to refresh the page.
Yesterday — 16 October 2025Main stream

韩国 Air 购买 AC 求助

By: mrlmh00
16 October 2025 at 19:05
mrlmh00:

国内 apple store 说今年政策改了不能跨区买 apple care,别人港版 17pro 也没买成功。 手机上直接出不来购买选项,手机设置韩国地区+更换韩国 id 也出不来购买选项 官网显示韩国是 60 天内都可以买,还有什么路子吗

目前新系统的几个 bug 你们有么

16 October 2025 at 15:59
wearzkjefa: 手机 iPhone16 ,电脑 m3 MacBook air ,都是最新系统,发现了几个 bug 很烦人。
1 、未接来电显示红色,以前点一下就消除红色通知,现在怎么点那个未接来电,电话图标的未接提醒 1 持续存在,强迫症难忍。
2 、库乐队 mac 输出的时候如果音乐名字切换大小写会直接卡死。
3 、王者荣耀打着,如果是来消息提醒或者是切出去看信息,或者是拨开提醒通知,都有几率触发变很卡,走路卡顿卡顿的。除非强制关闭后再重新打开。

记得好像还有很多 bug ,想到再来补充,大家有发现什么 bug 的也欢迎补充。

咨询一下买过港版 MBP 在大陆用的朋友,使用体验

By: Rickyyyy
16 October 2025 at 14:07
Rickyyyy:

想入最新 MBP ,纠结选择国行还是港版,国行阉割了 AI ,但是听说港版虽然有 AI ,但是回大陆使用,挂梯子使用 AI ,十分的不稳定,不如直接下个 GPT 客户端。想问问有没有买了港版 MBP 在大陆用的朋友,最真实的使用体验。

M5 Macbook 要来了,是等明年新模具还是直接冲?

By: marklu
16 October 2025 at 12:10
marklu: 题主是搞数据科学的,今年申博成功,手里还是本科时候买的 16g M1pro 的 macbook pro
进组之后做了好几个大项目,16g 内存确实吃紧跑不动
看到 M5 芯片大升级,但是一直犹豫今年买了,明年换新模具会不会亏……
或者其实等等党永远不亏

Apple has released an update to XProtect for all macOS

By: hoakley
16 October 2025 at 04:18

Apple has just released its weekly update to XProtect, bringing it to version 5319. As usual, it doesn’t release information about what security issues this update might add or change.

This version adds three new Yara rules. MACOS.SOMA.OCENA is yet another for the vast Soma/Amos family, and there are two for the far newer MACOS.ODYSSEY group, MACOS.ODYSSEY.SOCGO and MACOS.ODYSSEY.SEENA.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5319

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5319 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Before yesterdayMain stream

天塌了,美区 Apple ID 绑定美区 paypal 会验证信用卡

By: MoGeJiEr
15 October 2025 at 20:01
MoGeJiEr:

之前用了好几年的美区 paypal 被封了,所以重新注册了一个美区 paypal ,并且绑定了国内的建设 visa 卡,并捐款了乌克兰 1 美元;紧接着去绑定美区 apple id 发现会验证 paypal 绑定的信用卡,天塌了,也不知道什么时候变的?看下图:

IMG_3305.png

这份目前最全的 eSIM 开卡攻略,请国行 iPhone Air 用户收好

By: 马扶摇
15 October 2025 at 09:18

正当我们以为 iPhone Air 会在十月的新机潮里慢慢销声匿迹、直到被人遗忘的时候,它突然水灵灵地就这样来了。

爱范儿昨晚(10 月 13 日)获悉,国行 iPhone Air 将于本周五(10 月 17 号)起接受预定,并于下周三(10 月 22 号)正式发售。昨晚,苹果 CEO 蒂姆·库克也在 Apple Store 抖音直播间中正式宣布了这个消息:

至此,iPhone Air 成为了国内市场第一款正式发售的纯 eSIM 手机。后续伴随着其他国产品牌的跟进以及运营商的支持,iPhone Air 也算是拉开了 eSIM 技术在国内落地的序幕。

只不过相比 iPhone Air 的硬件本身,大家更关心的其实还是从实体卡转换到 eSIM 的各种技术细节——不仅仅是爱范儿评论区的读者们,也包括编辑部里面几位摩拳擦掌等着换 Air 的编辑。

因此,在国行 iPhone Air 正式开售之前,我们和三大运营商参与 iPhone Air 发售/eSIM 业务的相关工作人员进行了沟通,提出了大量的问题并试图找到更加明晰的答案。我们整理了三大运营商目前已知的 eSIM 政策,争取解答用户最关心的问题。

(本文描述的情况和资料,截至 2025 年 10 月 14 日周二晚间。不排除在 iPhone Air 正式开售之前和之后,国行 eSIM 业务政策仍会发生一定程度的调整,届时我们将对本文做出更新。)

1. 买到国行 Air 之后,应该怎么去办卡?

目前,三大主流运营商(联通、移动、电信)均宣布了对于 eSIM 业务的支持。无论你是开通一个新的纯 eSIM 号码,还是把现有的实体 SIM 卡转成 eSIM,都离不开亲自跑一趟营业厅的操作。

换句话说——无论你现在使用的是哪家的号码,在 iPhone Air 到手之后,都需要由你本人携带自己的身份证件,前往你所在地区的指定营业厅,由工作人员亲自帮你给手机写入 eSIM——

这也是目前三大运营商都在采用的「人证机合一」政策

图|新华网

在证件支持方面,中国联通支持的范围无疑是最广泛的。对于大陆居民支持身份证、户口簿和护照,对于港澳台同胞以及在华外国人,则支持港澳台通行证或居住证,以及外国人永久居留身份证

而移动和电信支持的证件类型就相对少一些,仅支持使用身份证(大陆居民)外国人永久居留身份证,港澳台同胞则只能使用居住证办卡,不支持通行证。

台湾居民居住证样例

此外,需要注意的是,如果你入手国行 iPhone Air 计划新开一个号码,也仍然要遵守此前六部委联合发布的「一证五户」和「一证十号」的规定,即:

  • 同一用户在单个运营商处办理的有效电话卡不得超过 5 张
  • 同一用户在所有运营商处合计持有的有效电话卡不得超过 10 张

2. 我手里正在用的号码可以转成 eSIM 吗?

可以。根据目前三大运营商公布的办理流程,三家都支持直接在现场办理实体卡转 eSIM 的操作,所需的证件和流程都和新开 eSIM 号码相同。

另外根据爱范儿向运营商内部知情人士咨询,实体卡转换 eSIM 之后,原本的实体卡就会直接失效,这一点与国际主流 eSIM 服务的策略是相同的。

然而针对挂靠在原本实体号卡上的增值服务——比如给 Apple Watch 使用的一号双终端业务——运营商知情人士表示仍在等待具体的通知文件,大概率是可以沿用的。

3. 国行 iPhone Air 到底能添加几张 eSIM?

根据目前的已知信息,我们可以明确的是:

国行 iPhone Air 在国内使用的时候,最多只能保存和同时启用两张 eSIM 卡。

这是个坏消息,毕竟外行 Air 机型支持最多存储 8张。

但也有好消息:国行 Air 存储的 2 张 eSIM,并不限制同一运营商。

也就是说,用户无论在任何渠道购买的都是全网通机型 A3518,只要还有一张卡的空位,就可以放入另一家运营商的 eSIM 卡。即便是合约机,也是全网通。

此外,国行 iPhone Air 的双卡依然仅支持双卡双待(DSDS)、不支持双卡双通(DSDA,两张卡可以同时接打电话),与 iPhone 17 系列其他机型保持一致。

大家最关注的点,可能就是国行 Air 能否、如何添加外卡。

很可惜的是,针对这个问题,三大运营商都还没有给出具体的政策,以下是爱范儿根据苹果官网和运营商内部人士信息,所整理出的结论:

  • 在国行 iPhone Air 上,存在一个地理围栏机制,当你身处国内,禁止添加国际运营商的 eSIM 卡。
  • 当你物理出国之后,国行 iPhone Air 就可以添加国际运营商发行的 eSIM 卡了,在使用方式和功能限制上,和以往「出国买张当地流量卡」一模一样。

至于一台国行 Air,在 2 张大陆 eSIM 的封顶之外,究竟能保存多少张(境外)eSIM 卡,截至本文完稿时,爱范儿仍然没能从三大运营商处获得明确的答复。

但根据爱范儿的技术推测,国行 iPhone Air 应该是「最多只能添加两张国内运营商的卡」,出国之后可以额外添加 6 张国际运营商的卡,即 eSIM 支持的总数为 8 张,与国际版 iPhone 持平,且不需要删除国内卡。

至于在国外时添加的国际运营商 eSIM 卡,回国后能否继续使用,运营商也未作出明确答复。从技术角度分析,爱范儿认为依然是支持的(前提是你的外国 eSIM 卡支持国际漫游),与蜂窝版 iPad 的策略类似。

4. 没忍住已经买了外版 iPhone,还能添加国内的 eSIM 吗?

非常可惜,从目前已知的信息来看,这个问题的答案是否定的。

根本原因在于,国行 iPhone Air 会在生产时预装一个专门的信任证书。手机上必须有这个信任证书,才能够正常部署和激活三大运营商的 eSIM 卡。

而外行机型不会预装这个证书,技术层面自然无法安装国内运营商的卡了。所以,外行机型要么用外卡,要么就当个 iPod Touch 用吧。

图|哔哩哔哩 @微机分WekiHome

这样就延伸出了一个新问题:外行机型不支持三大运营商可以理解,但是港澳台版 iPhone 怎么办呢?并且不仅是 iPhone Air,今年的港澳台版 iPhone 17 系列三款机型也都是支持 eSIM 的,只是没有信任证书。

对于这种情况,爱范儿未能从三大运营商处获得具体的回答。只能希望后续政策能够及时补全,避免将来国内的 eSIM 服务铺开、来访的港澳台同胞出现「能办理 eSIM,自己的手机却用不了」的窘况。

5. 换成 eSIM 之后还有什么奇奇怪怪的限制吗?

首先,也是最重要的,就是目前国内三大运营商对于 eSIM 的开通和补换次数是有限制的。

最大的限制,就是每个自然月,每台 eSIM 手机新开通号码不能超过 2 个;补换重新录卡的次数不能超过 5 次,等等。

这个情况,用爱范儿自己举个例子,就是我们一个月里最多只能有两个同事可以换着用 iPhone Air 国行评测机。

另外,使用三大运营商的 eSIM 之后,你的换卡流程也会变得繁琐许多。

根据目前的政策文件,如果你不巧摔坏了手里的 iPhone Air、需要把上面的 eSIM 卡转移到临时的备用机上,等修好之后再转回 iPhone Air 里面,可能需要跑至少两次营业厅线下办理,并且会消耗你当月的 2 次补换卡次数

并且换用 eSIM 之后,你在未来换新手机迁移的时候也会变得麻烦一些。虽然 iPhone 换机支持直接迁移 eSIM 卡,但是运营商对此会有额外的规定,比如有些国际运营商就规定了 eSIM 卡更换手机要收费,或者重新实名认证等等。

而对于三大运营商来说,根据目前已知的政策信息,在未来你从 iPhone Air 升级到别的 eSIM 手机,都需要去营业厅线下办理换卡流程,然后才能在新手机上激活 eSIM

这很倒退,我们不喜欢。但很遗憾,至少在目前三大运营商的政策下,只能如此。

另外,如果你对国行 iPhone Air 进行系统重置,手机还会提示你选择「抹掉 SIM 卡并重置手机」还是「保留 SIM 卡并重置手机」:

从技术层面,选择保留 eSIM 卡并重置之后手机的 SIM 卡状态是不会改变的,不需要重新激活。但是尚不确定目前国内运营商对于「重置手机」这种操作是否会存在限制——爱范儿合理猜测,这种情况不需要跑营业厅。

至于销号退网这种操作,从目前三大运营商公布的政策来看,国行 iPhone Air 是与国际版保持一致的:在手机上删除 eSIM 卡 ≠ 注销套餐和号码

换句话说,如果你不想用这个 eSIM 号码了,还是需要和从前办理实体 SIM 卡销号一样,前往具有处理 eSIM 业务资质的营业厅进行线下办理。

iPhone Air 值得买吗

无论 eSIM 与否,iPhone Air 就在哪里。在今年加量不加价的 iPhone 17 标准版的衬托下,iPhone Air 的性价比很难让人提起兴趣。

然而无论是平时对科技数码不感兴趣的朋友,还是爱范儿编辑部的同事们,在摸到 iPhone Air 真机的那一刻,原本对于参数的顾虑似乎都原地消散了。

对于一台 256GB 起售价 7999 人民币的旗舰机,iPhone Air 的确不是很大众的选项。事实上,搭配目前 eSIM 业务的种种限制,只会让 iPhone Air 的处境更加尴尬。

不可否认的是,iPhone Air 就是敲开国内 eSIM 业务的那块砖,虽然缺陷很多,但意义非同凡响。如果你不那么在乎参数,只想要苹果最新、最好、最有设计感的那一面——那 iPhone Air 还真是一个情绪价值拉满的选项。

#欢迎关注爱范儿官方微信公众号:爱范儿(微信号:ifanr),更多精彩内容第一时间为您奉上。

爱范儿 | 原文链接 · 查看评论 · 新浪微博


Apple has released an update to XProtect for all macOS

By: hoakley
9 October 2025 at 03:34

Apple has released its weekly update to XProtect, bringing it to version 5318. As usual, it doesn’t release information about what security issues this update might add or change.

This version makes several changes to the Yara definition for MACOS.COMPLIANTPIRATE.DEFU, but doesn’t add any new detection rules.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5318

Sequoia and Tahoe systems only

This update has now been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5318 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update
However, if the regular update has been installed in the old location, XProtect is likely to update its new location from that. There’s nothing you can do to force that, but it may well explain why your Mac seems to have updated itself.

Updated 0450GMT 9 October 2025.

闲鱼上的美区 apple one 超大杯为什么这么便宜?

7 October 2025 at 12:11
xiangsanliu: 有人知道为啥闲鱼上美区的 Apple one premier 拼车这么便宜吗?是用了啥活动还是纯盗刷?

太离谱了,官网$37.95/mo 。闲鱼季卡¥45 ,年付¥180 ,比马来西亚区官方价格还便宜(关键人家还全好评),如果是正规渠道,那我自己开啥车,直接上别人车得了。

2025 年底了, iPhone 还不支持 VOLTE 视频通话功能吗

By: doctorzry
4 October 2025 at 19:05
doctorzry:

如题,楼主已入 ipad 和 MacBook ,但手机之前都是安卓用户,年底打算换 iphone 17 ,查了下网上的坑点:例如没有侧边返回、没有 NFC 、没有红外、安装小众软件麻烦等,感觉有影响但不多 但是今天尝试给一个用 iphone 的亲戚打视频给打麻了,总是提示用户手机不支持,自动跳转到语音通话,后面一查,最新的结果在 2024 年,说 iphone 为了推自家的 facetime ,拒绝接入国内运营商的 VOLTE 视频通话。朋友们现在支持的情况是怎样的呢?有无改进,or 还是原样? PS:我打视频一直都是用 VOLTE 视频,发热低,也不吃流量,微信那个视频太烂太菜了

有没有觉得 iOS 现在删除 App 好繁琐

By: Scare
3 October 2025 at 20:05
Scare:

现在想在桌面上删除个 App ,至少要点击四次,才能删除一个 App 。
iOS 上第一次长按弹出菜单,第二步点击“移除 App”,第三步点击“删除 App”,第四步点击“删除”,才成功删除掉。
iPadOS 上第一次长按弹出菜单,第二步点击“选项”,第三步点击“移除 App”,第四步点击“删除 App”,第五步点击“删除”,才最终删除。

最近有 v 友成功在苹果官网买礼品卡成功了吗?求指导

By: srlp
3 October 2025 at 23:40
srlp:

今天因为想订阅美区 icloud+ ,因此想给美区的 id 充值一下。

几年前在 https://www.apple.com/shop/gift-cards 用招行卡购买成功,因此这次再次想试一下。

结果以下组合都失败了:

  • apple pay + 海外(非大陆非美国)信用卡 (账单地址是大陆的)
  • 直接输入海外(非大陆非美国)信用卡(账单地址是大陆的)
  • 直接输入招行 master 卡(账单地址是大陆的,+信息之类的都是英文填写)
  • 直接输入招行人民币银联卡(账单地址是大陆的,+信息之类的都是英文填写)

。。。

都失败了,我是大无语了。

我想到几个原因:

  1. 可能是 ip 问题?
  2. 我写的送礼人和收礼人都是 apple id email ,难道同一个 id 不可以?

最后都失败了之后,去 pockyt (支付宝那个渠道)购买了。。但是应该还是苹果官网比较稳,有 v 友最近购买成功了的吗?具体是什么组合购买成功的?卡、账单地址、送礼人收礼人都是怎么排列组合的?

除了官网,还有什么靠谱渠道? pockyt shop 靠谱吗?美亚可以用国内信用卡吗?

谢谢各位!

[内购限免] Affinity for iPad 内购限免(3 件套)

2 October 2025 at 11:03
Daniel0829: [内购限免] Affinity 一套专业级的创意软件套件,包括 Affinity Designer (矢量图形和插画设计)、Affinity Photo (照片编辑和修饰)和 Affinity Publisher (专业页面布局和排版)。

目前三件套 for iPad 都在内购限免中!

使用方法:注册/登录账户(已有账号的,登录账号;没有账号的,点击注册新账号),进去后先点 7 天试用,然后进账户购买 0 内购,再点注册绑定 Affinity 账户。亲测有效!!!



来源于 tg 群组

Apple has released an update to XProtect for all macOS

By: hoakley
2 October 2025 at 01:09

Apple has released its weekly update to XProtect, bringing it to version 5317. As usual, it doesn’t release information about what security issues this update might add or change.

This version adds five new detection signatures to its Yara file. These include another newcomer with four signatures, MACOS.DAILYDUMPLING, and MACOS.SOMA.SEEND to add to the large Amos/Soma family.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5317

I apologise for the late announcement of this update, which seems to have been released after 22:00 GMT on 30 September, but was still incomplete here through the whole of today, 1 October.

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5317 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Apple has just released macOS 26.0.1 Tahoe, 15.7.1 and 14.8.1

By: hoakley
30 September 2025 at 02:12

Apple has just released macOS 26.0.1 Tahoe, which fixes the problem upgrading to 26.0 on Mac Studio M3 Ultra models, and apparently fixes other urgent bugs.

For Apple silicon, the update is a 1.76 GB download.

Tahoe 26.0.1 fixes a single vulnerability, although Apple doesn’t report that it’s already being exploited. The same is also fixed in Sequoia 15.7.1, and in Sonoma 14.8.1.

macOS 26.0.1 has build number of 25A362, Safari version 26.0.1 (21622.1.22.11.15), and a Darwin Kernel version of 25.0.0. There has been no change in iBoot firmware, which remains at 13822.1.2.

As Apple hasn’t been forthcoming about what else has changed, here’s my list:

  • Passwords app has gone from version 2.0 to 2.0.1, suggesting it has at least one significant bug fixed.
  • AppKit framework has had an increment in build number, also suggesting bug fixes.
  • CoreText framework likewise, with bug fixes for a higher build number, possibly related to the fixed vulnerability in font handling.
  • Security framework has a substantial increase in build number, implying bug fixes there as well.

Otherwise, remarkably little has changed.

Updated 1910 29 September 2025.

A brief history of content caching services

By: hoakley
27 September 2025 at 15:00

One of the many fine details in macOS is its built-in support for a content caching service, both as server and client. This can be used for local distribution of macOS and other system updates, App Store updates, Apple media content such as Music and movie purchases, and iCloud content.

This appears to have originated as one of the new services added to Mac OS X Server 10.4 Tiger in April 2005, initially confined to a Software Update server. Apple’s online services were growing rapidly at the time, with the iTunes Store opening in 2003, and the first of its App Stores for iOS launching in 2008. Those were followed by the iCloud service in 2011. To cater for those, Apple added a separate Content Caching server by OS X Server 2 in 2012.

This shows the Software Update service in OS X Server 2 in 2012, with a list of some of the updates it had in its cache at the time.

At that time, a client Mac’s Software Update pane in System Preferences had to be pointed at the local server for that to be used instead of Apple’s. However, that didn’t work with App Store caching, for which the /Library/Preferences/com.apple.SoftwareUpdate.plist file had to be edited manually on each client to add a new property specifying the IP address of the local server.

macOS Server 5 in 2015 extended this further.

softwareupdserver

Features of the Software Update server then included the ability to limit the server’s bandwidth in its link back to Apple’s servers, and to control local network bandwidth used to transfer updates from the server to clients.

Amazingly, its original documentation is still available online here, and instructions for setting up clients remain here.

cachingserver

The Caching service worked with all content and apps provided by the Mac App and iTunes Stores, which of course included OS X updates, and is explained here. By this time, Macs and iOS devices connected to the local network would automatically find a server when it was running; there was minimal configuration for the server, and none for the clients.

When macOS 10.13 High Sierra was released in 2017, that brought update and content caching services to client Macs, and no longer required macOS Server, which was already in its terminal decline. These were configured in a new Content Caching feature added to the Sharing pane in System Preferences.

In essence, you designated one or more Macs as ‘parents’, to serve their cached content to ‘children’, which can themselves host caching services, to allow tiered setups. Initially, parents also needed to share their internet connection, required a minimum of iOS 10.3 for iOS devices, required a wired Ethernet connection to your router, and couldn’t sleep, so had to be run on mains power.

Although the content caching service has become quite widely used since, it’s never been as popular as it deserves. It remains remarkably simple to set up, as seen in these screenshots from 2020.

contentcaching01

Clicking on the Options button let you set the cache location and its size.

contentcaching02

Tabs were made available if you held the Option key before clicking the Options button, which then became Advanced Options. That let you set up clients, as well as other servers functioning as peers or parents, on more extensive networks.

contentcaching03

These remain essentially the same today in Tahoe.

When Apple changed macOS updates in Big Sur, life became more complicated. When updating Apple silicon Macs, the first GB of macOS updates had to be downloaded direct from Apple’s servers, and it was only after that the remainder of the update could be obtained from a local caching server.

Apple has further extended the types of content that can be cached locally, to include

  • macOS updates normally obtained through Software Update or the command tool softwareupdate;
  • internet Recovery images from macOS 10.13.5 onwards when obtained in Recovery mode;
  • apps and their updates supplied through the Mac and iOS App Stores;
  • GarageBand downloadable content;
  • iCloud documents and data, including Photos libraries;
  • Apple Books;
  • downloadable components for Xcode.

Most recently Rosetta 2, screen savers, wallpaper and AI models have been added to the list. Apple’s reference document is here.

Advanced server configurations are catered for by the command tool AssetCacheManagerUtil which can also provide performance information, and there are two additional tools available, AssetCacheLocatorUtil and AssetCacheTetheratorUtil. On the server, performance information is most readily accessed in Activity Monitor’s Cache view, which provides summary statistics for the local cache.

cachingserver1

This includes the total size of data served for the last hour, 24 hours, 7 days, and 30 days. To view those graphically, the time period for the charts at the foot can be changed by using it as a popup menu.

cachingserver2

cachingserver3

These show what happened on my content caching server during the macOS 11.4 update in 2021, for which almost 30 GB still had to be downloaded from Apple’s servers, while just over 20 GB was served from its cache.

Over the last 20 years or so, Software Update and Content Caching services have been remarkably reliable, but in June 2022 there was a period during which updates to XProtect and XProtect Remediator failed to install correctly when attempted through a content caching server. Apple never explained what the cause of that was, but it was eventually fixed and hasn’t recurred since.

Then, out of the blue, iOS and iPadOS 26 introduced a new feature to identify and test a connected caching server.

To access this, in Settings > Wi-Fi tap the ⓘ button on your current active network, scroll to the bottom and tap Content Caches. Tap the active cache to see full details, together with a download test. Don’t bother looking for an equivalent feature in macOS 26 Tahoe, though, as it isn’t available yet. How odd.

When will macOS be updated in 2025-26?

By: hoakley
24 September 2025 at 14:30

No sooner have we recovered from upgrading and updating macOS to 26.0/15.7/14.8 than Apple has released the next round of betas. This article looks at what’s in store for us over the coming year, as far as macOS is concerned.

With pandemics hopefully behind us, Apple’s planned OS updates have settled into a more regular pattern. Release dates when Sonoma was the current version of macOS (2023-24) were:

  • 14.0 – 26 September
  • 14.1 – 25 October
  • 14.2 – 11 December
  • 14.3 – 22 January
  • 14.4 – 07 March
  • 14.5 – 13 May
  • 14.6 – 29 July
  • 14.7 – 16 September.

Over the last year (2024-25), Sequoia has been almost identical, allowing for the small vagaries resulting from our calendar:

  • 15.0 – 16 September
  • 15.1 – 28 October
  • 15.2 – 11 December
  • 15.3 – 27 January
  • 15.4 – 31 March
  • 15.5 – 12 May
  • 15.6 – 29 July
  • 15.7 – 15 September.

If Tahoe follows the same pattern, you can expect releases to occur on the following dates:

  • 26.0 – 15 September 2025
  • 26.1 – 27 October 2025
  • 26.2 – 15 December 2025
  • 26.3 – 26 January 2026
  • 26.4 – 30 March 2026
  • 26.5 – 11 May 2026
  • 26.6 – 27 July 2026
  • 26.7 – 14 September 2026.

If you’d like a week’s notice of scheduled updates, watch Apple’s Developer Releases newsfeed at feed://developer.apple.com/news/releases/rss/releases.rss for Release Candidates. For minor versions, those are normally released about a week before the intended final release, so RCs seen on 20 or 21 October are likely to be followed by the public release on about 27 October.

Those can of course slip a few days or even a week if there are serious problems remaining with a release candidate, and some may be rescheduled to coincide with hardware announcements. These are also the ‘minor’ version updates, and Apple is likely to intercalate ‘patch’ releases to fix any serious bugs or urgent security vulnerabilities. Those almost never go through beta-testing or release candidacy.

For those staying with Sequoia or Sonoma for the time being, those security updates are most likely on the same dates as those for Tahoe.

Finally, a reminder for those whose Macs are still running macOS 13 Ventura: the final security update to 13.7.8 was released on 20 August this year, and Ventura is no longer officially supported by Apple. If your Mac can run Sonoma or later, and you want continuing security updates, then you’ll need to upgrade it to Sonoma 14.8 or later.

Apple has just released an update to XProtect for all macOS

By: hoakley
24 September 2025 at 03:42

Apple has just released its weekly update to XProtect, bringing it to version 5316. As usual, it doesn’t release information about what security issues this update might add or change.

This version adds nine new detection signatures to its Yara file. These include five with novel names:

  • MACOS.SULFURSLAB.JS
  • MACOS.FOXTAIL.DEST
  • MACOS.FLAMINGOFEET.AR
  • MACOS.COMPLIANTPIRATE.DEFU
  • MACOS.TETRAGONE.FU

together with MACOS.ODYSSEY.SOBGO for the recently added Odyssey, and MACOS.SOMA.SEENB, MACOS.SOMA.SEENC and MACOS.SOMA.INGOBA for the prolific Amos/Soma family.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5316

Sequoia and Tahoe systems only

This update has already been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5316 but your Mac still reports an older version is installed, you may be able to force the update using
sudo xprotect update

Last Week on My Mac: Things that go bump in the night

By: hoakley
21 September 2025 at 15:00

It has been barely a year since XProtect changed from stalwart to bogeyman. Over the course of dozens of updates through to macOS Sonoma, if there was one security data update you could rely on, it was XProtectPlistConfigData containing the many rules for XProtect. They guarded us through the dangerous days of Flash Player, the perils of ransomware, and a succession of stealers.

Then in Sequoia that changed, and XProtect’s data became stored in two locations, each with its own update method. The traditional location in CoreServices continued to be updated through softwareupdated, while the copy in the new location in /var/protected/xprotect has been updated by XProtectUpdateService over a connection to iCloud.

With both locations in play, XProtect updates have become more complicated. Some updates only came for one location, such as versions 5273 and 5275 that were released only to Sequoia’s new location. To help us manage XProtect in its new location, Apple provided a command tool, xprotect. That can check which version is available via iCloud, and update that when the local copy was no longer the latest.

One valuable feature was that it could also use a copy in the traditional location to update the new location, in the event that version was more recent than that available from iCloud, but most recently that has been disabled. Now, if a Mac running Sequoia or Tahoe has successfully updated its traditional location but not the copy in the new location, the user is unable to do anything to rectify that, and has to wait until that update is made available from iCloud. Sometimes both are provided at the same time, but it’s also common for iCloud to lag the traditional version by an hour or more, sometimes even longer.

Last week, with the update to XProtect 5315, the day after many of us were preoccupied with macOS updates, something even stranger happened. At around 18:00 GMT on 16 September, softwareupdated became able to download and install that new version into its traditional location, enabling macOS versions up to Sonoma to update successfully. But no such update was made available via iCloud for Sequoia or newly upgraded Tahoe systems, not for another 24 hours. Over that period attempts to obtain or convert the update using xprotect update were unsuccessful.

However, some hours after the traditional update was installed by those who had upgraded to Tahoe, XProtect’s new location was silently updated to 5315. Its version number had gone bump in the night. But if the xprotect command tool couldn’t accomplish that for the user, how could macOS? Were these silent updates coming by telepathy or radio waves?

Although there was no record in any of the usual places, such as Installations in System Information, or even found by my app SystHist, the xprotect version command disclosed that my Mac mini had updated XProtect’s new location at 06:46 GMT on the morning of 17 September, enabling me to hunt that event down in the log.

That update had been accomplished by a background check scheduled and dispatched by DAS-CTS (I have corrected times here to GMT):
2025-09-17 06:46:42.615072 com.apple.duetactivityscheduler REQUESTING START: 0:com.apple.security.syspolicy.xprotect-update:7874AD

This in turn fired up XProtectUpdateService
2025-09-17 06:46:42.695517 com.apple.xprotect Connecting to XProtectUpdateService
2025-09-17 06:46:42.744182 com.apple.security.XProtectFramework.XProtectUpdateService XProtectUpdateService booting
2025-09-17 06:46:43.157255 com.apple.security.XProtectFramework.XProtectUpdateService Attempting to apply update: [private]
2025-09-17 06:46:43.191178 com.apple.security.XProtectFramework.XProtectUpdateService Update completed. Activated update [private]

So the XProtect update had been completed and activated at 06:46 that morning. But how, given that iCloud was still only offering the old version?
2025-09-17 06:46:43.193159 com.apple.syspolicy.activities Finished Xprotect update in 496.4100122451782 ms: Error Domain=XProtectUpdateError Code=2 "Activated update LocalUpdate[5315]" UserInfo={NSLocalizedDescription=Activated update LocalUpdate[5315]}
2025-09-17 06:46:43.193285 com.apple.syspolicy Sent CloudTelemetry event: Xprotectupdateresult

“Activated update LocalUpdate” can only mean one thing, that XProtectUpdateService did what xprotect update used to do, and used the copy of XProtect 5315 in the traditional location to update the new location, taking just under half a second. In addition, com.apple.syspolicy had sent news of that event to Apple via iCloud.

That didn’t work for my old iMac Pro, still running Sequoia, though, which had to wait for the iCloud version of XProtect data to be updated, and wasn’t using version 5315 until 20:17 GMT on 17 September, over 26 hours after its initial release.

Prior to Sequoia, all supported and many unsupported versions of macOS got the same XProtect updates, available immediately they were released through Apple’s software update servers. Just over a year later,

  • Macs running Sonoma and unsupported versions of macOS could be updated as soon as the softwareupdated update became available, in the traditional way;
  • Macs running Sequoia could only be updated 24 hours later, when the iCloud update was made available;
  • Macs running Tahoe could have been updated at any time after the traditional update had been installed, until the update was finally made available through iCloud.

I’m so looking forward to the time when I don’t need to use SilentKnight, the xprotect command and my log browser LogUI to track XProtect updates, and when those become timely again.

iPhone 17 系列首发评测:你这是典型的「安卓」iPhone

By: 马扶摇
17 September 2025 at 20:11

每年在评测新 iPhone 的时候,爱范儿总会反复问一个问题:

新 iPhone 贯彻了怎样的设计哲学?

今年,苹果给出了三个清晰无比的答案——

造出极致轻薄 iPhone Air 的,是设计至上的苹果,为此,他们不惜在产品上做出了诸多妥协;

造出性能猛兽 iPhone 17 Pro 的,是技术驱动的苹果,他们用别出心裁的方式,造出了迄今为止最 Pro 的 iPhone;

而造出真香机 iPhone 17 的,是库存克星的苹果,他们用强大的供应链整合能力和自研技术优势,造就了高端手机市场里的价格屠夫。

这种明晰的定位,比前几年依靠屏幕尺寸和处理器性能,使人对大 Plus 和小 Pro 左右为难的情况截然不同。作为一名 iPhone 用户,我很清楚我该换什么手机——朋友圈里比往年晒得更多的订单截图,也佐证了这一点。

由于 iPhone Air 推迟发售,今年爱范儿评测的重心将会放在 iPhone 17 系列上,而经过这一周多的体验,我们得到了一个有趣的结论:

今年的 iPhone 17 系列,比以往任何时候,都更像「安卓」手机——这当然是褒义。

iPhone 17:库存克星

自 iPhone 11 以来,「标准版」的 iPhone 就总给人一种「标配即减配」的印象——但 iPhone 17 是个令人惊喜的例外。

有关 iPhone 17 的一切讨论,都离不开这块全新的屏幕——如果仅从硬件参数上看,iPhone 17 的屏幕几乎就是去年 iPhone 16 Pro 的同款。

这是 ProMotion 推出以来,标准版 iPhone 第一次用上高刷新率屏幕,打破了「ProMotion 必须要 Pro」的魔咒——

1-120Hz 可变刷新率,支持常亮显示的 LTPO 屏幕,甚至边框宽度都比 iPhone 16 缩窄了不止一点:

▲左边为 iPhone 17,右边为 iPhone 16

ProMotion 高刷屏带来的爽快感不言而喻,哪怕 iPhone 的调度策略不是全时锁定 120Hz,但相比 iPhone 16 上面那种字面意义上的「顿挫感」,仍然是巨大的提升。

更重要的是,今年愿意换标准版的人,大多是 12、13 代的老用户,我们在公众号评论区甚至见到了一位仍在使用 iPhone 7 Plus 的朋友。iPhone 17 加上 ProMotion,对于他们来说是真正意义上的「体验超速」了。

比起 iPhone 16 Pro,iPhone 17 的屏幕户外峰值亮度也更高,一举来到了 3000 尼特,甚至还用上了隔壁三星 Ultra 旗舰以及一些折叠屏机型会用到的抗反射涂层(Anti-reflective coating)。

根据我们的上手体验,iPhone 17 在晴朗户外的可读性相比 iPhone 16(甚至 16 Pro)都有相当程度的提升。其抗反射效果与三星类似,体现为屏幕在户外强光下,玻璃泛白、发灰的情况有所减轻。

只不过 iPhone 17 的屏幕抗反射效果只是相比前代明显,但是距离三星那种「让黑色更黑」的效果还有着不小的差距。哪怕是没有抗反射涂层、只贴了官方 AR 膜的 Z Fold7,也比 iPhone 17 更深邃一些:

iPhone 17 今年使用了第二代超瓷晶玻璃,在滑动时有点微微地涩手,且因为抗反射涂层的加入,选贴膜也变得更加考究。无论是为了改善手感,还是想保留抗反射能力,我们都建议优先选择 AR 膜。

更加倒反天罡的是,苹果甚至连 iPhone 17 的充电速度都做出了改进,最高充电功率来到了 35W 左右。

我们用 40W 的充电头实测,iPhone 17 的电量从 0 到 50% 只需要约 25 分钟,而充满则需要 80 分钟——有时候起床发现忘了充电,洗漱的时间临时充一会,也够 iPhone 应应急了。

▲iPhone 17 充电曲线图,蓝色折线为充电功率,红色折线为电流,绿色折线为电压

至于影像方面,iPhone 17 在两个方面做出了升级——超广角镜头从 1200 万像素升级到 4800 万像素,以及用上了新的正方形 CMOS 前摄。

虽然最近两年各家厂商都在发力长焦,但超广角镜头作为视觉冲击力最强的那个视角,仍然具有相当的不可替代性。本次 iPhone 17 升级到去年 16 Pro 同款的超广角,让拍出类似这样的可用画面成为了可能:

而本次全系标配的这套新的前摄——苹果称之为 Center Stage 前置摄像头——则是一个非常精妙的功能,因为它做到了一件和哈苏 X2D II 100C 差不多的事情:

用更精密的硬件和更复杂的功能,让拍摄本身变得简单。

放在 iPhone 17 上,就是现在 iPhone 可以自行判断你的自拍画面里有多少人、然后根据检测到的人脸数自动调整前摄的缩放和画幅,用更复杂的功能实现了更无感的操作。

根据爱范儿的测试,iPhone 17 会在只有一个人的时候保持普通竖向构图、两个人的时候切换广角但维持竖向,在画面进入第三个人且人脸比较分散的时候切换为横构图——在这个过程中,你的手都是完全不需要扭动,更不需要按任何按钮。

而得益于新的 2400 万像素正方形传感器,无论切换横竖构图,最后拍出来的自拍照分辨率都可以达到 1800 万像素,相比之前的 1200 万前摄仍然是可感的提升。

此外,苹果本次加入的前后同时录像功能也是相同的「机制复杂、简化摄影」的逻辑,虽然这项功能本身不新鲜,但是别忘了——它是建立在 iPhone 行业第一的录像能力和 iOS 无出其右的软件生态基础上的。

在大升级的屏幕和小改进的影像能力之外,iPhone 17 基本保持了与 iPhone 16 一样的三维和重量(17 比 16 略高 2mm、略重 7 克)。屏幕能够从 6.1 升级到 6.3 寸,主要就是得益于显著缩窄的边框。

至少在 iPhone Air 正式开售之前,iPhone 17 依然是整个 17 系列中手感最轻巧的那台。更重要的是, iPhone 17 的最低存储空间升级到了 256GB,加量不加价。

与其说这是 iPhone 17,不如说这是一台少了长焦镜头的 iPhone 16 Pro,特别是有了观感明显的 Pro 功能,你甚至可以当它是 16 Pro「青春版」。

iPhone 17 也是我们今年最推荐更新的机型,如果你是 iPhone 15 之前的用户,这是一个换机的好时机。

iPhone 17 Pro:技术驱动

比起「压倒性好评」的 iPhone 17 标准版,iPhone 17 Pro 的风评倒是褒贬不一,分歧主要集中于外观设计。

在经历过 15 Pro 和 16 Pro 两代钛金属之后,苹果在 iPhone 17 Pro 上放弃钛合金、重新回归了最传统的铝合金。但这并非保守和倒退的体现,而是苹果整了一个更大的活——

在新的铝合金机身上,苹果尝试了一种新的加工工艺:热锻铝金属一体成型(Heat-forged aluminum unibody)。这是一种手机行业不常见、但在汽车工业领域已经被广泛应用的加工技术。

▲苹果发布会上演示的一体成型机身|Apple

相比 CNC 工艺只能在成品铝料块上加工,热锻一体成型工艺因为需要在金属的「再结晶温度」以上进行,可以避免金属内部在加工过程中形成不规则结晶区,组成疏松和气孔结构,从而最大程度发挥出铝合金的强度、韧性和抗疲劳性能。

这种一体成型工艺的优点,一上手便知——

前两代 Pro 的确极大改善了「硌手」的口碑,而 iPhone 17 Pro 更大的边框弧度,又一次将 iPhone 16 Pro 远远甩在后面,甚至可以称之为「手感最好的直屏 iPhone」。

除了手感大升级,从钛金属换回铝合金还带来了另外两项材料优势——由于铝合金比钛合金更容易着色,今年的 iPhone 17 Pro 多出了这个醒目的「星宇橙」,比起前几年的「禁欲系」配色鲜亮不少。好不好看见仁见智,但包你换了新机一眼就能被认出来。

此外,钛金属虽有重量和强度上的优势,导热性能却并不优秀,而铝的热导系数接近钛的 20 倍,iPhone 17 Pro 的散热能力相比 16 Pro 提升是非常明显的。

在聊实际散热手感之前,先分享一些发热测试数据:将 iPhone 16、17 两代 Pro Max 屏幕调至最大亮度,并打开 4K 120Hz 进行录像,这样可以比较好的排除户外机身升温的干扰、更清楚的看到散热路径。

首先是上一代 iPhone 16 Pro Max:从热成像延时中可以看到,16 Pro Max 的发热点位非常集中,主板位置的最高温度接近 45°C,且由于背板玻璃和钛合金中框导热不畅,机身的下半部分始终没有怎么升温,无法有效参与到机身的散热过程中:

iPhone 16 Pro Max 4K 120 帧最高亮度录制半小时,最高温点位约 44.8 度

再看全新 iPhone 17 Pro Max:

  • 可以看到铝合金凸台和边框在主板热起来之后不久就迅速升温,沿着左右边缘迅速将温度传导了下去
  • 机身内部新增的 VC 均热板和钢壳电池共同作用,快速把主板上的积热铺开
  • 最终,iPhone 17 Pro Max 的机身最高温度,相比 16 Pro Max 低了两度,且在超过半小时之后也没有继续攀升。

这样的效果转换到游戏场景中,就是我们手持 17 Pro 玩《崩坏 星穹铁道》的时候,可以明显感觉到边框、背板和镜头凸台都在均匀发热,说明处理器的热量被有效传递到了更大面积的机身上、与空气热交换的效率更高。

iPhone 17 Pro Max 4K 120 帧最高亮度录制半小时,最高温点位约 42.6 度

更好的散热表现,意味着 iPhone 17 Pro 能够更有持续性地进行性能释放——无论是拍照、游戏,还是高强度回微信,手机都只是温温地不烫手。散热越好,降频越少,手机当然也没那么容易卡顿了。

同样,升级的散热也能够支持 iPhone 17 Pro 更长时间地高功率充电。实测下来,我们发现 iPhone 17 Pro 的最高充电功率可以长时间稳定在 30W 以上,Pro Max 甚至可以稳定地以 35W 的功率进行充电。

使用苹果官方的 40W 充电头, Pro 和 Pro Max 在 20 分钟以内就能充到 50% 的电量,和 iPhone 17、iPhone Air 等沿用三明治结构的机器相比,整体充电速度快了不少。

▲iPhone 17 Pro Max 充电曲线图,蓝色折线为充电功率,红色折线为电流,绿色折线为电压

诚然,VC 均热板在 Android 高端手机上已经屡见不鲜,但敢于果断抛弃大面积玻璃背板、将铝合金机身和 VC 共同设计为一个整体发挥效果,我们依然会感叹这确实是「技术驱动」的苹果,才能造出来的产品。

技术驱动这一点,落到 iPhone 17 Pro 全新升级的影像系统上,同样成立——我说的,就是那颗 4800 万像素的 4 倍长焦镜头。

iPhone 16 Pro 上面那颗 5 倍 1200 万像素的长焦镜头,经常被人诟病传感器过小、解析力不够,而 iPhone 17 Pro 将长焦原生倍率缩减到更常用的 4 倍(等效全画幅 100mm),并且将传感器面积扩大了 56%,不仅可以输出 4800 万像素的全尺寸照片,也能进一步裁切、当做的 1200 万像素的 8 倍长焦(等效全画幅 200mm)镜头来用,可以说进可攻退可守。

毕竟 iPhone 17 Pro 系列的主摄仍然是 24mm,从 1x 到 8x 实际上囊括了 24-200mm 的所有焦段——四舍五入,也相当于那颗被誉为「天涯镜」的腾龙 28-200mm 装在 iPhone 上了。

这套大底长焦的配置,也是许多国产影像旗舰手机采纳的方案——其带来的直接优势,就是 iPhone 17 Pro 调用长焦的频率相比 16 Pro 有了明显提升。

与此同时,苹果新的图像处理管线也不再固执己见,变得更愿意用适当的涂抹交换纯净度,显著提高了长焦的可用性:

影像系统的另一个重大更新,是全焦段都用上了 4800 万像素的融合镜头,使得 iPhone 17 Pro 系列的多镜头一致性更上一层楼,且超长焦和超广角镜头都变得更好用了,就算是在弱光或者室内环境,也能拍出质感在线的照片,而不至于满屏噪点:

超广角(0.5x):

超长焦(8x):

可惜的是,尽管 iPhone 传感器面积变大了,总的来说还是不够大……和国产旗舰相比,依然逃不过「底大一级压死人」的命运:

除了硬件升级,苹果还给原相机 app 加上了一款新的摄影风格「珠光」(Bright)。它的出片效果有点类似加两档曝光的富士胶片配方,是社交网络上最流行的色彩风格之一,更能轻松拍出适合亚洲肤色的「白里透红」效果,避免标准风格的黄蜡色调

如果你用 iPhone 拍人像很多的话,爱范儿甚至建议你可以将「珠光」作为默认的摄影风格来使用。值得一提的是,它并非 Pro 系列独占,iPhone 17 以及更新 iOS 26 之后的 iPhone 16 系列都可以获得。

今年的 iPhone 17 Pro 仍然是「有史以来影像能力最好」的 iPhone。如果你此前就喜欢用 iPhone 拍、在 iPhone 上修、直接用 iPhone 发图的话,iPhone 17 Pro 是近年表现最好的一代,甚至掏出「苹替」Android 影像旗舰的机会都变少了。

至于今年 ProRes Raw 录制规格、Genlock 以及时间码功能的加入,更多是为了方便 iPhone 融入影视剧组中的工作流。

过去的一段时间,我们越来越多地看到 iPhone 出现在一些电影机难以触达的角落,比如《F1:极速狂飙》车身上用 iPhone 相机总成改装的固定机位,以及《惊变 28 年》中用十几台 iPhone 拼搭出的子弹时间相机:

图|TheVerge

iPhone 17 Pro 上这些准专业功能(包括 299 美元的 Blackmagic 时间码拓展坞)可以帮助 iPhone 进一步在影视行业片场中站稳脚跟,整体来讲是在向着光谱中「更加专业化」的那一端推进的——

这也是我们在今年 iPhone 17 全系列机型中看到的最大趋势:iPhone 17 让普适的更加普适,而 iPhone 17 Pro,则是让专业的更加专业。

而那个没有数字代际后缀的 iPhone Air 又代表了什么呢?

iPhone Air:设计至上

由于国行 iPhone Air 推迟上市,评测也一并推迟了——编辑部那个对 Air 望眼欲穿的同事,只能自制壁纸解解馋了。

但,这并不妨碍我们为 iPhone Air 定下论调:尽管它既不普适也不专业,但 iPhone Air 代表的,仍然是那个「设计至上」的苹果。

此前,爱范儿曾报道过苹果在接下来两年的 iPhone 路线图,提到了由于要给折叠屏让路,iPhone 18 标准版可能和 e 系列一起推迟到 2027 年春季发布——明年秋季只有 iPhone 18 Pro/Max,和传闻中的折叠屏 iPhone。

图|9to5Mac

这样就将 iPhone 原本完全基于数字划分的机型迭代逻辑做出了调整。

爱范儿猜测:苹果接下来除了按照「秋季 Pro 春季标准版」的规律更新数字系列之外,还会不定期的推出像 iPhone Air 这样不含数字、只描述产品特点的设备

这样的好处有两个,一是可以将 iPhone 的热度在一年的时间跨度里分配得更平均,避免了此前 9 月份发布、来年 Q2 和 Q3 的销售数据落底,要靠国补/大促「挽尊」的情况。

而是,这样做可以给用于技术验证的 iPhone 机型留下充足的空间,让苹果可以跳出传统的模式,做一些更加大胆的尝试。

今年的 iPhone Air 就是如此,它肯定不如 iPhone 17 实用,也不如 iPhone 17 Pro 好用。这也是爱范儿在开头提到的「妥协」所在——但 iPhone Air 却美得不可方物,更重要的是,给未来的 iPhone 留足了想象空间。

比如类似曾经的 12 寸 MacBook 与 M1 MacBook Air 一样,iPhone Air 的零件集成度非常高,主板几乎完全压在了镜头凸台下方,将剩余的空间全部留给了电池和尾插。

图|Apple Newsroom

这样的布局在 6.5 寸的 iPhone Air 里或许显得有些捉襟见肘,但是如果放在传闻中空间更充裕的「纯玻璃 iPhone」里面呢?

iPhone Air 最大的意义,就在于其设计上的各种技术实践——专为无线连接性能定制的 N1 芯片、超高整合度的「高原」(plateau) 主板、抛光钛合金中框……许多激进的设计和妥协的功能,就这样被嵌入到同一部手机当中,有一种矛盾之美。

虽然 iPhone Air 和三星Galaxy S25 Edge 在硬件形态上都是超薄手机,但两者的产品思路是很不一样的。

三星的 S25 Edge 是将现有直板机的技术压缩到极致形成的超薄,优点是实用性更强,但是对于其他形态的指导和借鉴意义就没那么大了,是一种形态终末期的集大成者

但 iPhone Air 是一款外在虽然近似,但内在和以往截然不同的产品,和当年的 iPhone X 一样,更像是新物种的开端

当然,客观的现实就是,成熟技术的集大成者就是要比新物种的开路先锋更实用也更便宜,即使 iPhone Air 能够如期上市,我们仍然不推荐大家盲目下订

更「安卓」的 iPhone,和三位一体的苹果

纵观今年的 iPhone 17 系列,我想你也会有类似的熟悉感:标准版加量不加价,旗舰款堆散热堆影像,还有概念机秀肌肉——所有这一切,不就是典型的「安卓思维」吗?

这里的「安卓」当然是褒义——国补到手价 5499 元的 iPhone 17 标准版截至开放预订前(约发布会后 30 小时左右),在单一电商平台已经积攒了超过 300 万预约量,是去年的十五倍。

可以预见的是,在今年的双十一、明年的 618,甚至明年的双十一时,叠加了平台优惠、店铺优惠和国补「3 buff」的 iPhone 17……没准会在一整年中的大部分时候销量霸榜。

尽管那时一定会有配置比它高、价格比它低的选择出现,但在 4000-6000 高端手机主流价位段,绝大多数消费者的选择是非常朴素的——高刷屏、性能好、充电快、拍照也过得去的新 iPhone,面对标新立异的同名手机,依然有着强大的竞争力。

我们可以用一个常见的商业概念来描述这样的需求:总拥有成本(Total Cost of Ownership, TCO)。不只是硬件,消费者对于系统和生态未来预期的「心理成本」,实际上也是手机 TCO 的构成部分

而 iPhone 17 搭配 iOS 26,就是这个价位段一套 TCO 相对较低且稳定的选择,一台下单之后不需要担心马上过气的水桶机,同时拥有着现在行业内最强大的系统生态号召力。

iPhone 17 Pro 和 Pro Max 则比以往更加偏向「专业化的影视工具」,非常利好小型制作组、个人频道、规模不大的片场等等——《F1》电影爆火之后,苹果已经在电影制片行业站稳脚跟,后面应该能看到更多 iPhone 参与制作的影视内容。

至于 iPhone Air,我想会逐渐成为下一个世代 iPhone 设计的基准,通往智能手机进化的尽头。

无论如何,我们在今年的三台新 iPhone 上,看到了库存克星的苹果,也是技术驱动的苹果,更是设计至上的苹果——这是属于苹果的三位一体。

我当然希望每年的每一款 iPhone 都能臻于完美,也同样欢迎 iPhone 像「安卓」手机一样好用——只是对于本就竞争激烈的主流价位段,新 iPhone 的到来,可能会给竞争对手们,狠狠上点强度。

#欢迎关注爱范儿官方微信公众号:爱范儿(微信号:ifanr),更多精彩内容第一时间为您奉上。

爱范儿 | 原文链接 · 查看评论 · 新浪微博


Apple has just released an update to XProtect for all macOS

By: hoakley
17 September 2025 at 02:21

Apple has just released its weekly update to XProtect for all supported versions of macOS, bringing it to version 5315. As usual, Apple doesn’t release information about what security issues this update might add or change.

This version adds three new detection signatures to its Yara file, two for a new entry named Zuru as MACOS.ZURU.LOAD and MACOS.ZURU.BEACON, and the third as another Soma/Amos component named MACOS.SOMA.SEENA.

You can check whether this update has been installed by opening System Information via About This Mac, and selecting the Installations item under Software.

A full listing of security data file versions is given by SilentKnight and SystHist for El Capitan to Tahoe available from their product page. If your Mac hasn’t yet installed this update, you can force it using SilentKnight or at the command line.

If you want to install this as a named update in SilentKnight, its label is XProtectPlistConfigData_10_15-5315

Sequoia and Tahoe systems only

This update has finally been released for Sequoia and Tahoe via iCloud. If you want to check it manually, use the Terminal command
sudo xprotect check
then enter your admin password. If that returns version 5315 but your Mac still reports an older version is installed, you should be able to force the update using
sudo xprotect update

Update: as of 1100 GMT 17 September 2025, Apple still hasn’t released this via iCloud for Sequoia and Tahoe systems.

Further update: Sequoia and Tahoe systems are now receiving the 5315 update silently, without any change in the version reported by the xprotect tool. So don’t be surprised if your Mac gets updated without the xprotect tool knowing anything about it.

Further further update: over 24 hours after release of this update for older macOS, it has now been made available via iCloud, and the xprotect commands now work, for those Macs that still haven’t updated themselves.

iPhone 17,会成为新一代钉子户吗?|选购指南

By: 周奕旨
16 September 2025 at 11:41

刚刚,苹果开完了 2025 年的秋季发布会。

爱范儿第一时间在发布会现场,上手体验了今年四款全新的 iPhone,直接说感受——

和以往一条大道从标准版通往 Pro Max 不同,今年的 iPhone,的确是近年来最丰富有趣的一次,也是最值得买的一次。

这是 iPhone 的「大年」,也是 iPhone 走向「多样化」的元年,在这个热闹的十字路口,选择变多了,也变难了。

在体验后,我们也总结了这篇指南,帮你拨开迷雾,找到那台最适合你的 iPhone。

先说结论,方便你对号入座:

  • iPhone 17(6000 档):有高刷,A19 芯片,等等党的全面胜利,如果你习惯一台手机用好几年、「花小钱办大事儿」,那么 iPhone 17 标准版颇有成为新一代钉子户的潜力,同时也对钱包最为友好;
  • iPhone Air(7000 档):如果你想要一台极具个性的手机,并且不在意续航和拍照,那么集精致与手感为一身的 iPhone Air 就是你的不二之选;
  • iPhone 17 Pro / Pro Max(9000 档及以上):但凡你有影像需求,那就无脑选择 Pro 与 Pro Max——全 4800 万像素阵列,ProRAW、ProRes RAW 等专业格式,完全可以充当生产力,配合 A19 Pro,是创作者和重度游戏玩家准备的「毕业级」装备,目前 iPhone 队列中集大成的存在。

目前,关于 iPhone Air 的 eSIM 还有诸多问题等待回答,除了官网信息外,我们参考了苹果以往的 eSIM 情况并进行汇总,供大家参考:

  • 问:中国买的能不能在境外用当地 eSIM?
    答:可以,国行 Air 在境外可以激活当地 eSIM(必须开启定位)
  • 问:境外买的能不能在中国用联通 eSIM?
    答:不可以,仅有型号为 A3518 的 iPhone Air 能在中国通过 eSIM 激活,外版无法安装配置文件。
  • 问:中国买的能不能在境外用联通 eSIM?
    答 :不确定,具体情况要看中国运营商是否提供国际漫游 eSIM 业务。
  • 问:境外买的能不能在中国用境外 eSIM?
    答:可以,但需要在境外激活,同时运营商提供国际漫游 eSIM 业务。
  • 问:中国买的能不能在中国用境外 eSIM?
    答:不确定,但根据 iPad eSIM 来看,条件非常苛刻,激活时需要在境外,同时运营商提供国际漫游 eSIM 业务。
  • 问:境外买的能不能在境外用联通 eSIM?
    答:不行,根据官网信息看,要在境内为 iPhone Air 激活 eSIM,必须拥有一台在中国大陆支持 eSIM 的 iPhone(目前唯一支持的机型是 iPhone Air),并在线下营业厅办理。

iPhone 17:今年最值得购买的水桶机

这么多年来,iPhone 标准版一直有个意难平:没有高刷。

作为「旦用难回」的功能,高刷可能不如芯片、影像那样显眼,但它对体验的影响却是立竿见影的——习惯了高刷屏的丝滑流畅,再回到 60Hz,眼睛就会立刻抗议。

正所谓,由奢入俭难。

而在之前,苹果的策略一直是把最好的屏幕和长焦镜头、LiDAR 这些专业功能牢牢绑在一起,结果就是许多人为了屏幕,不得不硬拔预算,入手 Pro。

今年,这块最后的短板,终于得到补齐。苹果的「良心」,已经下探到 6000 元价位了。

ProMotion 高刷新率的下放,让 iPhone 17 标准版的屏幕刷新率终于来到了最高 120Hz。

这个数字带来最直观的改变,是 iPhone 17 标准版变得跟手了许多。根据爱范儿在现场体验区的上手感受,快速划过屏幕时,文字和图片不再有明显的模糊拖尾;在应用切换时,动画过渡也更流畅顺滑,操作过程更自然,让日常的每一次操作看起来更清晰、更轻快。

当然,为了产品线的区隔,iPhone 17 搭载的 A19 处理器,按惯例还是比 Pro 系列的 A19 Pro 稍逊一筹,不过比前代性能和功耗都有所提升,完全足以应对日常使用。

另外,iPhone 17 的屏幕也将与 Pro 系列看齐,从前代 6.1 英寸来到 6.3 英寸,亮度来到了 3000 尼特,同时前置摄像头的尺寸是前代的两倍,换为了方形 CMOS 传感器,并升级到 1800 万像素,上一代独属于 Pro 系列的 4800 万像素超广角摄像头也来到了 iPhone 17 标准版上。

可以说,今年的 iPhone 17 就是没有长焦的 iPhone 16 Pro。

最后,iPhone 17 标准版的起步存储为 256GB,起步价格为 5999 元。

如果考虑到部分地区的国补,17 标准版 256GB 的价格可能会来到 5499,如果再叠加部分老机型的以旧换新,可能一个 iPhone 12 Pro 用户的换机成本只需要两到三千,却能换到最新的 A19 芯片、8GB 运行内存和新的影像系统。

这样的 iPhone 17,是等等党的强力起钉器,注定也会是未来好几年里的最强「钉子户」。

综上所述,我个人认为今年的 iPhone 17 标准版是最值得购买的机型,这是一台不再让人纠结的「水桶机」,努力补齐了最后的短板,也守住了大多数人的钱包。

它最适合的,是那些务实、理性的用户,如果你手握 6000 至 7000 的预算,离不开苹果生态,希望手机能用得久一点、舒服一点,但又觉得 Pro 系列的很多功能(比如长焦、LiDAR)对自己来说是不必要的需求。

那么,今年的 iPhone 17 标准版,就是那个最稳妥、也最聪明的选择。

iPhone 17 Pro / Pro Max:这一次,Pro 得很彻底

如果说标准版的升级是「补齐」,那 Pro 系列的进化,就是一次彻底的「起飞」。

最大的惊喜,毫无疑问来自藏在全新横向 Deco 设计中的那个三摄模组。

过去,即便是 Pro 系列,在广角、超广角和长焦之间切换时,你偶尔也能感觉到画质和色彩上的不统一。而这一次,三颗 4800 万像素主摄级别的传感器,彻底解决了这个问题。

无论你是在录制视频时平滑地从超广角变焦到长焦,还是在拍照时切换不同焦段构图,都能获得几乎同样出色的画质和细节,各焦段镜头切换时的「跳跃感」将不复存在,画质保持高度一致,整个影像体验会变得前所未有地连贯。

更值得一提的是,Pro 和 Pro Max 独占的那颗全新 4800 万像素长焦镜头。它的原生焦段是 4×(约 100mm),加上无损变焦,最高可达 8× (约 200mm)光学级效果,同时 CMOS 尺寸比前代的 5× 长焦增加了 56%,远摄能力直接翻倍,解析力也获得了提升,进一步拓展了 iPhone 焦段的可用范围。

同时,iPhone 17 Pro 与 Pro Max 可以拍摄 ProRes RAW 格式视频,这是一种相当专业的视频格式,拥有极大的后期空间。

另一边,iPhone 17 Pro 和 Pro Max 配合满血 A19 Pro 芯片,无论是日常轻量级操作,还是影像创作或大型游戏这样高功耗场景,都能提供苹果阵营最佳的使用体验。

当然,今年 Pro 型号在售价和起步规格上也有微妙变化——iPhone 17 Pro 的起步内存来到了 256GB,售价为 8999,比前代的 128GB 起售价高了 1000 元,看齐前代的 256GB;

而 iPhone 17 Pro Max 的起步价为 9999。

上 Pro 的门槛进一步提高,也算是一种变相涨价了。

所以问题来了——Pro 和 Pro Max,适合谁?

对于今年的 Pro 和 Pro Max 来讲,芯片、影像系统以及机身材质一模一样,屏幕尺寸和电池容量是唯二的区别。

如果你手握九千元以上的预算,且对影像有明确的要求,特别是经常拍视频,抑或是演唱会常客,对长焦有较大需求,那么就可以跳过标准版,直接上 17 Pro——

Pro 的意义,就是用绝对的性能,抹平现实与创作欲之间的距离,你可以收获 ProRAW、Log 等专业影像格式,拥有更多的后期空间,以及更大的焦段可用性。

而如果你极其看重续航,或者是重度手游或影音用户,追求大屏沉浸和持久续航,那么配备 iPhone 序列最大电池和 6.9 英寸屏幕的 Pro Max,才是你的最终答案。

iPhone Air:Fold 的试验品,市场的新试探

在如今这个信奉「多即是好」的时代,当所有手机都在比谁的摄像头更多、电池更大、机身更重时,iPhone Air 的出现,显得如此格格不入。

像乔布斯从牛皮纸袋里抽出的第一代 MacBook Air 一样,iPhone Air 同样做出了取舍——唯一的摄像头,意味着你放弃了长焦和超广角的便利性;更薄的机身,也几乎注定了它的续航不会是第一梯队。

5.6 毫米的厚度、超薄的电池以及背部那颗孤零零的摄像头,都在传递一个信号:这是一台性格鲜明、定位大胆的产品。

值得一提的是,在 iPhone Air 上,苹果选择搭载曾经独属于 Pro 和 Pro Max 的 A19 Pro 芯片,为这个超薄新机型配备了强悍的性能。

之前爱范儿的报道和分析来看,iPhone Air 的出现有两个目的——

近年来,iPhone 的创新趋于平稳迭代,饱受创新缺乏的诟病,但智能机已经进入平稳期,哪怕是苹果也跳不出这个循环,如果在已有机身上玩不出花样,那就另起炉灶,重新定义一个机身,以此来看智能手机市场是否还有可以拓展的空间。

部分调查结果,也为苹果的试探提供了一定的底气——

SellCell 的调查中,有 47.5% 的人表示 iPhone Air 机身变薄电池缩小「可以接受」,但与此同时在愿意升级的原因中,现有手机续航不够用的占比,高达 53.2% 的用户。

这个数据表明,在一群追求「水桶机」的用户之外,还存在着将近一半的另一群人:他们对手机的「感觉」——握在手里的感觉、放在口袋里的感觉的重视,超过了对功能和续航的执念。

而另一个目标,则是实验。

据多方消息称,苹果打算在未来推出折叠 iPhone,对于折叠屏这样形态与直板机型完全不同的手机而言,设计思路也会相应改变,如此多的元器件、电池、影像模组,怎么高度集成在极低厚度的设备中?

此时,iPhone Air 就是一个无比合适的试验田,为折叠 iPhone 的设计与制造积攒宝贵的经验,并加以验证。

我想,这也是为什么这个机型最后取名 Air,而没有加入 17 家族的序列中的原因。

那么,这台极具个性的 iPhone Air,适合谁呢?

其实,刚刚的分析中已经讲得很明白了,如果你不在意手机的影像能力,平日里只有扫码需求,也没有续航焦虑,同时想尝试一些新鲜东西,或者追求一定的精致与差异化,而且恰好手里有 8000 元以上的预算。

那么 iPhone Air 是个比其他版本都更有个性的选择。

当然,需要注意的是,iPhone Air 没有实体 SIM 卡槽,而 eSIM 只有中国联通支持,需要用户持身份证前往线下营业厅办理激活。

不过根据最新消息,中国电信回应上海证券报表示,电信的 eSIM 手机业务已全面准备就绪,将在获得工业和信息化部商用试验正式批复后,向用户正式开放。

几乎同时,中国移动官方微博也表示,中国移动已支持 eSIM 手机业务,稍后放开服务将另行通知。

▲ 图片源自 中国资本市场法定信息披露平台

在 iPhone 的最后,我们还想提一个暂时没有人注意的升级——随 iPhone 17 系列而来的,还有全新的 AVS (Adjustable Voltage Supply)动态充电技术。

这种技术本来用于大功率设备上,在高电压区间中做细节操作,让性能更稳定,而 iPhone 17 系列支持的是专为手机、平板和轻薄本这样功率不算高的设备专门设计的 SPR AVS。

这个技术,有什么直观的好处呢?

简单来说,SPR AVS 更聪明、也更细致,能在充电过程中精准调节电压,不像传统充电那样死撑硬涨,导致多余能量变成了热量,而是文火慢炖、按需供给,手机需要多少,就精准地提供多少,尽最大努力避免手机发热。

同时,SPR AVS 也能让充电的整个动态过程变得前所未有地稳定,避免重新握手,电压过渡平滑得你几乎感觉不到。

这些优点落到实际体验上,就是你最在意的电池健康度,会比现在更「坚挺」。

值得一提的是,制糖工厂的 AI 小电拼,将会通过 OTA 成为首个支持 SPR AVS 的动态电源,覆盖到所有 AI 小电拼用户,让这项技术直接来到你们的新手机中。

今年,是一个换机的好时候,也是一个思考的好时候

最后,我们还是来看看 iPhone 之外的东西——

在秋季发布会上,苹果更新了 AirPods Pro 产品线,重构了内部设计、低音变得更加饱满、续航也有所增加且降噪效果达到上代两倍的 AirPods Pro 3 来到我们面前,尤其值得提一的是,AirPods Pro 3 的售价较前代没有涨价,依旧是 1899 元,可谓是加量不加价了。

如果你对续航、降噪有更进一步的需求,或是旧耳机已经不堪重负,那么 AirPods Pro 3 非常推荐购买。

而另一边,Apple Watch S11 的外观设计并没有大变化,带来了更耐磨的屏幕,同时还上线了血压提醒和睡眠评分的功能(血压提醒功能可能需要等待国行审核通过后上线),售价 2999 元起。

不过,要提醒一句的是,Apple Watch S11 并没有升级芯片,大家关心的快充也没有回归,同时血压提醒功能会逐步下放到 S9 及以后的机型。

换句话说,如果你用的是这以后的机型,那么除非有特殊需求,也没有升级的必要(甚至到现在,我还在用 S4)。

聊了这么多,让我们将目光放回今天的主角 iPhone。

毫无疑问,今年是 iPhone 久违的一个「大年」。

延续多年的设计,在这一代上终于出现了大改,让别人看出你用新 iPhone,终于不用只靠颜色了——全系标配的高刷、加量的起步内存、全新的机身设计,配合液态玻璃设计的更新,整个 iPhone 阵容都焕发出久违的新鲜感。

而另一边,这也是 iPhone 走向多样化的元年——

这意味着苹果终于开始正视用户群体的多样性,你不再需要在几个相似的选项里做排除法,或是为不需要的功能白白付钱,而是可以根据自己的预算和最核心的需求,直接找到那个「天选之机」。

从我的角度来看,今年的 iPhone,可以算是这几年里升级幅度最大的一代了。

那么,应该立刻就换吗?

如果你手上的 iPhone 是 15 系列以前的机型,或是已经卡顿到影响日常使用,或者你恰好是今年某款新机精准命中的目标用户,那么别犹豫,现在就是最好的时机。

同时,在 iPhone 17 标准版面前,我认为 iPhone 15 和 16 两代标准版已经完全丧失了竞争力,可以越过,直接考虑 iPhone 17,至于 Pro,大家根据需求判断即可,如果手上宽裕,顶配的 2T 也不是不行。

但如果你手上的设备还用着挺顺手,只是单纯被新鲜感所吸引,那不妨再等一等——从各路消息来看,iPhone 的「大年」才刚刚开始,我们念叨了很久的打孔屏、屏下摄像头、甚至是全玻璃机身,可能都在不远的未来排队等着了。

如果你对苹果生态没有强需求,又或者是想要换换别家的手机,试下花样更丰富的国产阵营,那也可以再等等——即将到来的年底,还有一大批国产旗舰整装待发。

不过话说回来,数码产品终究是服务于人的,在能力范围内,选一台能让你用得开心、拍得尽兴的设备,然后去生活,去创作,去记录,这或许比无尽的等待更有意义。

毕竟,早买,早享受嘛。

让我有个美满旅程

#欢迎关注爱范儿官方微信公众号:爱范儿(微信号:ifanr),更多精彩内容第一时间为您奉上。

爱范儿 | 原文链接 · 查看评论 · 新浪微博


Apple has released macOS 26 Tahoe, and Sequoia 15.7, Sonoma 14.8

By: hoakley
16 September 2025 at 01:14

Apple has just released macOS 26.0 Tahoe (build 25A354), together with security updates to Sequoia taking it to 15.7, and for Sonoma to 14.8. As expected, there are no further security updates provided for Ventura, which is now unsupported.

The upgrade to Tahoe is once again provided as an ‘update’ rather than a full Installer app. If you want to run the Installer app to upgrade, download it from the App Store rather than using Software Update. If you’re updating Sequoia or Sonoma and your Mac is capable of running Tahoe, be very careful to select the right update in Software Update.

The Tahoe upgrade weighs in at 7.7 GB for Apple silicon Macs upgrading from a recent version of Sequoia. For Intel Macs it should be 6.1 GB.

On Apple silicon Macs, iBoot is updated to version 13822.1.2. Intel Macs have their firmware updated to version 2092.0.0.0.0 (iBridge 23.16.10350.0.0,0). Safari is version 26.0 (21622.1.22.11.14). The Darwin kernel version is 25.0.0.

Security release notes are also available:

  • Tahoe 26.0 lists 75 vulnerabilities fixed, none of which is reported as already being exploited.
  • Sequoia 15.7 lists 34 vulnerabilities fixed.
  • Sonoma 14.8 lists 38 vulnerabilities fixed.

Useful links

Prepare to upgrade macOS – what you should have done already
What should you do when an update goes wrong?
When you should use Safe Mode, and what it does
What to do when there’s something fundamentally wrong with an Apple silicon Mac
Eclectic Light software updates for Tahoe

Last updated at 1928 GMT 15 September 2025. My apologies for some previous incorrect versions, which were the result of an unintended update.

A brief history of AppleWorks

By: hoakley
13 September 2025 at 15:00

The Mac wasn’t the only innovative product shipped by Apple in 1984. At the time, the company was still making its money from selling updated versions of the Apple II, and by then was offering models with 128 KB RAM. For those it provided a demo product developed by Rupert Lissner called AppleWorks. This was one of the first integrated ‘office’ suites, consisting of a word processor, spreadsheet and database, all within the same app.

The original 128K Mac shipped with its own two ‘killer’ apps, MacWrite, developed first by Encore Systems led by Randy Wigginton, and MacPaint, written in-house by the late Bill Atkinson (1951-2025), with its interface designed by Susan Kare. The first integrated ‘office’ suite for Mac was probably Lotus Jazz, released in 1985, and that was followed by Microsoft Works in 1986. Jazz was intended to replicate the success of Lotus 1-2-3 on PCs and proved popular with some, but it was generally considered to be overpriced at $595 and underpowered, and flopped.

Microsoft Works came from an integrated suite being developed for the Mac by Don Williams and Rupert Lissner (original developer of AppleWorks), both former Apple employees. Although first released for the Mac (apparently), it soon followed for DOS PCs, and in 1991 was released for Windows 3.0.

Meanwhile, Apple spun its app development out to its wholly-owned subsidiary Claris in 1987, but no progress was made in developing AppleWorks for the Mac. The following year, Claris bought FileMaker, a database, from Nashoba Systems, which it rebranded to FileMaker II to conform with its other Mac apps, and in 1990 it was succeeded by FileMaker Pro 1.0. However, that year Apple decided to keep Claris as a subsidiary rather than taking it public, and most of its executives resigned. AppleWorks for Apple II was upgraded by Beagle Bros, then licensed to Quality Computers.

Bob Hearn and Scott Holdaway wrote a completely new version of AppleWorks, this time for the Mac, and that was published by Claris as ClarisWorks 1.0 in October 1991. Initial modules included a word processor, drawing, painting, spreadsheet, database, and a communications terminal.

Apple’s financial woes in the 1990s brought further change. The ClarisWorks team left to develop a similar suite for BeOS, FileMaker and Claris HomePage were retained by its subsidiary, now renamed FileMaker, and its other products including ClarisWorks were brought back into Apple. Since then, HomePage was discontinued, and FileMaker changed its name to Claris International to continue developing and selling its FileMaker database products.

AppleWorks 5.0 was released in 1997 and saw Classic Mac OS through from System 7.0.1 to Mac OS 9.

That was followed by AppleWorks 6.0 in January 2000, which dropped the communications terminal in favour of a presentation module. This supported both Classic Mac OS and the new Mac OS X, although it was unable to use many of the latter’s new features. The last update to 6.2.9 was released in January 2004, and in August 2007 Apple declared AppleWorks dead, replaced by the iWork suite of Pages and Keynote in January 2004, followed by Numbers in 2007, three separate apps rather than an integrated suite. Since 2013, that suite has been provided free with each Mac user’s Apple ID.

AppleWorks was rich with document templates from brochures to postcards. It’s seen here running in Mac OS X 10.0 Cheetah in 2001.

Its word processor could export to HTML, and Microsoft Word formats thanks to its support for Claris XTND technology. This is in Mac OS X 10.1 Puma in 2002.

This shows its word processor with its Accents palette at the right and integrated drawing tools at the left. This is in Mac OS X 10.2 Jaguar in 2003.

These are AppleWorks’ word processor document preferences, in Mac OS X 10.4 Tiger in 2006.

This is one of the popular certificate templates used in the drawing module, with its tools at the left. This is in Mac OS X 10.6 Snow Leopard in 2009.

Today it seems extraordinary that AppleWorks, which shipped for Apple II in 1984, had to wait seven years until 1991 before it could run on the Mac.

❌
❌