Vik

Logitech Targets Home Automation Play with Harmony Living Home Lineup
  • Comments are Closed

Logitech Targets Home Automation Play with Harmony Living Home Lineup

Home Automation and Control – Setting the Stage

The increasing popularity of home automation (HA) equipment has fueled the Internet of Things (IoT) revolution. However, the low barrier to entry (there are innumerable crowdfunded projects in this space) has resulted in a very fragmented ecosystem. Interoperability is a major concern, and different devices use different protocols. In order to get a seamless experience across all home automation equipment, consumers have been forced to go the custom installation or integrated package route. These avenues tend to keep the joys of home automation and control out of reach of the average consumer.

The current market situation is ripe for someone to come in with a home automation gateway. Vendors such as Lowes (with the Iris product line) and Staples (with the Staples Connect initiative) have made interesting forays. However, the primary aim has been to sell more connected peripherals under the same brand. Interoperability with other HA devices is not given any importance.

On the other side, we have vendors such as Securifi trying to integrate a home automation gateway into a standard wireless router with their Almond+ product. All things considered, it would be best if the wireless router at home were to act as a home automation gateway. Consumers don’t need to buy yet another device to act as a gateway purely for their IoT clients. The problems would then be making sure that various HA devices can talk to the gateway and consumers have the ability to interact with all of them using one interface. Unfortunately, these aspects have contributed to Securifi delaying the retail launch of the Almond+. Under these circumstances, the slot is still open for a unified home automation controller. Logitech is hoping to fill that void with today’s Harmony Living Home launch.

Logitech Harmony – A Brief Background

Logitech’s Harmony lineup is very well respected in the universal remote control market. The ability of a single remote / hub device to control multiple home entertainment devices (AVR / TV / media players) coupled with one-touch control and simple setup has been well-received by the consumers. In fact, Harmony’s database of over 200K devices (which is also frequently updated) is unparalleled in the industry. The only downside of the units is the pricing aspect.

Prior to today’s launch, the scope of the Harmony lineup didn’t go beyond control of entertainment devices in the living room. However, the current popularity of home automation devices and the IoT ecosystem (coupled with the rapid rise of mobile devices that enable easy control via apps) make the next stop for the Harmony lineup quite obvious. Logitech is launching four new product SKUs centered around a home automation gateway hub under the Harmony Living Home category:

  • Logitech Harmony Home Hub
  • Logitech Harmony Home Control
  • Logitech Harmony Ultimate Home
  • Logitech Harmony Hub Extender

Logitech Harmony Living Home Lineup – Delving Deeper

The Logitech Harmony Home Hub connects to the home network and uses RF, IR, Bluetooth and Wi-Fi to relay commands from the Harmony mobile app or the Harmony remote to all supported entertainment and automation devices. The Harmony mobile apps can work over the Internet. True remote control of the various devices in one’s home from anywhere on the Internet is now possible.

Logitech Harmony Home Hub and Mobile App

Consumers can purchase the hub alone for $100 and use the full functionality with just the mobile app. As with any home automation setup, scenes can be programmed involving multiple devices from different vendors. Logitech terms these scenes as experiences.

The next ‘upgrade’ in the Living Home lineup is the Logitech Harmony Home Control that costs $150. This kit bundles a button-only remote with the hub described above.

Logitech Harmony Home Control and Mobile App

The remote communicates via RF, enabling the hub to be placed in a closed cabinet (if necessary). The mobile apps are obviously compatible with the hub even when the physical remote is being used. This configuration can control any number of home automation devices, but only up to eight entertainment devices.

The highest end configuration is the Logitech Harmony Ultimate Home. It is quite similar to the Harmony Home Control, except for a few updates to the remote control itself: a 2.4″ clour touchscreen, gesture control and additional programmability.

Logitech Harmony Ultimate Home and Mobile App

The kit including the hub and the touchscreen remote will retail for $350. This configuration can control up to fifteen entertainment devices and virtually unlimited number of home automation devices.

In addition to the above three configurations (which will be available for purchase this month), Logitech will also be introducing the Logitech Harmony Hub Extender in December for $130. This extender will expand compatibility by allowing the hub to talk to devices that communicate using ZigBee or Z-Wave. Logitech also stressed the fact that the extender will be Thread-compatible.

