Details of Google’s alleged wearable gadget or smartwatch keep appearing every now and then, but everything so far has been a leak, rumor, speculation or pure fantasy. Not now, just till you read the title. If you are not a newbie in the world’s technology platform, you may have heard of the reputation of @evleaks as the leading tipster with the highest rate of confirmations. Today, @evleaks reports that Google is indeed working on a smartwatch, and as it had been rumored earlier this month, it is most likely being manufactured by Google’s Nexus 5 partner, LG.
More Google (LG) smartwatch specs: 1.65" IPS LCD @ 280×280, 512MB RAM, 4GB internal storage, processor TBD.
— Evan Blass (@evleaks) March 13, 2014
The possibility of Google working on their own smartwatch is very high now as even the timing of the release is projected to be during the Google I/O developer conference to be held in San Francisco in June.
According to @evleaks’s tweet today, the Google smartwatch will have a 1.65 inch 280 x 280 pixels resolution LDC display, 512MB of RAM and 4 GB of onboard storage. Unfortunately, there aren’t any more details that would really make us picture where the device will be positioned in the global smartwatch listing including the actual design, the processor, core uses, integration with other devices like the Google Glass and Android smartphones and the battery.
Samsung announced its Galaxy Gear 2 smartwatch with a 1.63 inch 320 x 320 pixels resolution, a 1 GHz dual-core processor and a 300mAh battery that promises up to 3 days of use. Google’s smartwatch has to be better especially in hardware specs to make an entry into a market with over 10 different smartwatches already including Samsung’s, LG’s and Sony’s.
I hope that the floodgates of leaks has just been opened and we will be seeing more of leaks, especially with pictures, of the Google smartwatch since we all secretly hope that the giant company is known for its technological inventions and changes that affect an entire market. For now, this is all we have.
Sources: @evleaks via techcrunch.com