Android Wear Beta

Posted by Hoi Lam, Lead Developer
Advocate, Android Wear

LG Watch Sport

Today, we are launching the beta of the next Android Wear update. As we
mentioned at Google I/O, this will mainly be a technical upgrade to API 26 with
enhancements to background limits and notification channels. LG Watch Sport
users can go to this webpage to sign up and the factory image will automatically be downloaded to the watch you enroll. As this is a beta, please be sure to review the known issues before enrolling. If you don't have a watch to test on, you can use the Android emulator. For
developers working with href="https://developer.android.com/training/wearables/apps/creating-app-china.html">Android
Wear for China, an updated emulator image is also available.

Notification Channels

In this update, users can choose the types of notifications they receive via an
app through href="https://developer.android.com/guide/topics/ui/notifiers/notifications.html#ManageChannels">notification
channels. This gives users finer-grained control than muting all
notifications from the app. For notifications generated locally by Android Wear
apps, users will be able to customise the notifications channel they want to
see, right on their watch. Please refer to href="https://github.com/googlesamples/android-WearNotifications">the Wear
notification sample for more details. For notifications bridged from the
phone, the phone notifications channel settings will dictate what is shown on
the watch.

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
    mNotificationManager.createNotificationChannel(
        NotificationChannel("1001", "New Follower",
            NotificationManager.IMPORTANCE_DEFAULT))

    mNotificationManager.createNotificationChannel(
        NotificationChannel("1002", "Likes",
            NotificationManager.IMPORTANCE_LOW))
}

Background Limits

There are increased restrictions on href="https://developer.android.com/about/versions/oreo/background.html">background
services. Developers should assume services can no longer run in the
background without a visible notification. In addition, the background location
update frequency will be reduced. Battery-saving best practices such as using
href="https://developer.android.com/reference/android/app/job/JobScheduler.html">JobScheduler
should be adopted to ensure your app is battery-efficient and able to perform
background tasks when possible.

Please give us your feedback

We expect this to be the only beta release before the final production release.
Thank you for your feedback so far. Please submit any bugs you find via the href="https://issuetracker.google.com/issues/new?component=192711&template=840908">Android
Wear issue tracker. The earlier you submit them, the higher the likelihood
that we can include the fixes in the final release.

Read more

Updates to Google Play policy promote standalone Android Wear apps

Posted by Hoi Lam, Lead Developer
Advocate, Android Wear

Strava - a standalone wear app available to both Android and iOS users

Android Wear 2.0 represents the the latest evolution of the Android Wear
platform. It introduced the concept of href="https://developer.android.com/training/wearables/apps/standalone-apps.html">standalone
apps that can connect to the network directly and work independently of a
smartphone. This is critical to providing apps not only to our Android users,
but also iOS users - which is increasingly important as we continue to expand
our diverse ecosystem of watches and users. In addition, Wear 2.0 brought
multi-APK support to Wear apps, which reduces the APK size of your phone apps,
and makes it possible for iOS users to experience your Wear apps.

Today, we are announcing that multi-APKs will also work for Android Wear 1.0
watches, so you can now reach all of your users without needing to bundle your
Wear app within your phone app's APK. Additionally, the Google Play Store policy
will change to promote the use of multi-APKs and standalone apps. This covers
all types of apps that are designed to run on the watch, including watch faces,
complication data providers as well as launchable apps.

Policy change

The policy change will be effective from the 18th of January, 2018. At this
time, the following apps will lose the "Enhanced for Android Wear" badge in the
Google Play Store and will not be eligible to be listed in the top charts in the
Play Store for Android Wear:

• Mobile apps that support Wear notification enhancements but do not have a
  separate Wear app.
  
• Wear apps that are bundled with mobile apps instead of using
  multi-APK.

