Showing posts with label feedback. Show all posts
Showing posts with label feedback. Show all posts

Thursday, 15 October 2015

Week 11: Feedback update

Here is the amalgamated feedback we have received to date (Part A presentation, paper prototype, Part B presentation, Digital prototype) and how we have or will incorporate it into our design.

Done! Will do (but haven't yet) Might do (if there's time) update


Feedback

When

Responses

Levels/Gamification

Add gamification including level up, easy/hard mode, or points for completion. Hard mode could include editing without validating first (see if you can find the errors yourself). Part A
/Digital prototype
Easy/hard mode has been added.  
Easy/hard has been changed to modules.  Easy levels have smaller modules, code is broken up into chunks

Content

Add in option for users to find out more about their content.  Could be through linking back to trove to search topic. Part A Will add if there's time.
Tangential learning is a sub-goal of our product. Users will already be learning through the content provided within the websites. 
Have multi-user option (like google drive) or set up a study group to work on problem together to solve collaboratively. Part A Context of use is for classrooms or extension work.  The style of problem is more suited to individual learning.  We will add a commenting feature for other user’s projects if there is time. Likely we will not have time to implement this feature.

Help

How do users get help?  Could add chat panel or discussion board.

Make help more obvious on editor page
Part A
/Digital prototype
Help section has been added.  
Help similar to codeacademy where they link to relevant stack overflow discussions.
Will include glossary page with information from W3C on tags and tag changes across versions.
Will move help button to errors panel.  
Will make help a pop-out if time.

Audience

Concerns that initial audience of grade 7 & 8 students is too young. Part A Did further research that is discussed in previous blog post.

Audience has been modified
Web historians is for people:
  • who are familiar with HTML and CSS but still beginners
  • might know what validation is but don't necessarily understand it's importance or how/when it can be used
  • would suit grade 10 at school but other beginners in the general public and university
  • would suit classroom use or as extension work for school students

Features

Add in extra level of complexity with option of re-designing pages, not just cleaning up old tags and layout.  HTML5 validators don’t check for aesthetics.  Part A Will add redesign feature if there is time but is not part of our core concept of correcting archived content to current web standards. Likely we will not have time to implement this feature.
Add in a gallery of finished projects with a voting system Part A Gallery of finished projects added
(for all users to see).
Will add in voting if we have time to implement redesigning feature as well otherwise voting doesn't’ serve much purpose. Likely we will not have time to implement working gallery feature.
Separate profile setting and instruction page. Paper prototype Done.
Logo position and style not consistent across all page. Paper prototype Done, logo and header now consistent.

Landing/Home Page

Reduce the amount of text to explain concept Paper prototype Added an infographic/flowchart to explain concept and how you use site.
It should be more obvious whether you are singing up or login (make buttons more distinct from each other). Paper prototype Done with colours/CSS styling
Add explanation for difference between easy and hard mode.

Paper prototype Done on infographic.

Add in extra explanations/instructions for use. Paper prototype Will add more instructions on 'getting started page.
Make categories more obvious and easier to read. Paper prototype Done with CSS Styling. Have increased font size and made categories more obvious through use of colour.
Add in more categories Paper prototype If there is time. Likely we will not have time to implement this feature.

Editing page

Make it obvious what and how users are doing on this page.

Make errors easier to read
Paper prototype
/Digital prototype
Will display number of errors left to solve.
Have changed layout of page to reflect order of work (e.g. errors 1st, editor 2nd, "Save" and "Publish" 3rd)

Add small tutorial/instructions on how panels work/what you do on this page.

Will group errors together, add space between each error, numbering if possible.

Make sure "Publish" button saves as well Paper prototype Will be removing Publish button based on other feedback.  Users will get a 'winning' screen when all errors are solved that will allow them to publish.
Make navigation consistent across all pages (currently different on this page) Paper prototype Navigation/header has been updated on all pages to be the same.
Make layout of editor customisable. Paper prototype Will do if there's time.  This is high on the list of to-do features.
Suggested toggle box to make windows larger or smaller and continue to work in them or a pop-out system.
(relates to previous feedback)
Make code editing window larger.

(breaking up the errors into segments would also help with smaller code blocks).



Part B We will need to look into the current capabilities for adjusting the editors size as well as users ability to resize windows. (Changes to overall page width will need to be represented across the site).

ather than make panels movable, put content in tabs, either
errors thin at top, 2 tabs: html editor and css side by side; viewer, OR
separate html/css/viewer separate tabs and errors visible all the time
Add user name to work Paper prototype Has been implemented on gallery page
Let users know when they have solved errors. Paper prototype/ Part B Will add a 'congratulations' screen.
Remove publish button and allow users to publish privately or public gallery via win screen/pop-up.
Option to share success to social media if there is time.Likely we will not have time to implement this feature.
Add in a seperate box for CSS Paper prototype/
Digital prototype
Have done (but not currently fully functional).

