Hmm I find this analysis very interesting and thought provoking. I must be in the minority though, because if Apple made my credit card details available in that fashion I'd be closing my iTunes account and shredding my credit card and asking for a replacement. I don't have any sensitive information on my phone except for my phone No. and address. I also don't own an RFID card but if I did it would be stored in a metal wallet. It seems like all these people are looking for ways to lose your money. I'm not sure how it is in your neck of the woods, but now we don't have to enter a pin or use a signature if the sale amount is less than $30. The opportunity for theft with a combination of $30 limit and RFID card is incredible, and because the bank only lets you criticise a suspected wrong charge for 2 months means you literally need to check every entry on your statement within this time (if you have an RFID based card) They certainly are getting very cavalier with out money.
Yep, DrQuine. So many "uninteded consequences" are waiting to happen. It is interesting that many system design issues today are no longer just about what technologies can do. They are about what they might trigger something we haven't even thought about before.
The automatic payments may be efficient - but they can create problems if you're not thinking of all the possible consequences. If you lend your car to a friend, they rack up the tolls on your EZpass. How many people think of that? Our local pizza place has caller ID and knows when we're calling for pizza. Certainly they could retain credit card information - but any guest in the house would also trigger a payment from our account (and not necessarily even realize it had happened).
The smarter our things get, the more I worry about how secure my information is and to what degree these servcies will do more harm than good for me. While so many of these services are billed as "conveniences," I'm continually impressed at how very poorly companies are at exploiting the information that they do collect about me.
Sheetal: I don't think you need a smart car if you want to pay at a restaurant through some fast alternative. All you need to do is swipe your card once at a restaurant and have them keep it on file for future use. Or maybe you could use a mobile payment option on your phone. There must be 50 ways....
I guess it would be awesome if the restaurant where you frequently go, already has your payment information and you dont hve to spend too much time. Security is the only concern. What if your car is shared with friends and family. It will be nice to have a tablet inbuilt in the car.
Check out the website canbushack: Hack Your Car . Robert Leale of CanBusHack Inc. spoke at the BlackHat conference as part of DESIGN West last year. For instance, the site describes how to:
"Stop Normal Communications (GMLAN and Others): This service is fun because you can make the Normal Communications (the ECU to ECU communications that occurs normally on the network) stop. Why would such a service exist, mostly to clear the bus for large amounts of data such as when a controller is going to be reflashed over the CAN Bus. ..."
Bert22306, I think you are right that it might be better to have the data embedded in the person telly-tubbie style and not in the car. That way you can tell Ronald McDonald to charge the food to guy in the backseat. How does the drivethru deal with multiple people's payment info in a car? What if the car ahead of you charges purchases to the car behind? I'm sure there are already workarounds for this.
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.