first_imgAhead of its June 9 launch, there are more leaks around the Moto Z. According to a few images shared by HelloMoto HK on its Facebook page, the Moto Z will not only have a modular design but will also offer plenty of customization options to users through swappable back covers.Although for now it is not clear if the back cover will be entirely replaceable or not. We suspect it won’t because the Moto Z will most likely sport an metal unibody design. However, with help of plastic or leather shells, Motorola may offer consumers option to give a slightly colourful look to their Moto Z phone.The Moto Z, which is going to be the flagship Motorola phone, is likely to be launched on June 9 at Lenovo’s Tech World in San Francisco. Lenovo currently owns Motorola and is in the process of integrating the Moto division into its main phone business.Also Read: Motorola Moto Z leaks in full glory, launch on June 9 As per the information leaked so far, Motorola will launch the Moto Z in two variants. These are codenamed Vertex and Vector. The  Vertex is likely to be the mainstream variant with Snapdragon 625 and the 1080p screen.The Vector will be the high-end version with an extremely thin design, Snapdragon 820 processor and 1440p screen.Both phones will support the modular design. Motorola will sell “Moto modules” along with the Moto Z. These modules will connect to the phone using the pins on the back cover and will enhance the functionality of the device. For example, the camera module will probably add better controls and the possibly a better lens, helping make the Moto Z feel like a compact point-and-shoot camera.advertisementAlso Read: Bye bye Moto X, enter Moto Z: Motorola may rebrand flagship phones on June 9This is not the first time we are seeing a modular phone. Earlier at the MWC, LG had launched the G5, which also sports a modular design. However, Motorola’s modular solution seems to be somewhat more elegant. The G5 needs to be switched off while changing the modules. But it looks like with Motorola’s solution, something like this would be avoided.last_img