Here are a couple of recommendations to IoT designers. First, while it is nice to have your product be as beneficial as possible to the customer and adding more features to accomplish that is generally a good idea. If this poses a lifestyle change, it is more effective to gradually change the user’s routine and allow for exceptions when explicitly stated by the user. For example, with Wakey, the user isn't allowed to set a time to wake up later than their consistent wake-up time, so even if the user knew they wouldn't get much sleep, there is nothing they can do about it besides getting rid of the device altogether. So allowing the user to decide is important, even if it seems counterproductive to accomplishing their goals. Second, if you are ever dealing with personal information, everything should be localized on the system itself and encrypted. The average person generally isn’t the target of a hacker and even if one system gets compromised, it is only for one user, not everyone. Hackers tend to target large databases of information, so having a large database of sleep information, along with social media and smart home information, means a lot of personal data is at risk.
Content Rating
Is this a good/useful/informative piece of content to include in the project? Have your say!
You must login before you can post a comment. .