Since multi-APK is now supported by devices running Wear 1.0 and 2.0, developers
embedding their Wear app APKs in phone APKs should unbundle their Wear APK
and href="https://developer.android.com/training/wearables/apps/packaging.html">upload
it to the Play Store as a multi-APK. This will allow them to continue to
qualify for the "Enhanced for Android Wear" badge as well as be eligible to
appear in the Android Wear top charts. The two APKs can continue to share the
same package name.

In addition to providing top app charts, we periodically put together curated
featured collections. To be eligible for selection for these collections,
developers will need to make their Wear apps function independently from the
phone, as a standalone app. These apps will need to work on watches that are
paired with both iOS and Android phones.

What are standalone apps?

href="https://developer.android.com/training/wearables/apps/standalone-apps.html">Standalone
apps are Wear apps that do not require a phone app to run. The app either
does not require network access or can access the network directly without the
phone app - something that is supported by Android Wear 2.0.

To mark your app as standalone, put the following meta-data tag in the
AndroidManifest.xml:

<application>
...
  <meta-data
    android:name="com.google.android.wearable.standalone"
    android:value="true" />
...
</application>

In some rare cases, the user experience may be enhanced by the syncing of data
between the phone and watch. For example, a cycling app can use the watch to
display the current pace, and measure the user's heart rate, while displaying a
map on the phone. In this scenario, we recommend that developers ensure that
their Wear apps function without a phone and treat the phone experience as
optional as far as the Wear apps are concerned. In these cases, a Wear app is
still considered standalone and should be marked as such in its
AndroidManifest.xml file.

Wear what you want

From the beginning, Android Wear has been about wear what you want -- the
styles, watches, and apps you want to wear. This latest policy change lets you
highlight your Android Wear apps, giving users even more choice about what apps
they want on their watches.

Read more

How to improve app design for Wear 2.0

Posted by Steven Tepper, App Quality Consultant, Google Play

href="https://android-developers.googleblog.com/2017/02/AndroidWear2.html">Wear
2.0 launched back in February with added support for new hardware features
in addition to adopting new href="https://www.google.com/design/spec-wear/android-wear/designing-for-watches.html">Material
Design themes,href="https://www.google.com/design/spec-wear/android-wear/designing-for-watches.html">
ghref="https://www.google.com/design/spec-wear/android-wear/designing-for-watches.html">uihref="https://www.google.com/design/spec-wear/android-wear/designing-for-watches.html">dehref="https://www.google.com/design/spec-wear/android-wear/designing-for-watches.html">lihref="https://www.google.com/design/spec-wear/android-wear/designing-for-watches.html">nehref="https://www.google.com/design/spec-wear/android-wear/designing-for-watches.html">s,
and a simpler vertical UI pattern. It also introduces a href="https://developer.android.com/training/wearables/watch-faces/complications.html">complications
API, making it easier for apps to provide data to watch faces, and watch
faces to incorporate external data. The final big update was that, apps
targeting Wear 2.0 now have the ability to operate in a href="https://developer.android.com/training/wearables/apps/standalone-apps.html">standalone
mode, without needing a connection to a companion app on the phone.

There are a few design considerations in relation to navigation, notifications,
the complications API, and the standalone functionality to help you better
optimize for Wear 2.0 devices:

Navigation

1. Use the href="https://developer.android.com/training/wearables/ui/ui-nav-actions.html#create
   a drawer">WearableDrawerLayout navigation drawer for simple and infrequent
   navigation: Simple navigation includes tasks such as accessing app
   settings, switching users or logging out. You can implement
   this on Wear 2.0 to switch between different views or sections of the app via a
   swipe down from the top of the screen, or an action drawer can be set up for
   context-specific actions when swiping up from the bottom of the screen.
   
2. Present a navigation drawer as a single-page drawer to enable users
   to navigate views quickly: A navigation drawer can be presented as
   either a multi-page or single-page drawer. The single-page layout is useful for
   when the user is expected to navigate quickly between 7 or less views of the
   app. Remember that if the app is using a single-page drawer, the iconography
   should be clear and understandable as there will not be any sort of text
   labeling in this layout. If there are more than 7 views to navigate to or the
   views are not easily represented by icons, you should instead use the multi-page
   drawer layout.
   
   
   
   
   
   
   
   
