Apple did something with AirPods Pro 3 that I didn't think earbuds could pull off
Briefly

Apple did something with AirPods Pro 3 that I didn't think earbuds could pull off
"Apple has taken what is arguably one of its most iconic and widely acclaimed products -- the AirPods Pro 2 -- and elevated them with a significant upgrade for 2025. Since the product has a simple mission and it didn't appear that there were a ton of things Apple could do to make them better, it's always a risk to make big changes."
"Also: Best AirPods 2025: I've used every pair of Apple headphones and earbuds - these are the winners I've been using them for more than a month since they was first announced in September. And I'm happy -- even a little relieved -- to report that Apple didn't ruin a good thing here. In fact, there's one area where I didn't realize it was even possible to make them better, but they are. Additionally, there are new features that enhance the product's usability."
"But if you've had a pair of AirPods or AirPods Pro in the past and loved them, the good news is there's a great chance you're going to love the AirPods Pro 3 even more. How I tested AirPods Pro 3 I started testing the AirPods Pro 3 on the day they were announced at Apple Park on September 9. I wore them on a five-hour flight home from California to test the sound quality, active noise cancellation (ANC), and battery life."
Apple released the AirPods Pro 3 as a significant 2025 upgrade to the AirPods Pro 2, introducing major changes and new usability features while retaining the original mission. Testing began on announcement day at Apple Park on September 9 and included a five-hour flight to evaluate sound quality, active noise cancellation (ANC), and battery life. Daily comparisons were made with AirPods 4 with Noise Cancellation, Sony WF-1000XM5 earbuds, and Meta Ray-Bans smart glasses. The AirPods Pro 3 improve at least one previously unexpected area and should appeal strongly to previous AirPods and AirPods Pro owners, though a few gaps and blind spots remain.
Read at ZDNET
Unable to calculate read time
[
|
]