Design Computing Studio Week 13 - Final Submission

Design Computing Studio Week 13

Final Submission

This is the final week for submission of Project Jumper.

We are Team Jumper!

This is the stall for the project

Some of the team in preparation for the trade show.

Design Computing Studio Week 12 - Revision

Design Computing Studio Week 12

Revision

The project is due next week, so the following changes this week is mainly just revising some of the design decisions and applying a bit of polish on the interface.

This is the main screen, now with a working image slider. You can also see images that were tagged previously, and  your own tag is now saved to a database.

The home screen, as it would look on a digital device like a tablet.

With the addition of bootstrap code, we now have a responsive layout.

As complicated as it was to add Bootstrap code, it turned out for the better. This is how it would look on a smaller device like a mobile phone.

This is the friends list page as it would appear on a larger screen.

This is the friends list page as it would appear on a smaller device.

This is the appearance of the Profile page on a large screen.

The appearance of the profile page on a smaller screen device.

Design Computing Studio Week 11 - Digital Prototype Testing

Design Computing Studio Week 11

Digital Prototype Testing

This week was the testing of the digital prototype for the Jumper application. See below to photos of the user testing.

Design Computing Studio Week 10 - Progress continues

Design Computing Studio - Week 10

The application continues to take shape, with additions and updates being added daily.

Design Computing Studio Week 09 - Presentation

Design Computing Studio Week 09

Presentation

This week we had our final presentation before the final delivery. Mostly we had positive feedback, and there were a few difficult questions asked concerning constancy and visual appearance. 

So after the presentation, we had a discussion of the feedback and constructed a plan to completion document, where we gave everyone in the group tasks to complete, leading up to the final submission.

My role would be primarily to incorporate bootstrap into the system. Also smooth over the HTML and CSS coding of the project, using the style guide, ensuring coherency, contrast and consistency. 

Design Computing Studio Week 08 - Presentation Preparation

Design Computing Studio Week 08

Presentation Preparation

This week was mainly about preparing for the progress demonstration next week. We needed to show that we had made progress toward implementation, so each team member was assigned a specific task, and we had a lot of discussion and coding for the digital prototype.

Receiving images from Trove was setup nicely, although it still had limitations with the amount of images that were available. The Google maps API was also setup. We now have a main page where Trove pictures are being displayed, and a functional GPS with maps. Now it's just a matter of proper user interface design, and getting the GPS code working properly.

70% of the work has been completed, however it is this last 30% which has proven to be the most difficult and most time consuming so far.

Another thing we need to consider, is the motivating factor to select and tag the images, encouraging people to use the application more. We are pretty much aware of what we need to do from this point onward.

Design Computing Studio Week 07 - User Testing

Design Computing Studio Week 07

Paper Prototype

Today was the day of user testing with a paper prototype of the application. During the testing, we got some very detailed responses where almost everyone managed to break it in some way. Which is surprising, since it was made of paper.

Findings from the user testing shows that some things need to be changed conceptually. We made a lot of changes on the fly as we were testing between users. The things we need to consider are the following:

1. The overall concept was working, but it very confusing.

Firstly the navigation. The testers were not really sure which part of the application they were looking at, and the icons were not the standard convention.

Secondly, people were confused whether the application was gamification focused, or a social focused thing. As gamification has a very strong social aspect to it, this doesn't seem to be a problem. It's about competing against other people, which needs a social component or else it won't work.

2. The login system, is it necessary?

We had the option to log in using your Facebook account, or through email. Feedback from Launa stated that we do not need to worry so much about that. We can assume the user is already logged in, and we can work with a single user.

3. The first time opening the tutorial

At the beginning when you open the application, most apps have some form of tutorial. It can be in the form of tool tips, or a welcome screen, with the ability to turn it off. Also, perhaps the first few levels can be a tutorial to understand the game.

We need some form of initial instruction to help them guide the user through the game, yet that is not so important in comparison to getting the actual game to work first.

4. Using global icons to denote navigation and symbols

The icons are not conventional designs. Sometimes they are not self-explanatory. There was a problem with a particular form of icon we had, but there is also an ability to add a little bit more detail to the icons, to polish the interface design, We need to consider how understandable our icons are.

5. You can only log out through the settings page, 

The setting page can only be accessed from the profile page. It's a bit of a journey to log out. However, how often do you log out of a mobile application? From your mobile device?

It doesn't really matter that it isn't immediately obvious, as very rarely do people log out from mobile apps.