Allview V1 Viper S vs Motorola ZN300

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

  ZN300: 40.5 g lighter

  V1 Viper S:

  143.5 g

  ZN300:

  103 g

• Width

  ZN300: 25.8 mm narrower

  V1 Viper S:

  71.8 mm

  ZN300:

  46 mm

• Depth

  V1 Viper S: 6.1 mm thinner

  V1 Viper S:

  8.9 mm

  ZN300:

  15 mm

• Height

  ZN300: 48.4 mm shorter

  V1 Viper S:

  144 mm

  ZN300:

  95.6 mm

• Release year

  V1 Viper S:

  2014

  ZN300:

  2009

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. V1 Viper S

   Height:

   144 mm +48.4 mm versus ZN300

   Width:

   71.8 mm +25.8 mm versus ZN300

   Depth:

   8.9 mm

2. 2. ZN300

   Height:

   95.6 mm

   Width:

   46 mm

   Depth:

   15 mm +6.1 mm versus V1 Viper S

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. V1 Viper S

   V1 Viper S: Screen geometry unavailable or conflicting.

2. 2. ZN300

   ZN300: Screen geometry unavailable or conflicting.

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.