Concluding Remarks

The Living Home lineup is a welcome addition to the home automation market. However, Logitech faces a few challenges. There are also a few questionable decisions that have been made with respect to the operating details.

1. Entertainment device manufacturers have typically adopted a hands-off approach after selling their wares to the consumers. As such, they don’t have any issues sharing methods to control their equipment with Logitech. On the other hand, many of the IoT / home automation device makers treat their customers as recurring revenue sources by adopting subscription models. Some of them also want to tightly control the customer experience within a walled ecosystem. Under these circumstances, it is not clear how willing they would be to share their APIs with Logitech or work to make their products compatible with the Harmony platform. That said, Logitech says more than 6000 home automation devices are currently compatible with the hub, and the number is expected to keep growing.

2. Logitech is not adopting a subscription fee model for the Living Home lineup. While this is excellent news for consumers, it would be interesting to see what keeps the cloud servers for the external control aspect running in the future. It might not be a big deal for a company of Logitech’s size, but it leads to another aspect – decentralized control.

3. Based on the initial information provided to us, it looks like the Logitech Living Home lineup requires the hub to be always connected to the Internet for it to control the connected devices. This makes sense for devices that currently offer cloud-based control only. But, we are at a loss to understand why devices that can be controlled via the local network itself (such as, say, the UFO Power Center from Visible Energy and the Ubiquiti mFi mPower strips) need an Internet connection when accessed through the hub while being part of the local network. In our opinion, the control logic (i.e, processing the APIs that talk to the various devices) should be resident on the hub rather than on the cloud.

4. It is not clear whether it is possible for third-party apps to talk to the hubs. Logitech does have a developer program for device makers to make their products compatible with the Harmony home hub. While Logitech indicated that the products being launched today can talk to the recently SmartThings and PEQ hubs, the availability of APIs for the Logitech hub itself remains an open question.

In conclusion, the launch of the Harmony Living Home lineup looks to be just what the home automation market needs. If Logitech can replicate their success with home entertainment control in this space, it solves a very important problem for the consumers and will allow consumers to invest in home automation without the risk of a fragmented experience. A reputable and reliable company had to get serious about this space, and we believe Logitech has the right play here.

Testing Swiftkey for iOS 8
  • Comments are Closed

Testing Swiftkey for iOS 8

Earlier this week SwiftKey announced that they hope to have their keyboard available on the App Store when iOS 8 finally rolls out to users worldwide. They’ve been kind enough to provide us with a beta version of the SwiftKey keyboard for testing, along with some insight into developing extensions on iOS 8 and their hopes for SwiftKey’s future on both iOS and Android.

Assuming that nothing delays Apple’s approval for the app, the first step for users who want to get SwiftKey after upgrading to iOS 8 will be to download it from the App Store. Due to the nature of Apple’s implementation of extensions, even applications on iOS 8 that are essentially just extensions meant to run in other apps must have a container application that gets placed on the home screen. In the case of SwiftKey this is fine, as the application is home to settings for SwiftKey Cloud, languages, settings, and themes.

Once you’ve installed SwiftKey from the App Store, you’ll need to go into the settings app to add it as shown in the image above. With the app installed the SwiftKey keyboard would show up in the section to add a new keyboard under a header for third party keyboards. Once you’ve done this you’ll be ready to start using SwiftKey. However, you may notice that there’s one very important thing missing.

Swiftkey immediately after installation on an iPad

As you can see above, the bar for predictions is covered by a banner asking the user to enable “full access.” This is because of the sandboxing that Apple does for third party keyboards on iOS. Third party keyboards are, by default, placed in an extremely restrictive sandbox. They are unable to get information about what words are being inputted or what content is in an app, and they are unable to access networking to do server side prediction. These measures are in place to protect the user’s privacy and security. To enable extended functionality, Apple allows users to enable full access for third party keyboards in the settings app. By doing this, SwiftKey is able to grab what characters are being typed to use with their prediction and correction technology which learns more about how a user types and what mistakes they make.

