Urgent.News

What's breaking now, across thousands of outlets.

Tech

★ The iPhones 18 Pro

It’s the best version of the most successful product ever made. And yet by nature of *how* the iPhone 18 Pro improved in the last year, it’s not exciting at all.

Every year since 2007, Apple has introduced a new flagship iPhone, with numbers in their names signifying their generation. In this sequence, only the iPhone 4 bears the correct number to its generation, as the "ten" in iPhone X marked 10 years but was the 11th flagship model. The iPhone 18 Pro signifies Apple's 20th iPhone generation, marking 20 years of flagship releases.

The timeline of iPhone releases includes various milestones, such as the introduction of the iPhone 3G in 2008, the iPhone 4 in 2010, and the iPhone 18 Pro in 2026. Apple has consistently released new smartphones annually, although Apple has also launched multiple models with different names each year since the iPhone 11.

The iPhone 18 Pro and Pro Max are likely the flagship iPhones of this generation. Apple first started releasing multiple phones in the same year with the "unapologetically plastic" 5C alongside the 5S. The iPhone X in 2017 marked the first instance of multiple models being launched simultaneously. However, this year, the iPhone Duo appears to be the most exciting new iPhone, potentially taking the spot as the flagship iPhone in future anniversaries.

Written by urgent.news from Daring Fireball's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at daringfireball.net →

More in Tech

A 200 response can still break your API integration

An API can be up, fast, and still break every client that depends on it. A field changes from an object to an array. An optional property disappears. A path is renamed in the OpenAPI document.

  • API responses can change shape without breaking DNS or latency
  • Four types of API changes: availability, shape, contract, and behavior
  • Detailed JSON diffs pinpoint breaking changes for developers

Implementing Degraded Node.js Health Checks for API Credentials and Tiers

A readiness endpoint for a Node.js metering service should report the last verified capability state, not call the account API on every probe.

  • Store last confirmed capability state and cache with short lifespan
  • Refresh account credentials outside main request path
  • Separate liveness, readiness, and capability refresh checks

More from Friday 18 September →