Home / News / Laptop News / Is the MacBook Pro next in line to lose the headphone jack?

Is the MacBook Pro next in line to lose the headphone jack?

by

2015 13-inch MacBook Pro 5

Although the iPhone 7 wasn't quite the drastic overhaul many were hoping for, there was one big change on this years model: the removal of the headphone jack.

And with news that Samsung could be considering a similar move for its future handsets, and possibly licensing a proprietary port to other manufacturers, it seems we're poised on the precipice of an all-out headphone jack war.

Now, as reported by MacRumours, it seems Apple is moving forward with its 3.5mm killing spree – at least, it's thinking about it.

The company has reportedly been sending out surveys to MacBook Pro users asking about certain features, including whether they use the headphone jack or not.

Related: Best Black Friday deals

MacBook Pro 25

The rumoured 2016 MacBook Pro is thought to feature an OLED strip above the keyboard

Twitter users are also reporting being asked about the 3.5mm port, suggesting future MacBook Pro models could come without the connection.

The headphone jack question specifically reads: "Do you ever use the headphone port on your MacBook Pro with Retina display?"

Other questions on the survey touch on battery life and other connections such as the SD card slot.

Apple is expected to release a refreshed line of MacBook Pros this October, which are widely believed to come with a new OLED strip above the keyboard.

The new MacBook Pro 2016 is also thought to be lighter and thinner than previous models and could come with Touch ID fingerprint scanning.

Of course, it's highly unlikely the rumoured 2016 MacBook Pro will come sans headphone port, but with Apple clearly harbouring a desire to cut the connection out of future devices, there's every chance we'll see a MacBook Pro without the headphone port in years to come.

WATCH: 2015 MacBook Pro 13-inch review

Would you like to see more Apple products without a headphone jack? Let us know in the comments.

comments powered by Disqus