As far as the design of the keyboard goes, its layout is essentially same as the stock iOS keyboard so there’s no real learning curve. Users who are familiar with the iOS keyboard can start using SwiftKey and feel at home right off the bat. iPad users will notice that the keys are larger than the stock keyboard, which in my experience made keys easier to hit without causing me to hit the wrong key due to the reduced amount of space between them. In addition to its accuracy, it’s also extremely responsive. iOS 8 on the third generation iPad I was using for testing has an enormous delay between when you touch a key and when it actually registers. SwiftKey has no such issue, and for that reason alone it has become my daily keyboard on iPad. As for its appearance, the keyboard currently only comes with the nickel dark and nickel light themes that you see above. 

Swiftkey’s application, much like the keyboard itself, fits in very well with the visual style and design conventions of iOS. It’s obvious that some care has been put into making it more than a port of the Android version of SwiftKey. The application is home to all the settings for the keyboard, including themes, languages, and SwiftKey Cloud. Currently not all the settings from the Android version have been brought over. Layout options and themes are two notable omissions. However, this is a first release, and I’ve been told that there will definitely be updates as time goes on.

With iOS including Apple’s QuickType keyboard with similar correction and suggestion functionality, some users may be wondering why they even need a third party keyboard like SwiftKey. For me the most obvious reason is SwiftKey Cloud. My current setup is an HTC One (M7) and an iPad. Using SwiftKey on my phone but the stock iOS keyboard on the iPad would mean that the information each keyboard learns about how I type would not available to both keyboards. With SwiftKey on iOS and SwiftKey Cloud, all the information Swiftkey has collected about how I type and what mistakes I often make are available to both of my devices. This is a huge advantage for people who have mobile devices running multiple operating systems.

Another advantage that can be argued is that SwiftKey is a company that has had their keyboard available for 4 years, and specializes only in keyboards. It’s not unreasonable to think that SwiftKey’s technology for learning from how the user types may be more mature than Apple’s which is just now being introduced with iOS 8.

The last advantage simply comes down to features. SwiftKey, and other third party keyboards, can always offer more features than Apple does due to their focus only on keyboards and the ability to ship updates whenever necessary via the App Store. One notable feature that SwiftKey offers is Flow, which is a method of typing by moving your finger from key to key. Users who use Swype by Nuance will be familiar with how SwiftKey Flow works. Unfortunately, I was unable to test Flow as the iPad version of the keyboard does not have it. This is due to memory limitations imposed on extensions. The functionality and visual effects for SwiftKey Flow when run on an iPad exceeds this amount of RAM which is why only the version for iPhone and iPod Touch includes it. Flow is most useful in a one handed situation on a phone so I’m not heartbroken by its omission in the iPad version. That being said, I am still hopeful that SwiftKey will be able to do further optimization to eventually bring Flow to iPad.

Overall, I’m very happy with how SwiftKey has turned out on iOS 8. The SwiftKey Note application makes it clear that the company has wanted to bring their keyboard to iOS for some time now and has just been blocked by the lack of third party keyboard support. The fact that it fixes the keyboard lag on my iPad and syncronizes what it has learned across iOS and Android are enough to make me very happy to use SwiftKey on iOS. I’m very excited to see what future updates bring.

SwiftKey should be available for free on the App Store not long after the release of iOS 8. The application is subject to Apple’s approval, and so there could be some delay in its availability to users.

Update: SwiftKey is approved and available on the App Store now. Grab it here.

Testing Swiftkey for iOS 8
  • Comments are Closed

Testing Swiftkey for iOS 8

Earlier this week SwiftKey announced that they hope to have their keyboard available on the App Store when iOS 8 finally rolls out to users worldwide. They’ve been kind enough to provide us with a beta version of the SwiftKey keyboard for testing, along with some insight into developing extensions on iOS 8 and their hopes for SwiftKey’s future on both iOS and Android.

Assuming that nothing delays Apple’s approval for the app, the first step for users who want to get SwiftKey after upgrading to iOS 8 will be to download it from the App Store. Due to the nature of Apple’s implementation of extensions, even applications on iOS 8 that are essentially just extensions meant to run in other apps must have a container application that gets placed on the home screen. In the case of SwiftKey this is fine, as the application is home to settings for SwiftKey Cloud, languages, settings, and themes.

Once you’ve installed SwiftKey from the App Store, you’ll need to go into the settings app to add it as shown in the image above. With the app installed the SwiftKey keyboard would show up in the section to add a new keyboard under a header for third party keyboards. Once you’ve done this you’ll be ready to start using SwiftKey. However, you may notice that there’s one very important thing missing.

