...
GUI Section | Screenshot | Design Commentary |
---|---|---|
Login |
| The login screen was designed to ensure the application preserves security. It appears any time the application loses focus, to ensure that anytime the phone changes state, turns off, or otherwise may potentially enter an unsecure state, a password must be entered. The screen was kept simple with just the essential fields and allows the user to quickly enter their password to get into the application. |
Inbox |
| The Inbox screen is where the user can view and send messages from other users. |
Contacts |
| The Contacts screen is where users can browse and edit the users to whom they expect to communicate securely with. |
My Identity |
| 'My Identity' is a simple screen that shows the user's profile data, and a large 2d barcode that can be used to physically share their encryption key with another user of the application. |
Settings |
| This is a basic settings screen with gives a place for the user to modify application settings. This is designed much like any typical settings screen, and as of now only allows the user to edit their password. |
Implementation
Our application was built as an Android application.........
The backend server.......
We used standard toolkit for much of the UI components, such as.....
Individual tabs in the UI were defined as separate Activities, which helped allow the team subdivide tasks across each of screens.
Open Source packages were found and integrated for the barcode reader, numerous icons....
Evaluation
Three user tests were performed in order to investigate the effectiveness of our interface. One developer acted as both facilitator and observer for each test. We located users who we thought we be good targets for the application -- users who were interested in securely communicating with others, but not necessarily those who understood the technicalities of encrypted communication. One user test was performed using the application running on an Android phone, while the others we performed using the Android emulator.
...
The paper prototypes were both fun and informative, as we had not gone through such an exercise before. We learned a lot from having users physically attempt to use the paper version, and vocalizing their thoughts.
GR4 - Computer Prototype
The computer prorotypeFor the computer prototype we were attempting to get the barebones functionality working, as this was the first Android application any of us had worked on.
GR5 - Implementation
asdasdsomething...
GR6 - User Testing
asdsomething...