Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/dailynet/public_html/wp-content/plugins/elementor-pro/modules/loop-builder/module.php on line 200

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Google announces Android Wear – LG G Watch and Moto 360 first in line - The Daily Net

android-wear

Google has just announced Android Wear, a platform that will standardize Android on wearable devices. Android watches (and wearables) are kind of a mess right now. There is no consistency and the OS is usually modified in odd ways. Android Wear aims to fix this issue by becoming the common foundation across all Android wearables.

Google SVP of Chrome, Android and Apps Sundar Pichai touched on this topic at SXSW. He stated that Google would release an SDK that would set a standard for Android wearable devices. Today’s announcement only covers smartwatches, but we know Google aims to expand Android Wear to other wearable devices.

We usually don’t cover Android news that are not related to Chrome somehow, but there is an obvious connection between Android Wear and Chrome. Because both platforms are made by Google, we can expect services in Android Wear to be deeply integrated to Google’s other services.

Chrome and Android share many common services. We know you will be able to access Google Now and Hangouts through Android Wear, for example. These are also deeply integrated into Chrome and Chrome OS, and we are sure we will see more examples of Chrome and Android Wear working together.

Android Wear SDK preview now available for developers

Of course, this effort can’t become a success without the help of our beloved developers. Google has also released an Android Wear SDK preview, which will help developers start optimizing their apps for Android Wear smartwatches.

Get the Android Wear SDK preview here

Android Wear devices

So we know how Android Wear will work and what its main purpose is. That is awesome and all, but what we really want to see are the devices! Google is currently working with a very healthy list of manufacturers to bring Android Wear devices to the market.

Asus, HTC, LG, Motorola, Samsung, Broadcom, Imagination, Intel, Mediatek, Qualcomm and fashion brands like the Fossil Group are already planning to get some devices out later this year. In fact, LG and Motorola have already announced their very own!

LG G Watch and Moto 360

LG and Motorola are the first to come out and give us a glimpse of their own Android Wear Smartwatches. The manufacturers have just announced the LG G Watch and the Moto 360, two devices that are looking very promising.

I have to say I happen to really like Motorola’s design. It resembles traditional watches more closely, and it looks like the build quality and design are very well thought out. The circular design also makes it very unique compared to other smartwatches.

This is not saying LG is falling behind, though. The LG G Watch does look very sleek and elegant. It’s just that Motorola seems to have put deeper thought into its smartwatch’s design. This is something you can see in the results, as well as in the video below.

Release dates

Specs and other details will be announced later. We do have some estimated release dates, though. The LG G Watch will be available during Q2 of 2014, which is actually very soon. Meanwhile, Motorola will bring the Moto 360 with different designs by the summer.

What do you think?

I am very excited to see Android Wear coming to fruition. Android wearables are a complete mess right now. We needed some form of official support or guidance from Google, and I believe this is the first step for a great future with Android wearables.

For now, I have my eye on that Moto 360. It looks gorgeous! I am hoping another manufacturer will use e-ink, mirasol or some form of energy efficient screen technology. I don’t like the idea of a smartwatch dying on me every single day.

Which one do you like? Will you get one of these, or wait for a better Android Wear device to be announced?

[Google, LG, Motorola]