Wesley Hilliard
Apple has reportedly abandoned adding solid-state buttons to the iPhone 15 Pro due to production issues.
Multiple reliable sources suggested that the mute switch, volume, and power buttons would be replaced by solid-state components in the iPhone 15 Pro models. This controversial change would improve device watertight integrity and add new gestures.
However, a new report from Ming-Chi Kuo states that Apple has abandoned the solid-state buttons due to technical issues. This change comes during the EVT development stage, which gives the company time to make final hardware decisions like this.
Since Apple will revert the design to its physical buttons, this should reduce complexity and simplify development, according to Kuo. The last-minute change will have a limited impact on mass production or shipping schedules.
This report arrived only moments after Jeff Pu, an analyst at Hong Kong-based investment firm Haitong International Securities, made a similar declaration. It seems likely that the solid-state buttons were indeed planned but won't be implemented now.
Apple is expected to announce the iPhone 15 Pro during an event in September 2023. It could feature a rounded titanium frame with a new periscope telephoto lens.
Malcolm Owen
Andrew Orr
William Gallagher
Sponsored Content
Christine McKee
Thomas Sibilly
13 Comments
Here’s another rumour
Because Apple had been thinking of going with solid state buttons, Samsung definitely will have them on their next models. They won’t work worth a d**n but Samsung can say “First!”
Thank goodness!
Using tried and true button tech will better ensure iPhone 15 is a very solid performer!
Unintended registration will be a fundamental design flaw of solid state buttons on a handheld device as I mentioned weeks ago. If true, this is the best news possible.
Good news. If Apple would now just move the right button a little higher to prevent even further accidental clicks. That’s a problem for me since years.
I wonder if this is a result of internal user prototype feedback. I can think of several reasons why this wouldn’t be desirable, and it doesn’t seem to really solve any significant problem from a user perspective. Seems like a classic example of “if it ain’t broke…”
Or maybe it was just fake info planted to root out a leaker.