Swiftkey immediately after installation on an iPad

As you can see above, the bar for predictions is covered by a banner asking the user to enable “full access.” This is because of the sandboxing that Apple does for third party keyboards on iOS. Third party keyboards are, by default, placed in an extremely restrictive sandbox. They are unable to get information about what words are being inputted or what content is in an app, and they are unable to access networking to do server side prediction. These measures are in place to protect the user’s privacy and security. To enable extended functionality, Apple allows users to enable full access for third party keyboards in the settings app. By doing this, SwiftKey is able to grab what characters are being typed to use with their prediction and correction technology which learns more about how a user types and what mistakes they make.

As far as the design of the keyboard goes, its layout is essentially same as the stock iOS keyboard so there’s no real learning curve. Users who are familiar with the iOS keyboard can start using SwiftKey and feel at home right off the bat. iPad users will notice that the keys are larger than the stock keyboard, which in my experience made keys easier to hit without causing me to hit the wrong key due to the reduced amount of space between them. In addition to its accuracy, it’s also extremely responsive. iOS 8 on the third generation iPad I was using for testing has an enormous delay between when you touch a key and when it actually registers. SwiftKey has no such issue, and for that reason alone it has become my daily keyboard on iPad. As for its appearance, the keyboard currently only comes with the nickel dark and nickel light themes that you see above. 

Swiftkey’s application, much like the keyboard itself, fits in very well with the visual style and design conventions of iOS. It’s obvious that some care has been put into making it more than a port of the Android version of SwiftKey. The application is home to all the settings for the keyboard, including themes, languages, and SwiftKey Cloud. Currently not all the settings from the Android version have been brought over. Layout options and themes are two notable omissions. However, this is a first release, and I’ve been told that there will definitely be updates as time goes on.

With iOS including Apple’s QuickType keyboard with similar correction and suggestion functionality, some users may be wondering why they even need a third party keyboard like SwiftKey. For me the most obvious reason is SwiftKey Cloud. My current setup is an HTC One (M7) and an iPad. Using SwiftKey on my phone but the stock iOS keyboard on the iPad would mean that the information each keyboard learns about how I type would not available to both keyboards. With SwiftKey on iOS and SwiftKey Cloud, all the information Swiftkey has collected about how I type and what mistakes I often make are available to both of my devices. This is a huge advantage for people who have mobile devices running multiple operating systems.

Another advantage that can be argued is that SwiftKey is a company that has had their keyboard available for 4 years, and specializes only in keyboards. It’s not unreasonable to think that SwiftKey’s technology for learning from how the user types may be more mature than Apple’s which is just now being introduced with iOS 8.

The last advantage simply comes down to features. SwiftKey, and other third party keyboards, can always offer more features than Apple does due to their focus only on keyboards and the ability to ship updates whenever necessary via the App Store. One notable feature that SwiftKey offers is Flow, which is a method of typing by moving your finger from key to key. Users who use Swype by Nuance will be familiar with how SwiftKey Flow works. Unfortunately, I was unable to test Flow as the iPad version of the keyboard does not have it. This is due to memory limitations imposed on extensions. The functionality and visual effects for SwiftKey Flow when run on an iPad exceeds this amount of RAM which is why only the version for iPhone and iPod Touch includes it. Flow is most useful in a one handed situation on a phone so I’m not heartbroken by its omission in the iPad version. That being said, I am still hopeful that SwiftKey will be able to do further optimization to eventually bring Flow to iPad.

Overall, I’m very happy with how SwiftKey has turned out on iOS 8. The SwiftKey Note application makes it clear that the company has wanted to bring their keyboard to iOS for some time now and has just been blocked by the lack of third party keyboard support. The fact that it fixes the keyboard lag on my iPad and syncronizes what it has learned across iOS and Android are enough to make me very happy to use SwiftKey on iOS. I’m very excited to see what future updates bring.

SwiftKey should be available for free on the App Store not long after the release of iOS 8. The application is subject to Apple’s approval, and so there could be some delay in its availability to users.

Update: SwiftKey is approved and available on the App Store now. Grab it here.