Will make CSS save between modules.
Large amount of errors which load into the working panel. Hard to read/understand/manage (looks hard on easy level).
Suggestions:
  • order the errors by importance
    (must be fixed vs best practice)
  • break  rebuild into sections; could be a good way to tie in gamification
  • components would be a good way to work, encouraging users to encapsulate their code for each segment of a page.


Part B/
Digital prototype
Done See: Easy/hard has been changed to modules. 
HTML editor text is small for some users.  Many found side scroll annoying.  Digital prototype Let users use in-browser magnification to increase or decrease text size as needed.
Have changed scroll to text wrap in editors.
Users would like ability to upload own images to working panel

Digital prototype Will not have time to implement this feature

My Restorations

Make format similar to Gallery/Categories (i.e. tiles in a column/grid) Paper prototype Done
Change % progress bar to actual number of errors to make it more meaningful Paper prototype Done

Login

Would like log in to autofill after sign-up align font awesome icons Paper prototype Will do if there is time.

(Originally posted on our team blog: Restoring the web)

Week 11: Digital Prototype in class test

Here are the result of the Digital Protoype test session we ran in our contact session this week.  We aim to conduct the same test with real users in the next week.

Number of users: 5

Task 1: Login stress test and workflow test


  • Would like log in to autofill after sign-up
  • align font awesome icons

Task 2: Working panel and accessing help

Did you read the instructions on the home page?

  • no but prior knowledge of product x2
  • yes x2

Would you expect further instructions at this point?
  • as a dev, would rather play first
  • small tutorial maybe?
  • no
  • instructions didn’t cover working panel windows, this is what each bit is, need to understand layout

Do you know what to do on this page?
  • yes
  • where can i type?  looks a bit scary?


What would make the errors easier to read?
  • grouped together, space between each error, numbering would be good, bullet points, checkmarks
  • they are fine to read
  • multi-line erros, where does one error end and another start, gaps between each error, alternting line colours, wrap in container


If you didn't understand an error, where would you look for help?
  • google problem, not go to internal help
  • help should not be at the bottom
  • help should be modal or pop-out
  • difficult to see help button, add '?' help to error panel
  • put help with errors
  • google, stack overflow is industry standard on how to look for help


