InspiredCode

Turns out this might be half true. Wccftech’s sources say a newly redesigned A17 will be coming to the standard iPhone 16, but it will be based on the newer N3E process.

If Google lost their search dominance I think Android would suffer. Google has a very well built house of cards, but if search fails everything else probably fails. Android is too big to die, but a lot of people are tied to Google services on Android and many of those services are sustained by search ad revenue.

Actually it does make sense. Apple will not want to produce the A17 longer than it needs to. The N3B process took some shortcuts and was just a way to start making chips for Apple before they were actually ready for the N3 process node. Next year they will certainly want to see all chips built on the N3E process which is much less expensive.

That probably means an A18 and a A18 Pro. The A18 Pro may have more GPU cores enabled. Apple is setting the stage for this next year by calling this years processor the A17 Pro despite no "plain" A17. If Apple does use the A17 naming for the lower-end iPhone next year it will certainly be an A17 redone for the N3E process. I would not be surprised if we see Apple really go overboard on the A18 GPU to continue with the gaming focus (going head-to-head with the Switch 2 next year) and start working toward a lower cost Vision headset. I think Apple is just getting started with prioritizing AAA class gaming that could take on consoles now that most of the pieces are in place: DirectX compatibility, mesh shaders / next gen shading pipeline, raytracing, upscaling, Game Porting Toolkit, etc. It feels like Apple might want to really hit their stride in AAA gaming 1-2 years from now.

The analysts don’t know anything for these low volume parts. Anything could happen. It is always possible it will ship with the M3 and not need a refresh for several years.

I’m certainly buying one as early as possible in anticipation of it being supply constrained.

Reviews have all been favorable. I’m sure Apple is planning to stick with the product for as long as it takes to become mass market.

Technically TCP/IP is easy to put a man-in-the-middle too, but that is why we build stuff on top of it to make it secure. This is just more difficult for devices because it is harder to protect the client certificates on them. If you can extract the client certificates from an Apple TV then you can pretend to be an Apple TV. This doesn't work for the web because you would need to break in to a data center to pretend to be a web server.

Apple might have a plan to help mitigate these issues with the U1 chip, but it would need to be integrated everywhere. This can help ensure the device is actually really close before accepting a bluetooth connection on a new device. Devices that have already been joined for the first time can use techniques similar to the web to protect their connections. Alternatively NFC could be used for initial connections.