Google Pixel 7 Pro renders show off a similar Pixel 6 series look

Google is known to have difficulty in keeping its unreleased product details under wrap. So as is traditionally the case, the renders of its forthcoming flagship have already been leaked. The drop comes from OnLeaks via Smartprix.com and it strips down all there’s to see about the upcoming Pixel 7 Pro. The phone seems to be sharing a similar design language as its precursor. That means a slightly curved fascia with a central punch hole camera and a triple rear camera setup. Yes, it continues the visor-like appearance at the back, although the protrusion looks a bit flatter. 

Here’s everything we have learned about the device so far:

Google Pixel 7 Pro Design, Specs, and Features (Expected)

The Pixel 7 Pro will reportedly come with a 6.7 to 6.8-inch curved OLED screen on the front with a punch-hole cutout for the selfie camera. The bezels look rather slim. And even though this has rounded edges, the regular Pixel 7 could have a flat-screen like its antecedent.

Google Pixel 7 Pro renders | Image Source: OnLeaks

Coming to the backside, there, you get to see a familiar visor-like camera housing with three cameras (probably of the same kinds as before). Yes, it borrows the design cues from the Pixel 6 lineup but there seems to be a smattering difference if you look closer. That is here in this renders, the camera hump looks fading into the frame and it isn’t that jutting out either. 

One other tiny difference is the missing plastic strip housing the mmWave antenna which it looks like is being switched with a mmWave window flanking by the side frame.

Rest, it is said to have a USB-C port, dual stereo speaker setup, a SIM card tray,  and physical dimensions of 163×76.6×8.7mm.

That’s all for now. We will keep you posted on the new updates about Google’s Pixel 7 lineup. So, stay tuned.

And for more news, feature stories, buying guides, reviews, and everything else tech-related, keep reading Digit.in.



from Mobile Phones News https://ift.tt/sJhEQ02
via IFTTT

0 Comments