3. Use multiple app launchers if your app has two or three discrete
   functions: For example, if your app supports
   both activity tracking—with various options, actions,
   and views—and historical analysis and management of tracked activities, you can
   use multiple app launchers to handle these tasks. Alternatively, if your app has
   a simple home screen, these features could be placed in line, at the bottom of
   the screen.
   
4. Use peeking at the top of the action drawer to provide quick access
   to the primary action: If there is no primary action associated with
   the view, override the default behavior and force an overflow button to peek
   instead, exposing all actions at the bottom of a view, when tapped.

Ensure that for devices using Wear 2.0, your app takes advantage of these new UI
patterns to provide a consistent user experience. Check out more training
resources for href="https://developer.android.com/training/wearables/ui/ui-nav-actions.html">Wear
Navigation and Actions and the Material Design specifications for href="https://www.google.com/design/spec-wear/components/navigation-drawer.html">Navigation
and href="https://www.google.com/design/spec-wear/components/action-drawer.html">Action
Drawers.

Notifications

Wear 2.0 uses a simpler vertical navigation pattern, removing the horizontal
swiping gesture to present actions for a notification. Notification actions are
now presented as a single primary action (if applicable) at the bottom of a
notification. If there is no primary action, expanding the notification will
present options in a single, vertically scrollable view.

Notifications will work without needing many changes on both 1.x and 2.0
devices, but appear quite different:

When creating apps for Wear 2.0 devices, improve the user experience with
notifications by applying the following best practices:

1. Support expandable notifications: Use href="https://developer.android.com/reference/android/support/v4/app/NotificationCompat.BigTextStyle.html">BigTextStyle
   so that users can see more content on their watch.
   
2. Use the collapsed view of the notification (if applicable):
   Add the primary action for your notification to the collapsed view of the
   notification using setContentIntent(), where appropriate.
   
3. For messaging apps, use the href="https://developer.android.com/training/wearables/notifications/noti-styles.html">MessagingStyle:
   Provide a rich chat app-like experience in the expanded notification using this
   style.
   
4. Update user directions which are specific to Wear 1.0:
   Remove any text guiding users to act on a card by swiping horizontally
   (the Wear 1.x pattern).
   
5. Enhancing notifications to use inline actions: This allows
   users to do things without needing tap to see the expanded notification details.
   Actions for messaging notifications can use several different input methods
   including Smart Reply presets, voice, and keyboard input. Take advantage of
   these features to provide added functionality and delight users.

To learn more about href="https://developer.android.com/training/wearables/notifications/index.html">adding
wearable features to notifications.

Complications

The complications API in Wear 2.0 makes it much easier for watch face developers
and third-party data providers to surface important information users want, at a
glance. Watch faces that support the API can be configured to use any of the
data providers that have been installed on the watch while maintaining complete
control over their appearance. Apps supporting the complication API allow the
app's data to be accessible on any watch faces that support complications. These
complications can be displayed in a variety of forms (short text, icon, ranged
value, long text, small image, and large image) depending on what the data
provider has configured and how much space has been allocated on the watch face.

To ensure that complications fit the overall design of the watch face and
properly handle their data type, when adding complication support we recommend
watch face makers should:

1. Use the href="https://developer.android.com/reference/android/support/wearable/complications/rendering/TextRenderer.html">TextRenderer
   class found in the Wear 2.0 SDK: This allows the text within
   complications to be adjusted to their bounds by shrinking the text, dynamically
   supporting line breaks or ellipsizing strings when they exceed the bounds of a
   text-based complication.
   
2. Use the href="https://developer.android.com/reference/android/support/wearable/complications/rendering/ComplicationDrawable.html">ComplicationDrawable
   class to set the background color, shape, border, and font options for the
   complications: This gives complete control of how the complication is
   rendered to the watch face.
   
