Please enable JavaScript.
Coggle requires JavaScript to display documents.
IA1 Young Person App - Coggle Diagram
IA1 Young Person App
Functions
Access User Location
Concatenate an IP Stack call with the API key, take the longitude and latitude from this call and save it as a variable
Use the previously saved longitude and latitude variables and concatenate them to an openweather API call, extract useful JSON data form this and display it
Access Weather Data
Have a search box implemented that takes the user's input and concatenates it into the openweather API call url
From this call, turn JSON data into a readable format and extract useful data such as weather description, temperature, etc..
There will be a function that will create a list when the user clicks a button, and will generate an 8 digit code for them to access it again in the future
The user will be able to access this list at any time with an 8 digit code and will be able to add any movie/tv show to the list at any time that they want to by clicking on a button
With the users weather data they will be able to have a genre of show picked out for them, and automatically have six movies/shows that align with this genre be displayed to them
A finalfunction that lets users search for either a genre, movie, or to input a budget and have the program respond with an answer to the users search
Existing Solutions
Usability Principles
Must be able to consider all four of the usability principles when creating this web app, understanding how certain websites use these can inform my solution greatly
Seeing a similar existing solution not using usability principles can also inform my solution, as it will tell me what not to do, and will help me to improve on myself
Should give definitions on each usability principle before describing how each website has/hasn't used them properly, and describing how this can inform my solution
Information Gained
This is another seperate section of my existing solution anlysis which describes the useful information that I have gained from viewing the existing solution
This section can describe how I will use what I have seen on the website, in terms of UI/UX for my own solution, and how it will be able to help
Pros/Cons
There will be a pros section in my existing solution analysis that will describe everything I like about the existing solution, and what I will most likely take from it
There will be a cons section in my existing solution analysis that will describe everything I dislike about the existing solution, and what I will most likely not take from it
Evaluation
Each criteria created is fully analysed, not just a simple checklist of whether or not the criteria has been met, but rather an analysis of how or how not the criteria has been met
If the criteria is not fully met, there needs to be a section which describes improvements that can be made to the said criteria in future projects, and how met criteria could be improved to include more facets
A section discussing how this project has made an impact of various facets of every day life, including Personal areas, social areas, and economic areas
Data/Technology
API's
The IPStack API will be used to gather the user's geolocation information, it is important to ask user's for permission to use this data before actually using the API
The Open weather API will be used in order to determine the users weather at their current location, with the location determined by the ip stack api.
Data
Using databases from the open source data website called Kaggle, all data sets on here are open source so that is not something that needs to be considered
The two main datasets that I will use will be one that displays various information regarding Telvision shows and movies on the streaming services of Hulu, Amazon Prime and Disney Plus
Additionally, a dataset will be used in order to determine the genre of shows/movies that are on the various platform this will be merged with the other two datasets to form one coherent piece of data
Data will be normalised and an erd will be created based upon the data in order to demonstrate how the different tables will work with each other, it will be annotated.
UX/UI
Usability Principles
It is important to consider utility in creating both the UI and UX. This will make it easier to access the web app on any device, as it will make it responsive and portable, greatly improving the UX and making users want to return
It is important to consider learnability and effectiveness when creating the web app. This should be considered in order to make all information on the web app as easy to understand as possible, to teach the user about weather
It is important to consider accessibility when creating the web app. If the app is accesibile it will encourage more users, and a higher use return rate due to easy use of the web app
It is important to consider saftey, so that user's will not feel as if their data is being violated, or if they have lost important information on the website. It is important to consider this, to improve the user's experience on the site.
CARP Principles
Contrast on the UI must be considered as it is important in creating a UX that a user will want to return to. If everything is easy to read due to good contrast and pleasant on the eyes they will want to return.
Alignment is also key in making an effective website, it means all the important information is aligned together making it accesible and the website effective at conveying its intended information
It is important to keep things following a pattern, this is why repitition must be considered when creating the web app, it creates a UX that is pleasant. Repititon goes hand-in-hand with contrast
Proximity must be considered when creating the website, this can be considered alongisde alignment
Users
Personas
Must consider the indivudals using this app, personas for differnt age groups and differnet types of experience with technology, different backgrounds, such as careers
Must consider people's past solutions to their problems, and why these solutions just aren't good enough for them anymore
Must consider the context in which they need the proposed solution, and how often they would actually be using it
Must consider how they would be using the app, making sure that every single scenario and context is considered and that all users are accounted for when creating the application
User Group
Must consider how the demographic would use this app, certain aspects specfically targeted towards younger people, and to consider other aspects such as gender, or technological familiarity
Must work out what would make my app stand out against the crowd, and what would make it different to anything else
Must consider what features would appeal specifically to younger people, and what would make them want to use the application more often
Criteria
Prescribed
All aspects of the solution have been evaluated against the criteria, in addition to recommendations being made for future improvements to the web app
A low fidelity prototype has been created, which demonstrates the data used, user interfaces, and algorithms, and is the best representation of the final solution
The boundaries and scope of the task, the constraints and limitations of the environment it is created in, impacts of the solution, and the algorithms required for the creation of the web app have all been identified
Programming features and algorithms must be represented by annotated diagrams, images, screenshots, and sketches
The documentation must contain adequate recognition and description of the data sources that have been used, the usability principles and the user interface components, and the existing solution
Programming features, data structures, user experience and accessibility principles have all been explained in thorough detail
he web app must make use of an open dataset from Kaggle, the data source that is provided within the task stimulus, it must contain no restrictions to its use
Web app must be based upon the restrictions of Python, Flask, Bootstrap and SQLite, in addition to PyCharm the theoretical tool that would be used to construct it
-
The best approaches for the creation of user interfaces, the data structures and the algorithms for the coded solution have been taken
The best approaches for the creation of user interfaces, the data structures and the algorithms for the coded solution have been taken
The proposed solution is feasible and could realistically be created in order to benefit young people, in addition to this, feasibility and the limitations of judging it have been communicated to the audience
The proposed solution is acceptable and feasible enough to be placed within and judged in the Young ICT Explorers competition
Self-Determined
The proposed solution demonstrates how the users weather could be taken into account when recommending shows to watch, affecting factors such as genre
The proposed solution allows users to input age, interests and budgets to determine shows they wish to watch and the recommended streaming services to watch them on
There are three unique user personas created to guide the web application proposal, all young people but coming from very different contexts, and with very different yet related needs and wants
The proposed solution contains three database that have all been merged together and normalised and provide clean and useful data records
The proposed solution contains features that were highlighted within the existing solution analysis, but does not directly copy them, instead taking inspiration from them
The proposed solution takes into account the needs, wants and the context of all users personas that were created in order to create a beneficial web app to the determined audience
The user interface and user experience of the proposed solution follows all usability principles in addition to the Australian Accessibility guidelines
The overall user experience is as pleasant as possible for the user, the imagery is engaging, and there is as minimal steps as possible to access the content that is on the proposed website
The existing solutions contain features which make them accessible to all users, and features which can be used by myself in my own proposed solution
All features of the website are useful for all users, and are made known to the user the second they join the home page, so that there is not any users on the website who do not utilise it fully
Imagery used on the documentation is relevant to the content it is paired with, and is engaging to the Young ICT Explorers Judges and others that the proposal is presented to
The final proposed solution must be easy to navigate for the user, they should be able to know what each section on the website does, and know how to use each section without having to think about it