Apple leaks iPhone 8 design

“You know how Apple is big on secrecy and how it has employed a team of former highly skilled intelligence officers to crush internal leaks?” Chris Smith writes for BGR. “Well, they probably didn’t see this one coming. Someone at Apple accidentally — or intentionally — released the first firmware of Apple’s HomePod smart speaker.”

“Intrepid developers took that firmware apart to find various details about the Siri speaker itself, but also about the next iPhone,” Smith writes. “Because, for some reason, a schematic of the new iPhone form-factor was buried in the software.”

Smith writes, “It’s unclear at this time why the HomePod firmware was released in the wild, but someone’s going to be in a lot of trouble over at Apple these days.”

Read more in the full article here.

MacDailyNews Take: Oops!

Whoever leaked this HomePod firmware, if it wasn’t intentional, isn’t having a fun time at work.

SEE ALSO:
Apple’s HomePod will support VoiceOver, other accessibility features – July 28, 2017

9 Comments

  1. oh silly me, my iPhone 6s still “screws up” (locks up) enough that I have to press the home button a few times a month to stop the offending app from running. (it should be noted that since 2008 none of my iPhones EVER crashed.)

    I’d be hesitant to buy an iPhone without a physical button.

    1. If you’re double-pressing the home button to force quit an app, that’s still a software function and a physical button wouldn’t be required for that as long as it was accounted for in the UI.

      If you’re needing to force restart the iPhone, the other buttons remain (volume up/down and power).

      1. yes, what you are saying makes sense. However, what if an app screws up and takes over the WHOLE screen, without a physical button to get to the list of apps running, then what? A whole “reboot” would suck.

        Is there a way now to stop an errant app from running without pressing the home button?

        1. Since it’s a software function, it doesn’t have to be the home button. It could be any button (volume/power) or screen gesture. If screen gesture, they’d need something that overrides the app’s control of that gesture, but that’s not a problem to implement (especially with what they’re likely to do with the screen).

Add Your Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.