3. Design the watch face to provide a way for users to configure or
   adjust complications on the watch face through a settings menu: To
   learn how to construct these settings see the href="https://github.com/googlesamples/android-WatchFace">watch face sample
   on GitHub.
   
4. Use the data provider href="https://github.com/googlesamples/android-WearComplicationProvidersTestSuite">test
   suite app to feed dummy data to the watch face complications: This
   will enable you to verify that all of the complications render properly and have
   fonts formatted for their bounds.
   
5. As a complication data provider, expose relevant data by using the
   href="https://developer.android.com/reference/android/support/wearable/complications/ComplicationProviderService.html">ComplicationProviderService:
   Simply define and configure what types of href="https://developer.android.com/reference/android/support/wearable/complications/ComplicationData.html">ComplicationData
   the app can provide for complications.

Standalone functionality on Wear devices

1. Make sure your app is able to handle itself if there is no companion
   app installed when using the android.hardware.type.watch hardware feature
   flag: Using this feature enables your app to become searchable and
   installable directly on Wear devices without needing to install a companion
   phone app, so ensure your app can handle itself to avoid a confusing or broken
   user experience.
   
2. Ensure your wearable app doesn't rely on the phone app for
   sign-in/authentication or primary functionality: When requiring
   complicated input for authentication (for example, password entry) your wearable
   app can point to the companion phone, but should rely on web UI for
   account/password entry rather than an app.
   
3. Where a companion app must be present on a phone to support your app
   in some other way, the app should use the href="https://developers.google.com/android/reference/com/google/android/gms/wearable/CapabilityApi">CapabilityApi:
   This should be used to properly direct users to the Play Store listing on their
   companion device to install the missing app. Otherwise, the app should function
   on its own, using the Wear built-in Wi-Fi, GPS, or other connectivity functions.
   
   
   
   
   
   
   
   
4. Include wording about any companion app requirements or briefly
   mention how your Wear app should function within the Play Store listing
   description: This will help set expectations and guide users to install
   the correct apps for the best possible experience.
   
5. Incorporate the href="https://developer.android.com/training/wearables/apps/standalone-apps.html">com.google.android.wearable.standalone
   flag in the manifest if your Wearable app can function without any phone
   companion interaction: This flag indicates that the wearable app can be
   installed and will fully function when not paired to an Android or iOS companion
   phone.

Though a lot was covered here, there are additional resources you can use to
ensure that your apps or games are optimized and use the latest patterns and
functionality on Wear. Be sure to href="https://developer.android.com/develop/quality-guidelines/wear-app-quality.html">review
the quality guidelines and check out the developer training documentation to
learn more best practices for href="https://developer.android.com/wear/index.html">wearable app
development and href="https://www.google.com/design/spec-wear/android-wear/introduction.html">wearable
app design in order to build quality apps for Wear.

How useful did you find this blogpost?

