I agree, Jim. The potential of Hotknot as mobile payment is there, but yet to be proven. But I believe MTK has a great strategy to proliferate Hotknot as broad as possible first -- and use those handsets as a Trojan Horse to tackle the new mobile payment stuff.
Hotknot works very well where you have two devices with power and capacitive touch screens. However, once you start to include other devices, creditcards, stick-on tags, wrist-bands, etc... that do not have a capactive touch screen or power, then something like NFC works very well.
Yes Notknot and NFC can share the same application of transfering data between two smartphones. Based on the smartphone data share application, we could ask Hotknot vs Bluetooth or Hotknot vs WiFi. However, the technologie's applications start to diverge very quickly outside of the smartphone data share application.
NFC has a lot of potential but people get hung up on things like sending pictures.
NFC tags should be used to put your device in to a mode suitable to it's location, like send incoming calls to voicemail after you enter your car or re-route your calls to VOIP when you are at home and don't want to waste your voice minutes.
"Simple" tasks like that should be easy but it's hard just figuring out which NFC tags are compatible with your phone. Maybe if NFC suppliers want to make it take off they should make sure handsets get bundled with a couple tags.
I could care less about sending tree pictures to another phone, I've got email for that.
The concept seems novel but if they don't make it do anything basicly useful it's just going to be one more thing in the online user's manual that never gets read.
Electronic payments might change the game but as above I would rather use proximity than touch.
Junko, I see the potential security aspect of this as being a key differentiator, especially for electronic transaction. Then combined with the cost and design simplicity, Hotknow has potential. The determining factor is adoption by the financial services industry. Thus far, the industry has been heavily divided. If any of the big players see value and adopt Hotknot, it could displace many NFC applications.
@tb100, I agree. The genius of Hotknot is in the business model. If MTK can leverage its strong presence in touch controller ICs (through Goodix and Mstar), they might be able to proliferate this thing a lot faster -- at least, initially in China.
I assume that the advantage is cost, since you can use the touch interface that is already built into the phone. Power should be less too.
I think you'd have to get a lot closer, though, and the data rate is a lot slower.
Still, if it is practically free to add this to a phone, maybe more phones will have it in the future. One of the problems with NFC is that not every phone has it (especially iPhones, which are a significant portion of the market). It is hard to get traction with a 'swipe to pay' NFC system unless lots of people have a device that can be used.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.