On April 21, we presented a Smart:Drive rapid prototype to show what our product will look like. We showed our hardware device as a breadboard with chips and wires, without the casing that we will build. We then showed our Nexus One smartphone that we will use for development and testing, and we described our plans for the user interface of this Android app. Lastly we showed static mock ups for our web portal, including a sign in page and a route-map page. These mock ups as pdfs are available on our main web page.
Some feedback we received from this presentation is listed below.
Status lights on the hardware device? Will we use this technique to provide the user with low-level feedback and aid in troubleshooting? For example, we could show that the bluetooth module has failed or succeeded to pair with an Android app.
Will we provide users with the raw data from their trips? As a spreadsheet or textfile?
As a future goal, are we thinking about Smart:Drive becoming a tool to create dynamic MPG maps, like traffic maps that show up in black or red where traffic is heavy, and it shows up as green where traffic is light?
Will we calculate an eco-score for users? Would we base this off of their peers (other people driving in same city/region)? Or the expected performance of their car make/model?
Will we provide feedback on users' driving habits? Including fast acceleration and riding a gear?