href="https://docs.google.com/forms/d/e/1FAIpQLScLTlzFd_aV-3rAdBqO1QxwCsuAcDCIM6fJFXyNcyf7zElVXg/viewform?usp=pp_url&entry.753333049=1%E2%98%85+%E2%80%93+Not+at+all&entry.2056663615&entry.646747778=Wear2.0tips-08/17" style="color:gold;">★
href="https://docs.google.com/forms/d/e/1FAIpQLScLTlzFd_aV-3rAdBqO1QxwCsuAcDCIM6fJFXyNcyf7zElVXg/viewform?usp=pp_url&entry.753333049=2%E2%98%85+%E2%80%93+Not+very&entry.2056663615&entry.646747778=Wear2.0tips-08/17" style="color:gold;">★
href="https://docs.google.com/forms/d/e/1FAIpQLScLTlzFd_aV-3rAdBqO1QxwCsuAcDCIM6fJFXyNcyf7zElVXg/viewform?usp=pp_url&entry.753333049=3%E2%98%85+%E2%80%93+Somewhat&entry.2056663615&entry.646747778=Wear2.0tips-08/17" style="color:gold;">★
href="https://docs.google.com/forms/d/e/1FAIpQLScLTlzFd_aV-3rAdBqO1QxwCsuAcDCIM6fJFXyNcyf7zElVXg/viewform?usp=pp_url&entry.753333049=4%E2%98%85+%E2%80%93+Very&entry.2056663615&entry.646747778=Wear2.0tips-08/17" style="color:gold;">★
href="https://docs.google.com/forms/d/e/1FAIpQLScLTlzFd_aV-3rAdBqO1QxwCsuAcDCIM6fJFXyNcyf7zElVXg/viewform?usp=pp_url&entry.753333049=5%E2%98%85+%E2%80%93+Extremely&entry.2056663615&entry.646747778=Wear2.0tips-08/17" style="color:gold;">★

Read more

Android Wear: New complications tools and watch friendly UI library

Posted by Hoi Lam, Lead Developer Advocate, Android Wear

Android Wear 2.0 gives users more informative watch faces and provides developers with new ways to build useful apps. These new opportunities have been well received by users and developers alike. To help developers take advantage of these new features, we have released a suite of complication API tools, to make it easier for developers to add complication support to their watch faces, and a new Wear UI library, to help developers build watch friendly user interfaces.

New Complications API tools for Watch Face developers

Complications are bite-sized pieces of information displayed directly on the watch face. They can also be great shortcuts into your favorite apps. We introduced the Complications API last year to enable watch faces to receive data from any app that the user selects, and display the data to the user in a way that is stylistically coherent. Today, we are introducing four new tools to make it easier for watch face developers to integrate with the Complications API:

• TextRenderer - Auto-sizes text to fit in bounds defined by watch face makers.


• ComplicationDrawable - A full rendering solution for complications, that handles all the styling for you, and adjusts the layout to fit the space you specify


• Easy watch face settings sample - Adoptable sample code that makes it easier to build complication settings with a rich and usable experience.


• Complication test suite - A sample data provider to help check that your watch face can handle all the combinations of fields that can make up complication data.

It's never been easier to integrate complications into your watch faces.

New Wear UI Library for Wear developers

We have provided Android view components for building watch friendly user interfaces since the launch of Android Wear 1.0. Developers have told us that they would like to see these components open sourced. So, starting at Google I/O, we are open sourcing some components and providing some Android Wear UI components in the Android Support Library. This brings a number of advantages, including more consistent APIs with the rest of the Support Library, more frequent releases, and better responsiveness to developer feedback. We will:

• Migrate Wearable Support classes - Migrate and update Android Wear specific view components, such as WearableRecyclerView, from android.support.wearable.view in Wearable Support to android.support.wear.widget in the Android Support Library. This new package is available as open source. In terms of developer impact, we expect the migration process to be simple, with minor API name changes to bring consistency with the existing Android Support Library.


• Merge some Android Wear functionality to Android - Some Android Wear components have a lot of overlap with Android, e.g. CircledImageView and DelayedConfirmationView. We will merge the Android Wear specific functionality with the Android counterparts under android.support.v4.widget.


• Deprecate outdated user interface patterns - Two user interface patterns are deprecated with Android Wear 2.0: the Card pattern and the Multi-directional layout. As a result, we have deprecated all supporting classes, such as GridViewPager and CardFragment. Please refer to the class reference docs for their replacements.

In the first wave of these changes, we migrated the WearableRecyclerView, BoxInsetLayout and SwipeDismissFrameLayout classes to the new Android Wear UI Library. We expect the migration process to continue during 2017, and developers will have until mid-2018 to migrate to the new UI components. For additional information, see Using the Wear UI Library.

Get started and give us feedback!

