Original List of IoT Ideas:
1. height + weight scale that sends info directly to phone (i.e. healthkit)
2. refrigerator that scans and inventories groceries (can look up inventory, recipes on phone)
3. plug and play conference calling (like handoff but one less step, interface with company network)
4. morning routine application (raises blinds, starts automatic coffee machine, plays alarm music)
5. intelligent music selection (e.g. while running, electronic; while studying, classical; etc.)
6. hotel room setup (NFC code as key, temperature control, tv remote, room service through online acc)
7. instruction "manual" lookup (scan barcode / nfc / take picture -> overlays basic instructions)
8. home light grid (control individual bulbs or set groups instead of guessing with light switches)
9. prompted payments for parking spaces when arriving (+ meter expiry, open locations)
10. parental controls in cars (limit or track max speed, alert set distance/location)
11. integrated library application (check out books w/ smartphone, notifications to return, related/previous searches)
12. exercise exertion meter armband (notify vitals [heartbeat, blood oxygen], warn for overexertion or tenseness)
For my mockup, I chose the prompted payments for parking spaces and associated tasks (#9). I feel this would be widely applicable to many commuters especially in our Berkeley-SF area, as good parking is generally difficult to find, and this would alleviate the hassle of having to pay at the machine and handling remembering times and tickets. This assumes the existence and installation of smart parking meters that can interface with a smartphone and know their status (full/empty).
User Tasks:
A. Locate nearby parking (through a map interface)
B. Decide whether to pay for parking at location
C. Have a counter for when they must return
The index card-based prototype above showcases the general flow of the application. The app loads in on the title screen, and decides which screen to go to based upon the user's location. Users not currently at a parking spot are greeted by the left-most screen, which shows a map of nearby open parking spots (both street and lots). When they drive on one of these open slots or open the app on a previously open spot, the screen switches to the second screen, in which the user can decide whether to pay and for how long they'd like to pay. If they do pay, they are taken to a screen which counts down their time left, and can set a time for a push notification to let them know to return soon. Otherwise, if they decide to cancel and look elsewhere, it gives them the allotted drop off time to leave. In both cases, if time expires, it takes them to an overtime page, which lets users know they should quickly return. On all three of these timer pages, there is a locate button that brings up a map on how to return to the user's vehicle.
After running the prototype past the very helpful user I found at the BART, he appreciated the idea, and he had many ideas to improve the design of the application. On the finding empty parking spaces screen, he suggested that I include almost empty (<15 min or so) parking spots as well, and find a better way to note open street parking spots (perhaps with a green OPEN as with the lots). Also, he suggested that the time counter screens have the specific time at which the meter expires written below in addition to the current counter. Lastly, he felt confused by the term "locate," and felt it would be much better as "find car."
In addition to his suggestions, through the process I also realized that I should implement some way of remotely adding to the meter, so people can refresh if they find themselves running late.
Comments