Please pardon this very long Topic Name, but I can edit it as the Topic evolves. And pardon my complete ignorance of the essence of this post – I guess my goal is to become less ignorant, doh!
I’ve been introduced by a friend to the Samsung SAMI Project, and I’m just at the very beginning of getting a feel for what this project and platform is all about. Heck, I didn’t even know what the acronym SAMI stands for (and why it is sometimes written as “SAMIIO”).
SAMI is definitely related to Internet of Things … or is it just a data sharing platform … or just another cloud?
Oh… there’s this:
… ‘SAMI,’ short for Samsung Architecture Multimodal Interactions, and it’s a cloud-based platform capable of reading and storing data from various sensors. It’s compatible with Samsung’s S-Health products, and completely open to developers.
If there are any “SAMI experts” (ummm… probably anybody that’s used SAMI is an expert relative to me at the moment), I’d love to chat. Myself – well, I’ll share more information here as I explore, experiment, and perhaps understand what this is all about.
The SmartThings relevancy…
At first glance, SAMI seems to provide an environment and API that has a lot of functional overlap with the SmartThings Cloud and the SmartThings Web Services API. It is far too early for me to understand or explain the overlap, let alone speculate if the two environments could be reconciled and what sort of value there would be in doing so (technical value and business strategic value).
As an arbitrary example, SAMI has a “Device Simulator”… sound familiar?
Is SmartThings going to integrate with SAMI? Should it? Is this integration optional or could it be mandatory due to SmartThings’s ownership of Samsung? Is SAMI redundant to ST in any way – or, is SAMI completely irrelevant to SmartThings?