To get started with these new tools, simply update the Android Support Library in Android Studio and update your gradle build files to import the new support libraries. In addition to the documentation links above, check out the Google I/O session - Android Wear UI development best practice - where lead engineers for these tools will be on-hand to explain the technical details.

We will continue to update these tools over the next few months, based on your feedback. The sooner we hear from you, the more we can include, so don't be shy! Let us do some of the heavy lifting for your Android Wear apps and watch faces.

Read more

Android Wear 2.0 is here with new hardware features!

Posted by Hoi Lam, Lead Developer Advocate, Android Wear

Today, we are releasing the final SDK for Android Wear 2.0. In this release, we have added support for the new hardware features announced yesterday. If you have not done so already, it really is time to publish your apps so as to not miss the consumer hardware launch tomorrow.

Throughout the developer preview program, you have given us a lot of constructive feedback as well as bug reports. Thank you again!

Android Wear 2.0 recap

Android Wear 2.0 is our biggest update since we launched Wear in 2014, with numerous platform and developer enhancements. Some of the highlights include:

• Material Design for Android Wear - A new system user interface and design guidelines, featuring a darker colour palette, vertical layout and visual components such as the WearableRecyclerView and WearableNavigationDrawer. We have also enhanced notifications on the watch with the new MessagingStyle rich notification style and inline actions.


• Watch Face Complications - Complications are areas of the watch face that display information other than time. Apps can supply data to supported watch faces by creating a ComplicationProviderService, and watch faces can render this data in a style that suits the watch face design.


• Standalone Android Wear apps and iOS support - Apps can now be downloaded directly to Wear devices via an on-watch Google Play Store. In addition, these apps can access the internet directly without relying on phone apps. This means that apps can now run on Android Wear devices that are paired to iOS devices.

New hardware support

The first two watches with Android Wear 2.0 give users more ways to interact with their smartwatches. In the final SDK, we have added API support for physical button locations and rotary input. At present, developers will need the new LG Watch Style or LG Watch Sport to test these new functionalities; however, we are working to add these new hardware features to the emulator. Stay tuned for updates! The SDK also includes a few other final bug fixes, such as support for more than three items in the Wearable Action Drawer.

App review changes

Now that Android Wear 2.0 is live, we'll soon update the Android Wear App Quality review process with two important changes. First, enhancing your phone app notifications for Android Wear will no longer be sufficient for passing the review. Second, it will soon be required that you upload a watch APK that's compatible with Android Wear 2.0. Only apps that pass these criteria will receive badging in Play Store on the phone and be eligible for top charts for Android Wear apps. These changes will ensure a more consistent experience for users and allow us to streamline the review process for you.

The journey doesn't stop here!

The Android Wear 2.0 developer preview lasted longer than we originally planned, but we think that the extra time has paid off in a big way. Thank you once again for your input and patience. You helped us achieve a higher quality bar than we could have achieved on our own.



We have integrated the Android Wear 2.0 Developer Preview documentation into the main Wear developer documentation site and we continue to maintain links to the factory images for the preview devices. For developer related bugs, please continue to file developer bug reports or post comments in our Android Wear Developers community.



From the Android Wear team: Thank you again for your feedback and support!

Read more

Spesifikasi dan Harga Samsung Gear Live, Smartwatch dengan OS Android Wear

Samsung telah telah resmi meluncurkan perangkat Wearable yang dijuluki Samsung Gear Live yang telah tersedia untuk Pre-Order di AS. Perangkat ini diumumkan dalam acara Google I/O bersama dengan SmartWatch lainnya seperti LG G Watch dan Moto 360 yang juga diperkenalkan dalam acara tersebut.

Perangkat yang dapat dipakai pada pergelangan tangan ini akan memberitahukan semua rincian seperti pesan SMS, panggilan dan pemberitahuan lainnya. Anda juga bisa mendapatkan ramalan cuaca dan juga memiliki dukungan Google Now sehingga Anda dapat mencari sesuatu di Google dengan perintah suara.

