{"id":687,"date":"2017-01-03T01:13:43","date_gmt":"2017-01-03T01:13:43","guid":{"rendered":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/?p=687"},"modified":"2017-01-03T01:13:43","modified_gmt":"2017-01-03T01:13:43","slug":"blog-6-storyboarding-our-product","status":"publish","type":"post","link":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/2017\/01\/03\/blog-6-storyboarding-our-product\/","title":{"rendered":"Blog 6: Storyboarding our product"},"content":{"rendered":"

Before we jumped straight ahead into prototyping, the team had reservations about the number of potential conflicting concepts we had. Therefore, we approached the means of storyboarding to set the design in context , which would help us to visualise the app itself and clarify the key function we would like to include for our prototype.<\/p>\n

Plot<\/u><\/strong><\/p>\n

Set: Friday night<\/p>\n

After a long working week, our main character, Mr. X went back home and planned to have a chill out night. He then took out his iPad, went on Facebook and starting to browse his wall.<\/p>\n

Suddenly, a notification from Jesmond Community Energy Dashboard pops up, saying \u2018your estimated monthly bill for the end of the month: \u00a3124\u2019. Mr. X was shocked, he didn\u2019t expect to pay that much, since he normally pays \u00a350-70 for a month.<\/p>\n

He then went on the app, checked on the energy usage and found out the main source of energy usage was the radiator in the living room, which he always forget to turn it off when he doesn\u2019t need it.<\/p>\n

He\u2019d like to share this experience with his family and friends, warning them not to leave any electric applicant on when not using it.<\/p>\n

Luckily, there is a share button in the app, making it a convenient way for Mr. X to share it to his friends and family.<\/p>\n

\"storybvoard-1\"<\/p>\n

Unfortunately, this was the storyboard specifically for the app only. There will be some alteration so that there\u2019s an influence to install a solar panel for their house, aiming specifically to the Jesmond Community. However, we\u2019ve managed to determine that there are several key aspects that we would like to include in our dashboard prototype.<\/p>\n

    \n
  1. Monthly Energy Consumption (i.e. the graph that shows how much energy used for the month)<\/li>\n
  2. Estimated Monthly Bill (what all users care about the most)<\/li>\n
  3. Energy Consumption Pattern of user<\/li>\n
  4. Graph that shows the amount of energy used for the past months (Archives)<\/li>\n
  5. Push Notification (smartphones and tablets specifically)<\/li>\n
  6. Social Media Buttons for easy shares<\/li>\n
  7. Of course, some extra minor widgets to add a little spice to the app.<\/li>\n<\/ol>\n

     <\/p>\n

    However, after feedback on our first storyboard we as a group decided to alter our storyboard and we now have a new story based on the most important feature of our project which is renewable energy.<\/p>\n

    \"storyboard2-feedback\"<\/p>\n

     <\/p>\n

    The concept is very much the same as previous just slight alterations.<\/p>\n

    They are as follow:<\/p>\n

    Setting is now end of July and the new production figures have come through from the company, so he\/she goes signs into the app, goes onto the production page where last month\u2019s figures for June are present, they then select the add new button which then takes them onto another page where they can enter the new data, once that has been done they can then submit the new data which updates on their production stats. Then finally they share their monthly figures with everyone on the JEPP app to show how much energy they\u2019ve made for the month.<\/p>\n

    We have now finished with the storyboarding and are now moving on to start thinking about making the prototype, watch this space!<\/p>\n","protected":false},"excerpt":{"rendered":"

    Before we jumped straight ahead into prototyping, the team had reservations about the number of potential conflicting concepts we had. Therefore, we approached the means of storyboarding to set the design in context , which would help us to visualise the app itself and clarify the key function we would like to include for our … Continue reading Blog 6: Storyboarding our product<\/span><\/a><\/p>\n","protected":false},"author":6572,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,29,33],"tags":[],"class_list":["post-687","post","type-post","status-publish","format-standard","hentry","category-refining-and-story-boarding","category-story-boarding","category-team-4"],"_links":{"self":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts\/687","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/users\/6572"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/comments?post=687"}],"version-history":[{"count":2,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts\/687\/revisions"}],"predecessor-version":[{"id":691,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/posts\/687\/revisions\/691"}],"wp:attachment":[{"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/media?parent=687"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/categories?post=687"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/digicivics-at-apl\/wp-json\/wp\/v2\/tags?post=687"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}