What you need to know
- The unannounced Beats Studio Buds have received FCC approval.
- The buds were outed in iOS 14.6 betas and still haven't been officially announced.
The unreleased Beats Studio Buds have received their FCC approval ahead of an announcement that will likely come pretty soon.
The earbuds were first outed by code found in iOS 14.6 betas and now it seems they're more official than ever. The FCC approval was first spotted by MyhealthyApple and it follows 9to5Mac's recent discovery. We expect Studio Buds to function similarly to Apple's own AirPods.
From 9to5Mac's report last week:
Now we keep our eyes and ears peeled for a Beats press release. It's surely just around the corner.
We don't yet know what Beats will charge for these things, but we do know that there are some great AirPods deals to be had. Don't fancy the Beats look? AirPods are here to save the day!
Oliver Haslam has written about Apple and the wider technology business for more than a decade with bylines on How-To Geek, PC Mag, iDownloadBlog, and many more. He has also been published in print for Macworld, including cover stories. At iMore, Oliver is involved in daily news coverage and, not being short of opinions, has been known to 'explain' those thoughts in more detail, too.
Having grown up using PCs and spending far too much money on graphics card and flashy RAM, Oliver switched to the Mac with a G5 iMac and hasn't looked back. Since then he's seen the growth of the smartphone world, backed by iPhone, and new product categories come and go. Current expertise includes iOS, macOS, streaming services, and pretty much anything that has a battery or plugs into a wall. Oliver also covers mobile gaming for iMore, with Apple Arcade a particular focus. He's been gaming since the Atari 2600 days and still struggles to comprehend the fact he can play console quality titles on his pocket computer.
Get the best of iMore in in your inbox, every day!
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.