AIApple Newsroom
John Ternus Becomes Apple CEO on September 1 — AI Catch-Up Is Job One Ahead of iPhone 18 Event
John Ternus, 51, assumed the role of Apple CEO on September 1, 2026, with Tim Cook transitioning to Executive Chairman of the Board. Ternus joined Apple in 2001 and has led hardware engineering since 2021. His first public test as CEO is the fall product event on September 9 — codenamed 'Surprise and Shine' — expected to unveil the iPhone 18 Pro, the company's first foldable iPhone, and Apple Watch Series 12.
Context
Apple announced the succession in April 2026 and managed a deliberate handover through the summer. Ternus inherits a significant AI gap: Apple has faced sustained criticism for the slow rollout of Apple Intelligence features and Siri's lag behind competing assistants. The company's AI division has already seen leadership changes. An engineering-centric CEO is expected to accelerate hardware-software integration, though analysts have raised questions about whether leading a large-scale AI strategy shift requires a different skill set.
HaLVision's take
For web studios and SMBs, the most relevant near-term signal is what Apple announces on September 9 regarding Apple Intelligence capabilities and on-device AI. If Siri's rumored rebuild delivers meaningfully better voice and local search responses, that could shift how iOS users discover local businesses — a relevant consideration for any client running a local search strategy. Longer term, a hardware-first CEO may prioritize AI features tied to device capabilities over purely cloud-dependent approaches.
Read source ↗Web9to5Linux
Firefox 155 Ships Today as First Biweekly Release — Chrome Joins the Two-Week Cycle on September 8
Mozilla released Firefox 155 on September 1, the first update under the browser's new two-week release cadence announced in July. Key additions include Happy Eyeballs v3 for faster connection setup, WebRTC interoperability improvements, a CSS nesting depth limit of 75 levels to prevent crashes, and the ability to reorder containers in Settings. Chrome is on the same trajectory: Chrome 153, due September 8, will be the first Chrome release under an equivalent biweekly schedule.
Context
Both major browsers are transitioning from roughly four-week to two-week release cycles starting this month. Mozilla's stated goal is to get bug fixes and finished features to users sooner while making the release schedule more predictable. For web developers, biweekly cadence means new capabilities and fixes arrive faster, but compatibility checks and regression testing need to happen more frequently. Individual releases are expected to be smaller in scope, which limits the blast radius of any single update.
HaLVision's take
For agencies and in-house dev teams managing multiple sites, the practical change is doubling the frequency of browser release monitoring. Automated cross-browser regression tests become more valuable: any site relying on newer CSS or web API features will see both benefits and risks at double the rate. If your maintenance SLAs reference a browser update cycle, now is a good time to revisit those terms.
Read source ↗AIEU AI Act Enforcement Tracker
EU AI Office Issues First Formal Information Requests to Frontier AI Providers — Four Weeks After Enforcement Began
On August 29, the EU AI Office sent its first formal requests for information to providers of general-purpose AI models across multiple regions. EU Commission Executive Vice-President Henna Virkkunen confirmed the action. Recipients reportedly include OpenAI, Anthropic, and Google. The requests cover model security, independent external evaluations, and post-market monitoring practices. The GPAI provisions of the EU AI Act became enforceable on August 2, meaning the Office acted within four weeks of gaining its powers.
Context
The EU AI Act's General-Purpose AI rules came into force on August 2, 2026. The four-week turnaround on these information requests signals that the European Commission intends to use its new enforcement powers actively, not as a paper exercise. Requests for information are not penalties; they are the investigative step that can precede one. Non-compliant responses or refusals can escalate to formal proceedings, with fines of up to 3% of global annual turnover available. The quick action and breadth of targeted companies suggest a systemic review of how frontier labs are operating, rather than a response to a specific incident.
HaLVision's take
Any web service deploying AI chatbots or interactive AI features that serves EU users is now operating in a regulated environment. The immediate practical note: ensure your AI-powered features include clear user-facing disclosure — under the EU AI Act, any interactive AI system must identify itself as AI at the outset of an interaction. For clients expanding into European markets, build compliance checkpoints — disclosure, logging, incident monitoring — into project scopes from the start rather than retrofitting later.
Read source ↗WebGoogle Blog
Google AI Max for Search Is Now Live — Auto-Migration Complete, Focus Shifts to Performance Monitoring
September 1 marks the effective date of Google's AI Max for Search auto-migration. Search campaigns that were running campaign-level broad match or Automatically Created Assets without manual opt-out are now enrolled in AI Max. Dynamic Search Ads migration remains scheduled for February 2027. For advertisers who took no action before the deadline, AI Max settings are active as of today.
Context
AI Max for Search is Google's consolidated automation layer combining automated ad copy generation, landing page selection, and query expansion under a single setting. With the migration now complete, the immediate task shifts from deciding whether to opt out to monitoring what AI Max is actually doing to each campaign. Early performance signals — changes in impression share, search term distribution, click-through rate, and cost per conversion — will start surfacing in dashboards within days. Fully reversing the migration is not straightforward once applied.
HaLVision's take
For agencies and in-house managers: pull this week's Search Terms report and compare impression volumes and CPCs against last week's baseline. Pay close attention to any spike in impressions from expanded match queries, especially for brand-sensitive or geographically restricted campaigns. If AI Max is surfacing clearly irrelevant queries, add negatives immediately — do not wait for monthly optimization cycles. Clients who were manually managing broad match settings carefully will see the biggest divergence and need the most attention over the coming days.
Read source ↗