Samsung telah merilis beberapa smartwatch seperti Galaxy Gear yang awalnya memiliki OS Android, dan yang lainnya smartwatches Gear 2, Gear 2 Neo dan Gear Fit yang menggunakan Sistem operasi Tizen. Samsung juga membuat pesaing Google Glass dengan membuat Gear Blink yang diharapkan akan dirilis akhir tahun ini.

Samsung Gear Live memiliki layar Super AMOLED 1,63 inci dengan resolusi 320 x 320 pixel. Perangkat ini didukung dengan prosesor 1,2 GHz ditambah dengan RAM 512 MB dan memiliki baterai dengan kekuatan 300 mAh. Memori internal pada smartwatch adalah 4 GB dan juga akan menjadi perangkat yang tahan air dan debu seperti kebanyakan smartwatch lainnya. Perangkat ini memiliki bobot 59 gram dan dengan ketebalan 8,9 mm.

Membawa Android ke perangkat yang dapat dipakai adalah langkah yang baik dan untungnya smartwatch Samsung Gear Live tidak hanya terhubung dengan smartphone Samsung, tidak seperti yang sebelumnya, itu berarti setiap perangkat Android akan mendapatkan akses ke smartwatch ini asalkan sudah menjalankan Android 4.3 atau yang lebih baru. Smartwatch ini tersedia untuk pre-order dan dibandrol dengan harga $ 199 di AS, yang akan dikirim pada tanggal 8 Juli.

Read more

Spesifikasi dan Harga LG G Watch, SmartWatch dengan OS Android Wear

Di Google I/O 2014, LG telah mengumumkan bahwa LG G Watch akan mulai dijual di Amerika Serikat mulai bulan Juni. Perangkat ini diumumkan bersamaan dengan smart watch Samsung Gear Live yang juga akan menjalankan OS Android Wear yang akan dijual sekitar $ 199 di Amerika Serikat.

Sekarang, perangkat ini dapat dipesan secara pre-order di Google Play Store di AS dari 25 Juni dan akan dikirim pada Juli 2014. Pre-order smart watch ini hanya tersedia di 12 negara dan kemudian akan tersedia di 27 negara lainnya. Biayanya sekitar $ 229 sebelum pajak dan pengiriman.

Smart watch LG G Watch dapat kompatibel tidak hanya dengan ponsel LG, tetapi juga dengan ponsel Android dengan OS Android v4.3 ke atas. LG G Watch adalah smart watch tahan debu dan tahan air yang telah mendapat sertifikasi IP67 dan bisa tahan hingga 1 meter dibawah permukaan air selama 30 menit seperti sebagian besar perangkat tahan air lainnya.

Untuk spesifikasi perangkat ini, LG G Watch memiliki layar sentuh IPS LCD 1,65 inci dengan resolusi 280 x 280 piksel. Dimensi dari perangkat ini adalah 37,9 x 46,5 x 9,95 mm dan berat sekitar 63 gram. Smart watch ini didukung dengan Chipset Qualcomm Snapdragon 400 dan digabungkan bersama-sama dengan RAM 512 MB. Jam tangan pintar ini memiliki kapasitas memori internal 4 GB yang kemudian dapat ditransfer ke sistem. LG G Watch memiliki pilihan konektivitas seperti Bluetooth v4.0 sehingga dapat dengan mudah dihubungkan dengan ponsel Android. Perangkat ini didukung dengan baterai 400 mAh yang diperkirakan dapat tahan sepanjang hari.

Perangkat ini juga dilengkapi sensor seperti Accelerometer, Heart Rate, Kompas dan giroskop. Perangkat ini akan memberitahukan semua notifikasi yang Anda dapatkan atau Anda terima pada perangkat Android. LG G Watch tersedia dalam pilihan warna White Gold dan Black Titan dan tersedia untuk pre-order di Google Play seharga $ 229.

Read more