Describes a requirement that must be satisfied in the final solution for the solution to be considered a success.
Sounds to describe phrases must be of high quality and clearly audible for the user, and should not breach any copyright or intellectual property laws
Sounds being played to the user is an integral part of the concept and so is deemed absolutely necessary to include in the final build. The sounds must be high quality to the point they can be clearly heard by the user to offer both a solid user experience and to not detract from the mechanic of the app
Sounds must make sense in their connection with answers, and relate to corresponding phrases through use of word-sound association as per detailed in examples
The main mechanic of the concept revolves around the connection between the sound effects being played and the phrase that they correspond with – so the logical link between them needs to be feasible and make sense, else the concept falls apart, and the concept breaks at this point, as the user will not be able to make connections.
Sounds and their connections with answers must elicit relevant information to the magna carta history, and legacy as per the current part of the app, and with appropriateness to the target demographic group
The brief states that there must be a close connection to the Magna Carta as a general concept – therefore it is imperative the factual elements of the correct phrases elicit accurate information in order to meet the brief. The factual information must also be understood by the target demographic.
Sounds must be able to be manually played by the user with the option to repeat if needed
Users must be able to repeat the sound if needed, as they may require a second guess or attempt at listening to the sound in order to confirm their choice. This is a must, as the user may otherwise get stuck and not be able to move on through the app.
The app must save progress on closure automatically, requiring no input from the user to do so, and be persistent during total closure of the app, or shutdown of the device
The persistence of user progress on app closure is a must-have feature as failure to do so will likely cause the user to not want to use the app, as they will have to repeat questions in order to achieve their previous score.
The app must offer the choice of three different answers to the sound combination, of which one is unequivocally correct and two are incorrect
When the correct answer has been chosen there can be no debate as to why it is correct, and the others are incorrect, as this will cause the app to appear to lack integrity. Likewise, more than one correct answer would go against the central concept of the mechanic and multiple-choice quiz conventions, and will be confusing for the user.
The app must include a separate view in which the relevant fact or info is displayed for the correct answer, and be of a legible font, colour, size, and arrangement
A separate view for the facts being revealed after choosing a correct answer is key, as they will not be able to fit alongside the content already being displayed without resulting in an unclean interface and composition, producing a poor aesthetic for the user, potentially dissuading them from continued usage of the application. The font must be legible in all sense of the term in order for the user to easily read, and make use of the information supplied.
Graphical elements and the design of the app must be adaptable and fit on all proposed devices properly.
The visual design of the application must be adaptable – as per the brief, the final product will likely be adapted by a senior designer in order to be built into a large application framework for final release to the client. The graphical elements must be easily adapted to the brand bible supplied by Haley Sharpe design, and the components must fit on all proposed devices in order to avoid incompatibility which could render the app dysfunctional.
Represents a high–priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary.
The mechanics of the game should be self-explanatory and easy to understand through the use of appropriate design cues, visual hierarchy and consistent graphical elements
Self-explanatory mechanics are an ideal feature to have in the app, as it is reasonable to assume a well-formed connection with the game and the user will improve engagement with the concept as a whole, however should this not be included the user can still refer to instructions in order to learn how to use the app.
The app should suggest to the user, or prevent the user from, playing sounds during prayer times at the cathedral, taking care not to sound patronising or offensive, perhaps through the use of looking at the system timer and displaying a relevant message
This feature would be useful to have included as it shows an element of responsibility in the production of, and encouragement of using the app as well as showing awareness of the environment, however the creators are ultimately not responsible for the ways in which users make use of, and the times they use, the app as there are too many outside factors that could circumvent this, including, but not limited to, other applications available to the user in the final product.
The app should have a clear visual sense of progression narrating the structure of the game
This element was suggested in a sense through feedback from the client and university staff – that there should be an emotive element to the game. The inclusion of a progressive narrative through the application helps to reinforce the concept of a storyline to the user, and fosters connection with the subject matter.
The incorrect answers offered should be feasible, and/or believable as correct ones, in order to provide a challenge to the user when selecting a response
If the incorrect answers available to the user are completely, unequivocally wrong due to an obvious tone of speech or subject matter, in stark contrast to that of the correct answer, then it could be argued the content would offer no challenge to the user, and potentially no hook to keep the user interested due to a lack of challenge.
The app should explain how the sounds provided result directly in the correct answer as opposed to the incorrect options through literal description, or potentially synchronised animation with the sound clips in the “correct answer” fact view
Including this feature has the benefit of explaining to the user how the connection is formed, which could in turn elicit a type of rationale the user could apply to following questions, in order to better understand the mechanic and the process through which the sounds have been matched with the answers.
Describes a requirement, which is considered desirable but not necessary. This will be included if time and resources permit.
The app could include a mascot character narrating the playthrough if it appeals to the target demographic, which can be explored through user testing prototypes with said demographic or looking at available research
The inclusion of a mascot would add greatly in terms of emotive appeal and the support of a strong narrative in the app, however is not strictly necessary and this could be achieved in other ways. The addition of a mascot would however be highly beneficial to the value of the app, if time allows this.
The app could include a view showing instructions explaining the mechanics of the game which would be clearly legible and in line with other graphical elements of the game, providing a succinct yet helpful tutorial on playing the game
The mechanic chosen for the game is categorically self explanatory due to the nature of the quiz format being used as well as visual hierarchy and user cues that will be naturally picked up on – however if time allows, the addition of an instructions screen will help to engage users and ensure that full understanding of the concept is achieved.
Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future.
The app wont rely on QR codes as previously discussed due to adding a further layer of complexity and possible issues with architecture in the location
The base mechanic of the application is standalone and the content is not contextualised in an explicit sense that requires QR codes to be attached to the environment. This can be ruled out as a feature due to the sensitivity of the environment, also.
The app won’t be geolocated in the environment as previously discussed due to possible issues with GPS in the cathedral and a lack of necessity for the current feature set
GPS requires a view of the sky to work correctly and/or accurately, and the application has been designed with this in mind. While the concept could be adapted to make use of GPS, it would add another layer of complexity that could block engagement between users and the main intentions of the concept.
The app won’t have a unique or irrelevant visual style in order to remain adaptable to other apps and the design guidelines
As previously stated, the visual style must be matched to the Haley Sharpe design guide as per the brief and client’s wishes, as well as to ensure maximum cohesion with the other aspects of the project as a whole.
The app will not be available in a landscape orientation, due to the lack of content that affords this, and the types of usage by the user that might require this
Landscape orientation compatibility will not be built into the application as a form of usage sanitation, as the content will not be best suited to a landscape orientation and there is no need for the layout to be adaptable to such, for this particular application, as it will offer no salient benefits for the user.