vivo Y17 vs Wiko View3 Pro

Key differences

Calculated from recorded specifications using minimum difference thresholds. These are differences, not an overall ranking. For three phones, numeric highlights compare the two extremes.

• Weight

  View3 Pro: 6.5 g lighter

  Y17:

  190.5 g

  View3 Pro:

  184 g

• Width

  View3 Pro: 1.8 mm narrower

  Y17:

  76.8 mm

  View3 Pro:

  75 mm

• Chipset

  Y17:

  Mediatek MT6765 Helio P35 (12nm)

  View3 Pro:

  Mediatek MT6771 Helio P60 (12 nm)

• Depth

  View3 Pro: 0.8 mm thinner

  Y17:

  8.9 mm

  View3 Pro:

  8.1 mm

Relative size, not calibrated actual size. Front and side outlines share one scale and a bottom baseline. Generic outlines use recorded body dimensions, excluding camera bumps.

1. 1. Y17

   Height:

   159.4 mm

   Width:

   76.8 mm +1.8 mm versus View3 Pro

   Depth:

   8.9 mm +0.8 mm versus View3 Pro

2. 2. View3 Pro

   Height:

   159.5 mm

   Width:

   75 mm

   Depth:

   8.1 mm

Screen size

Approximate rectangular screens calculated from recorded diagonal and aspect ratio at one relative scale. Rounded corners and cutouts are not subtracted. These are not phone outlines or calibrated actual sizes.

At least two phones need compatible screen dimensions for a drawing.

1. 1. Y17

   Y17: Screen geometry unavailable or conflicting.

2. 2. View3 Pro

   Screen diagonal:

   6.3 in

   Aspect ratio (height:width):

   19.5:9

   Approximate rectangular screen area:

   97.4 cm²

Memory variants

Each row compares the same storage capacity. Cells show recorded RAM alternatives, not combined maxima. Not recorded does not mean unavailable in every market.

Practical features

Explicit Yes and No values are shown directly. Qualified or regional records retain their details. Unknown means the record is missing.

Battery capacity

Capacity is not battery life. No endurance test is implied.

Open a section for more detail. On narrow screens, swipe sideways or use Left/Right arrow keys while the table is focused. Unknown means missing data, not No. Recorded zero values are shown as recorded.