Apple's Next iPhone: Facial-Recognition, All-Screen Design (theguardian.com)
Apple may have just revealed the features you could expect in the next iPhone. Last week, the company released the firmware of the HomePod, a smart speaker which it will begin selling later this year. In the code, the company has accidentally spilled some features about at least one of the iPhone models. Developer Steve Troughton-Smith looked at the code to find that the next iPhone is going to feature facial recognition and a brand new "bezel-less" design. From a report: The near bezel-less design has long been expected, with leaks and rumours suggesting that Apple was following Samsung's design moves with the Galaxy S8 and producing a smartphone that resembles Android-creator Andy Rubin's upcoming Essential phone. Apple is not the first company to use IR-based face recognition as a means of unlocking devices and authenticating users. Microsoft's Windows Hello IR-based face recognition is found in its Surface line as well as Windows 10 computers from other manufacturers.
I bought my removable battery from Anker, and I take it (and its short tethering cable) along with me on my 1% of excursions that aren't near an electrical outlet. My removable battery is so clever that it can also charge my watch, tablet, and my buddy's Android. It also has the amazing design characteristic of adding zero additional hardware to my phone in the 99% of trips when I don't want or need it. How cool is that!
I'm meh on the headphone socket. Yeah, it was nice. But yeah, I prefer Bluetooth audio so that my headphone wires don't get snagged on the bus I'm trying to deboard. There's also the significant headphone jack problem that there's absolutely zero standardization for circuits more complicated than left audio / right audio. Every company that supports extra stuff like mics or volume buttons has come up with their own way of doing things. In the PC world, this manifests in my gaming rig's headphone + mic not working with our Xbox. Yay standards! At least Bluetooth has this stuff written into the core protocol instead of everyone going a different path, so we have at least some chance of Company A's widget being compatible with Company B's.
Dewey, what part of this looks like authorities should be involved?