The first thing I needed to decide was the primary state of the webpage. What if it immediately loaded the camera? This was going to be an issue because Firefox had its own camera verification policy which loaded over the webpage, and you could still see the AR beginning to show (this is an aframe issue that is currently not solvable). As a way for dealing with this issue, I decided to design a landing page, like any usual website. My landing page would begin to show my project as a tool people could actually use, describing and advertise the tool I created through the animations I've shown in a previous blog post. It would also give the user the option to accept the camera. If rejected, the website would refresh and the process would start from the beginning till the camera is accepted.
As my tool is focused on the camera, every instance in the app is unique, based on the environment the user is in. I didn't want to remove the user from their environment, which is what usually happens when designing a normal webpage. This all changes when the camera is involved. All menu elements are overlayed ontop which takes up little screen estate. Keeping menus visible at all times was important. I mustn't forget that my system was dealing with data, data I was exposing which needs to be accessible whenever the user wishes to view it.
The name of the device appears at the top of the screen, tapping on it enlarges the element and shows the extra information that was hidden away till now, showing the user the raw, statistical data that's been collected from their device.
Tapping on an element within this would then take the user to a deeper view of the selected data. For example, if 'Google Home Speaker' is tapped, the past 24 hours of data is own as an overview - such as countries connected to, percentage of the total secured HTTPS, and unsecured HTTP. Tapping on one of these will display a further breakdown. This can all be removed with the touch of the 'Back' button, sending the user back to the camera feed,
scanning IoT devices.
As I progress, I will start designing the sections which show how the user's privacy is dealt with depending on the privacy laws subject to countries their data is entering.
Bibliography List:
SPACE10. (2018). Assembling IKEA’s new AR app, without a manual. Available at: https://medium.com/space10/assembling-ikeas-new-ar-app-without-a-manual-c74c09d0488d (Accessed: 2 December 2019).
Comments