For each web page, there are multiple modules (e.g. Cricket Australia has 8 modules) that all pertain to the one page.  When you add CSS to the CSS editor and save, would you expect to see your saved CSS when you progress to the next module (i.e. Module 1 to Module 2)?
  • blank, prefer to start fresh each module
  • carry over if part of same website
  • frustrating to start over
  • would copy and paste if not automatic
  • yes, definetly

    Task 3: Use the working panel


    • would like ability to upload own images 
    • html editor text small x 2
    • html editor wrap text rather than scroll x2
    • rather than make panels movable, put content in tabs, either
      • errors thin at top, 2 tabs: html editor and css side by side; viewer, OR
      • separate html/css/viewer separate tabs and errors visible all the time


    (Originally posted on our team blog: Restoring the web)

    Week 11: Digital Protoype Test procedure

    This is the procedure we used in the digital protoyping session in class and will repeat with real users in the next week.  Sessions are run a one-on-one, in-situ interviews and usability tests.  Encourage users to talk aloud as they participate.  Remember - it is the system being tested, not the user.

    Pitch the concept:

    Explain concept but don't give any specific instructions on how to use site.

    Web standards are important to ensure that web pages display correctly in all browsers. Learning current web standards and how to comply with them are an essential part of learning how to write HTML and CSS. As web standards change over time, they depreciate old tags and introduce new tags and new features. One of the problems with archiving old websites (e.g. Trove, Pandora, Wayback Machine) is that even as web standards change, the archived websites still use the old, out-dated HTML tags.
    Web Historians provides HTML/CSS beginners with a practical, interactive web application to familiarise them with correct syntax and layout, the concept of web standards, the process of validating code against the latest standard, in context use of HTML and CSS, and basic editing.

    Task 1: Login stress test and workflow test

    Ask users to familiarise themselves with the home page (index.php) and when they are ready, sign up, log in, and log out.
    (tests the login system, workflow of log in/out and set-ups for the next task to see if the instructions/information on the home page are read)

    Task 2: Working panel and accessing help

    Ask users to log in with test account (tester/tester) and navigate to the test module for Cricket Australia. (tests navigation to working panel)

    Questions:

    • Did you read the instructions on the home page?
    • Would you expect further instructions at this point?
    • Do you know what to do on this page?
    • What would make the errors easier to read?
    • If you didn't understand an error, where would you look for help?
    • For each web page, there are multiple modules (e.g. Cricket Australia has 8 modules) that all pertain to the one page.  When you add CSS to the CSS editor and save, would you expect to see your saved CSS when you progress to the next module (i.e. Module 1 to Module 2)?

    Task 3: Use the working panel

    Ask users to have a play with the working panel, they can edit HTML, add CSS, and re-validate.  Ask if they have any comments or feedback.

    (Originally posted on our team blog: Restoring the web)

    Tuesday, 8 September 2015

    Week 7: Experiences with paper prototype

    For the paper prototype this week, we split our group into two groups.  Two people (Felix and Rena) conducted the paper prototype session with classmates (results posted on our blog) and Lyndon and I tested the paper prototypes for the other groups.

    Our paper-prototype

    We had paper mock-ups of all the main screens in our app, including pop-ups, and a list of tasks we wanted users to complete.  These tasks were designed to test navigation, whether the path needed to complete tasks was clear, and whether the layout of individual elements of complex pages (e.g. the working panel) had a logical layout that made sense to users.

    Other groups

    It was interesting to see how the other concepts were progressing, but more interesting to observe other prototyping practice and procedure.

    A great example was pinboards.  They used a digital version of the paper prototype - it had the same level of interactivity as the paper version but was able to record user's inputs digitally.  Their session was reminiscent of the Digital Prototyping subject many of us are also doing this semester.  They had clear objectives of what they wanted to test (i.e. what questions is the prototype trying to answer) and followed up with a user questionnaire to help quantify and record their results.  They also took the session seriously, they used a script and addressed testers as potential users rather than classmates (i.e. more formally).

    There were elements of concepts from some of the other groups that I really struggled understanding, but that is part fo the process of testing, helping to clarify concepts and how users will interact with the project.

    Even though I didn't run the paper prototyping session for our group, it was still a worthwhile experience to act as a user for other groups.

    Sunday, 6 September 2015

    Week 6: Experiences in the Poster & Pitch

    Concept, project and design process  

    Documentation

    Writing up part A document was fairly similar to project documentation I have written for projects at work.  While it seems like a lot of writing and a lot of work, it is an important skill with workplace application.  It is also important because it clarifies a lot of the detail of our project and outlines our plan for how we will turn our concept into an application.

    Design thinking

    Design thinking last semester taught us a lot of different processes and design techniques.  They were all clearly prescribed and written into our assessment criteria.  The criteria for this project doesn't have the same level of detail and I found myself thinking back to those pieces of assessment as a guideline.  I imagine my design thinking toolbox will get easier to remember the more I use it.

    The brief

    Student briefs are generally comprised of two elements, the 'client' needs and the assessment needs. One of the problems we have already come across (as detailed in a previous post) is which APIs we will need to use to complete the project.  The 'client' needs is to highlight an area of Trove, the assessment needs is to learn how to use API calls (in particular the Trove API).  It was good to find out that there was a little room to move so that the 'client' need still came first.

    Feedback

    I did a quick write-up of the feedback we received from our Part A presentation on our team blog. We also went over the feedback in more detail in our Part A document.  The piece of feedback that stood out most to me was around help.  Our intention for our concept was never to provide training but for it to be a tool students could use to practice html skills and in the process learn about web standards and practice validation.  It hadn't occurred to me to provide help information or how our users would go about getting help if they were stuck.  There were many suggestions from class including a discussion board, chat or links.

    I recently did the AngularJS track in Codeacademy and really liked the way they did help.  One problem with chat (and other types of help) is that it requires staffing or moderation.  The way codeacademy approach is to leverage existing methods of getting code help and incorporating it in context (i.e. where the student needs it). Here are some screen shots.







    Even though they use other services to provide the help, they still guide the user there with questions. This is a much better approach than just providing links or a discussion board.  While we can put together information on tags and tag depreciation to get users started, if they are looking for more in-depth help, Stack Overflow would be the best source for this.  The other benefit of this is familiarising users with standard help channels for code that they can use in future for other coding problems.


    Other teams

    Seeing other teams progress was good inspiration.  It was interesting to see how they had divided the team responsibilities and how technical their projects will be.  I know there will be quite a lot of learning ahead of me to be able to complete the project but I found it encouraging listening to other teams proposals and how they are approaching the different components.  The other concepts were also interesting to see, especially the shipwreck one (Atlantis).  Early Australian shipwrecks was the individual concept I presented and I'm really interested to see how another team will pursue and change the idea. Seeing it progress to a more complete interface from the wireframes I presented was great.

    My process

    Completing the part A presentation and documentation has reiterated to me the importance of planning in design thinking techniques to a project.  It would be easy to plan a project considering only the end product and the technical needs (i.e. how am I going to make this).  But it is important to plan in time for research, testing and feedback.  I know that there are a lot of design resources (like the d.school) but I also think it might be good for me to keep a record of the different techniques I've used to add to as I progress.