Skip to content

A numbers version of the Wordle game, deliberately kept simple (Humble)

Notifications You must be signed in to change notification settings

DeeMcCart/CI_PP2_HumbleNumble

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

91 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

HumbleNumble

(Developer: Deirdre McCarthy, May 2023)

Table of Contents:

  1. About
  2. Project Goals:
    1. UX Design - Strategy
    2. UX Design - Strategy - Competitor Portals
    3. UX Design - Strategy - Target Audience
  3. UX Design - Scope
    1. UX Design - Scope - User Requirements and Expectations
    2. UX Design - Scope - Data
    3. UX Design - Scope - Viewing Device
  4. User goals/ user stories:
    1. Site Owner Goals
    2. First-time User Goals
    3. Returning User Goals
    4. Other stakeholder Goals
  5. Further UX Design:
    1. Skeleton - Wireframes;
    2. Surface - Fonts;
    3. Surface - Colours
    4. Surface - Imagery
  6. Features
    1. Included
    2. Future Development
  7. Technology
    1. Languages
    2. Frameworks and Tools
  8. Validation
    1. HTML Validation
    2. CSS Validation
    3. Javascript Validation
    4. Accessibility
    5. Performance
    6. Multi-device Testing
    7. Multi-browser Testing
    8. Testing user stories
    9. Unfixed Bugs
  9. Accessibility
  10. Performance
  11. Deployment
  12. Credits
    1. Content
    2. Media
    3. Code
    4. References
    5. Acknowledgements

About


Humble Numble is a numbers version of the Wordle game, deliberately kept simple (Humble). This site offers a fun way to practice mathematical equations, using an interface that many are already familiar with. Many people worldwide take part in the 'Wordle' game, which offers a chance to guess a 5-letter english-language word in 6 tries. With Wordle, the user is presented with a grid and must choose from a panel showing the letters of the alphabet (26 possible characters), to form a dictionary-recognised english word (ie it is logically consistent). On pressing ENTER, the user's guess is validated, and each letter of their grid entry is colour coded as

  • grey - this guessed letter doesnt exist within the solution;
  • orange - the guessed letter exists in the solution, but not at the guessed position;
  • green - the guessed letter exists in the solution, and was guessed at the correct position.

In Wordle, the panel of letters is also updated with the appropriate colour (grey, orange, green) for the chosen letter.
So.... Humble Numble is a version of Wordle applied to numbers. The panel represents an equation, there is a six-row grid to make guesses, and the user must choose from numbers 1..20 and simple operators +-*/ to arrive at a given target number. The 'solution' is a predefined equation, e.g.
13+5+6=24
5+3-6=2

_ i.e. the format is num1 op1 num2 op2 num3 = target
Any guessed expression must be 'logically consistent' ie should evaluate to the target number. (an error message 'wrong calc' will pop up if an inconsistent equation is entered). Evaluation uses PEMDAS priorities - well actually MDAS -: Multiply first, then Divide, then Add, then Subtract, therefore:
13 + 6 / 3 is evaluated as 13 + (6 / 3), equating to 13 + 2 evaluating to 15.
20 + 12 * 6 is evaluated as 20 + (12 * 6) = 20 + 72 = 92
12 * 6 + 20 is evaluated as (12 * 6) + 20 = 72 + 20 = 92
5 - 2 * 2 = 5 - 4 = 1 2 * 2 - 2 = 4 - 2 = 2 2 * 2 / 2 = 4 / 2 = 2

If an equation contained multiply and divide, the sequence will affect the result, ie : 6 * 10 / 5 = (6 * 10) / 5 = 60 / 5 = 12 10 / 5 * 6 is calculated as 10 / ( 5 * 6) so 10 / 30 or 0.3333

    Rules:
  • All target results will be integers, ie no decimals or fractions. This makes it a little easier to guess.
  • Each equation contains 3 numbers (operands) and 2 operators and must calculate to the target number. A guess which doesn't calculate correctly will be accepted at Humble Numble V1.0 (the user may wish to strategically test out some number or operator combinations, while knowing that they will not solve the equation on this guess).
  • (refer to 'How To Play' for a full set of rules - https://deemccart.github.io/CI_PP2_HumbleNumble/)

    Responsive Mockup

    https://ui.dev/amiresponsive?url=https://deemccart.github.io/CI_PP2_HumbleNumble/

    Live webpage link

    https://deemccart.github.io/CI_PP2_HumbleNumble

    Project Goals


    1. To produce a 6-try numbers-based game.
    2. Using a mobile-friendly development development approach.
    3. Which uses the capabilities of HTML, CSS and Javascript.
    4. And is possible to play with a reasonable chance of success.

    UX Design Strategy

    Wordle (https://www.nytimes.com/games/wordle/index.html) is a game which began as a personal project for software engineer Josh Wardle. As of Jan 2022 it had 2M weekend players (theguardian.com 'Wordle-creator-overwhelmed-by-global-success-of-his-puzzle') and was subsequently acquired by the New York Times. The Guardian wrote that 'Wordle’s popularity is thought to be partly because, in an era of apps aggressively competing for your attention and time, the game was deliberately built to be played once a day, and without features designed to promote its growth such as push notifications and email sign ups.' Current estimates are of 250K daily users, many of whom are repeat users, and 57% of whom play the game on their smartphone (blog.gitnux.com).

    Humble Numble aims to piggyback on the Wordle philosophies of:

    • simple interface with uncluttered screen
    • clearly understood rules
    • scarcity - user can only access one game per day
    • reponsiveness - ability to play on small screens (convenient for user)
    • no time-out - can fit into small pockets of time as game remains on-screen until 6 guesses completed
    • feedback and interaction - user immediately gets feedback when they press ENTER on a guess
    • statistic tracking - user can track # of attempts to solve, number of days solved, success rates
    • peer-group communication - user can share their problem-solving pattern (without revealing any part of the solution) to friends who may also play


    ### UX Design Strategy Analysis - Existing Numble Games

    Using Google search, the following were identified as possible Numble websites -
    https://thenumble.app/
    https://numble.wtf
    https://numble.game
    https://numble.win
    https://numble.online
    https://en.wikipedia.org/wiki/Numble (wikipedia)
    Whilst these sites individually contain some good features, none is comparable to the range of functionality, and simplicity of design, available from the Wordle site.

    Analysis of Existing Numble Websites

    UX Design Strategy Target Audience

    The aim of this specific website is develop a Numble game which can be played in simple form

    The target audience is:
    a. People who enjoy puzzle-solving
    b. People who already play Wordle and are familiar with the user interface (e.g. grey, orange, green guess-letter evaluation; 6 tries, grid layout)
    c. People who want to have a reliable consistent experience through out the game (in other words, they want an opportunity to finish the game by reaching the end, and they want to be able to trust the process (ie they can understand how they move forward or backwards, and they dont feel it is unfair or impossible to complete).
    d. People who like to practice their mathematical skills

    • Game players
    • who enjoy mathematical puzzles
    • and want to have a bit of fun doing it

    UX Design Scope


    UX Design Scope User Requirements and Expectations


    From the analysis of existing games, a set of possible requirements was identified for a new portal.

    The basic requirement for users is to have access to a 'fair' game where they have a possibility of reaching the goal. Humble Numble is a fun way of applying simple mathematical principles
      MVP Requirements:
    • Must be intuitive to use
    • Must be easy to learn
    • Good for first time or returning users
    • Accessible - no ad display & no paywall
    • Familiar interface for Wordle consumers

      Requirements - Desirable:
    • Would like to share results (graphic showing the pattern of result)
    • Would like to be able to track user statistics (cookies)
    • Would like to be able to auto-generate new equations
    • Would like to be able to track equations already used
    • Would like to be able to set difficulty levels

      To incorporate as many of the Wordle characteristics below as possible:
    • Simple interface with uncluttered screen
    • clearly understood rules
    • scarcity - user can only access one game per day
    • reponsiveness - ability to play on small screens (convenient for user)
    • no time-out - can fit into small pockets of time as game will remain on-screen until 6 guesses completed
    • feedback and interaction - user immediately gets feedback for each guess
    • statistic tracking - user can track # of attempts to solve, number of days solved, success rates
    • peer-group communication - user can share their problem-solving pattern (without revealing any part of the solution) to friends who may also play

    UX Design Scope - Data

    A set of equations are pre-loaded which are consistent with game rules (e.g. operator numbers not > 20, calculations return an integer value) Currently Humble Numble will randomly select one of these equations for each game.

    User Goals/ User Stories


    Site owner Goals

    • SO_01 As site owner I want to provide a fun, satisfying game which is visually engaging and highly interactive
    • SO_02 As site owner I want to provide a familiar interface for Wordle consumers (to assist in user learning and ease of adoption for a large pre-existing user base)
    • SO_03 As site owner I want to provide an interface which is uncluttered, free from ads, and not behind a paywall
    • SO_04 As site owner I want to include a mathematical learning experience in this game
    • SO_05 As site owner I want to provide straightforward, intuitive, consistent website navigation
    • SO_06 As site owner I want to provide a website, which meets current programming, performance and accessibility standards (html, css, javascript, responsive, accessibility, performance)
    • SO_07 As site owner I want to provide an opportunity for the user to provide feedback, including reporting issues, or suggesting improvements to the Humble Numble site
    • SO-08 As site owner I want to acknowledge to the user that their feedback has been received
    • SO-09 (FUTURE) As site owner I would like to implement scarcity - so that user can only access one game per day
    • SO-10 (FUTURE) As site owner, I would like to auto-generate new equations
    • SO_11 (FUTURE) As site owner, I would like to be able to track equations already used
    • SO_12 (FUTURE) As site owner, I would like to be able to set difficulty levels
    • SO_13 (FUTURE) As site owner, I would like to provide player stats - user can track # of attempts to solve, number of days solved, success rates
    • SO_14 (FUTURE) As site owner, I would like to facilitate users to share their problem-solving pattern (without revealing any part of the solution)

    First-time User Goals

    • FTU_01 As a first time user I am curious about what this site does, and may just want to quickly play a game
    • FTU_02 As a first time user I would like to be able to easily navigate the site and quickly learn its functionality (particularly if I am already a Wordle user)
    • FTU_03 As a first time user I would like to easily understand game rules
    • FTU_04 As a first-time user I want clear, timely and unambiguous feedback and interaction
    • FTU_05 As a first-time user I expect links and functions that work as expected
    • FTU_06 As a first-time user who is curious about mathematical equations, I want to practice mental maths using a puzzle solving game
    • FTU_07 As a first time user I would like to see my score and receive feedback on my performance
    • FTU_08 As a first time user I would like to play on my device of choice (quite likely my mobile - reponsiveness)

    Returning User Goals

    • RU_01 As a returning user I wish to play the game, just because I enjoy it
    • RU_02 As a returning user I want to 'beat the computer' by guessing the solution within 6 tries
    • RU_03 no time-out - can fit into small pockets of time as game will remain on-screen until 6 guesses completed
    • RU_04 As a returning user I definitely want to be able to see any equation which I didn't guess within 6 tries
    • RU_05 As a returning user I would like to receive a 'fresh' challenge each time I play (ie not an equation thats been used before)
    • RU_06 As a returning user I want to feel that the game is 'fair' and that I can apply my skills to playing it
    • RU_07 As a returning user I would like to be able to contact the developer and to provide suggestions for game enhancement
    • RU_08 (FUTURE) As a returning user I would like to be able to share my results with my friends (graphic showing the pattern of result)
    • RU_09 (FUTURE) As a returning user I would like to receive only one challenge per day (to avoid being sucked into a timewarp of endless gaming)
    • RU_10 (FUTURE) As a returning user I would like to be able to track my statistics and to track/ maintain/ improve my winning streak

    Other stakeholder Goals

    • OT_01 As an educator I might wish to suggest new equations to be solved by Humble Numble players
    • OT_02 As an educator I might promote the use of this game amongst my students to increase their mathematical skills

    UX Design Decisions


    Wireframes

    Landing Page
    How To Play
    Game screen
    Game screen in progress

    Fonts Chosen

    The fonts are deliberately chosen to mimic appearance of Wordle screen. In real life, Wordle uses proprietary fonts (NYT Karnak Condensed), with Helventica Sans for the grid and button text. A reasonably close match, which is widely available on a range of devices, was thought to be the Google bebas Neue font.

    However, when testing the site this did not present a good look, and so Roboto Slab was chosen as a better alternative. Fallback fronts are used in both cases

    Colour Scheme

    The colour combinations mimic Wordle's game (for consistency and to ease the user learning experience).

    The choice of colours for Humble Numble is very much in accordance with user stories S_02 (closely emulate the Wordle look & feel); FTU_02 (first-time user to easily navigate and learn the site) - consistent with Wordle so as to speed the learning process and encourage the focus on the game content, rather than on how to use it.

    Colours- similar to Wordle

    Design Images

    This site has very few images as the focus is on the game content. A 'Wordle-type' logo is used on the Intro page.

    'Wordle-type' logo

    Design Images - Icons and Symbols

    Certain icons and symbols (again based on Wordle look & feel) are used for quicklinks e.g. ? for About page, graphy symbol for Stats page, cog symbol for settings page.

    Features

    F01 Intro Screen

    Introduction screen

    On first using the game an introduction window is shown, the user can choose 'Play' or 'How to Play' buttons. The intro page shows the current date, the Humble Numble day number, and some copyright and acknowledgement notices. This addresses user stories SO_01, SO_02, FTU_01, FTU_02, FTU_03

    F02 'How To Play' Screen

    How To Play screen

    A modal 'How to Play' explains how to play and some of the subtleties of the calculations. Available from the 'how to play' button on the Intro screen, or from the navbar help icon on all screens. The 'How to Play' window can be scrolled to see full text, and is closed by clicking on the X in top right hand corner, at which point it disappears from screen.

    F03 Play button

    The Play button Play button allows the user to go directly to a game screen, and immediately play a game ('call to action').

    F04 Randomly selected solution

    Array of potential solutions
    (Dont look too closely or you will ruin the surprise of playing the game!)
    An array of solutions is maintained, and, when the game starts, an entry is randomly chosen from this array. At the time of development this array contained approx 20 entries, which is sufficient for demo purposes, it is envisioned that this will be extended in the future.

    F05 Uncluttered game screen

    Initialised game screen
    The game screen is presented to the user fully initialised (ie a target value has been set and populated to each grid row). The screen is free of ads and supplemental displays, which allows the user to focus on the game.

    F06 Consistent Navbar

    The Navbar is consistent throughout the website, 404 and feedback pages. (modals/pop-ups are used to show intro and help pages, which don't show the navbar but when they are closed, the navbar can be seen on the underlying page) Contains icons for Help, Stats and Settings. Navbar

    F07 Game grid

    Game panel
    Interactive and responsive game panel which allows the user to record one set of guess tiles per attempt (the current attempt # is shown at top of screen). The game grid is initially blank, and will be populated with successive user guesses. Interactivity/feedback: when the user presses ENTER to submit a guess, the guessed tiles update as green(correct); orange(present) or grey(absent).

    F08 Keyboard display

    Keyboard
    A pseudo-keyboard shows the permitted entries. The user must click on the keys using a mouse pointer to select an entry. When a keyboard key is pressed, its colour flickers to light blue, and the key value is loaded to the current guess row on the game grid. So the keyboard is the main user control for the game, and each press of a keyboard key triggers an action. (keys 1-20, */-+ populate the game grid).
    When the user presses ENTER to submit a guess, the keyboard elements used within the guess also update as green(correct); orange(present) or grey(absent).

    F09 DEL key

    A backspace key is provided which allows the user to remove the last keyed entry on the current grid row.

    F10 ENTER key

    The ENTER key submits the current guess row for validation.

    F11 Equation validation

    When a guess is submitted, the equation which the user has submitted is parsed and validated as follows - the entries at the second and fourth columns are assessed to ensure these contain an operator (plus minus multiply divide); the guessed equation is then validated to check if it equates to the target value. If not, an error message is shown, however the game (at this version) will still progress to individual element valuation. If equation has wrong total

    F12 Individual guess element validation

    Feedback on keyboard re guessed solution
    Each element of the guess is compared to the solution, and its tile colour amended according to whether the guessed tile is: * correct (green)- tile value is at this position in the solution; * present (orange)- tile value is at a different position in the solution; * absent (grey) - tile value is not in the solution. ![Feedback on game panel re guessed solution](./docs/readme_images/f12_game_interaction_feeback.jpg?raw=true "Image of guessed tiles changing colour")

    The corresponding keyboard grid value is coloured on the lower part of the screen, e.g. '5' guessed correct; will colour both the row tile and the keyboard key green. A (hidden) count of the number of correct elements is maintained.

    F13 Success message

    Appropriate success message, content varies by # of attempts
    This displays when all elements correctly guessed. A pop-up message with the appropriate text appears. This text mimics the Wordle site, so depending on the number of attempts the successful user can get (Genius, Magnificent, Impressive, Splendid, Great, Phew).

    F14 Solution display if exceeded 6 attempts

    Solution display if 6 unsuccessful guesses
    A pop-up message with the appropriate text appears if the user has matched the entire solution equation. This text mimics the Wordle site, so depending on the number of attempts the user can get (Genius, Magnificent, Impressive, Splendid, Great, Phew)

    F15 User Statistics

    User statistics

    This screen is really a placeholder for future functionality as would like to display some of the statistics for a player over a number of games

    F16 Settings and Feedback

    User settings

    This allows the user to provide feedback and to choose to join a daily reminder mailing list. There are placeholder questions here for future Limit to one game daily (preset to 'no limit'); Difficulty levels: easy or difficult (preset to 'difficult'). Share image of solution to clipboard (future)

    F17 Responsiveness

    The site is designed to be fully responsive so it can be played on a range of convenient devices.

    Features in Scope

    Mapping of user stories to features

    This website includes 3 pages and 16 features The pages - which effectively bring the features lited in the previous section together - are:

    • Landing Page (see feature F01 Intro Screen)
    • Settings page (see feature F16 Feedback and settings )
    • 404 error page
    • 404 Error Page This allows graceful failure, where the header and footer are preserved, allowing the user to navigate away from an error page using the site navigation (rather than the back button).
    404 error page

    Implementation Decisions

    Pre-defined calculations are stored in a multi-dimensional array as follows: Solution [ [ 3, *,_ 7 * 2, 41_], // ie 3 * 7 * 2 = 41 [2, + , 5 * 7, 41] //ie 2 + 5 * 7 = (7) * 7 = 41 ] Each day's equation can therefore be referenced as Solution[day#] Each days' elements can be referenced as solution[day#, element#] This is useful when comparing a user entry for a match.

    Daily user entries are stored in an array of 7 x 6 rows as follows: Attempt [(undef, green, orange), (undef/green/orange), (undef/green/orange), (underf/green/orange), (undef/green/orange), (success)] Attempt attempt#, element# can be compared to each of the entries in solution [day#, element#y] to search for a match - if found then if attempt.element# matches solution.element# then green, else orange.

    Break out of loop when success, or when 6 tries reached.

    Features Left to Implement

    While Humble Numble, at the current version, provides the 'engine' for pattern matching and calculation, there are a number of desirable features which exist in the current version of Wordle and which would greatly add to the user experience for Numble.

    Choose difficulty level

    • Allow the user to choose difficulty level EASY (all numbers <= 10) or DIFFICULT (numbers <=20 included). Note that this has been allowed for in the array of solutions, these are classified according to difficulty, so this may be an 'easy win' future feature.

    Allow the user to limit to one game daily

    • One of the beautiful features of wordle is its limited-release mode whereby only one puzzle is released daily ... this creates a sense of anticipation and the user wants more, they don't get the chance to become bored or tired with the game.
    • Humble Numble at the current version, allows the user to play continuously by refreshing the browser. This is useful when in testing and demonstration mode, but ideally the default would be one game per day.

    Preserve user statistics from one game to the next

    • This has been allowed for within the user interface by providing a statistics page, however the stats currently only relate to the latest game played. Tracking of # of days 'winning streak' is very motivating to the user.

    Share results

    • Wordle has a feature whereby a user can share their pattern matching results without revealing the underlying solution.


    Technologies

    Langugages

    • HTML
    • CSS
    • Javascript

    Frameworks & Tools

    • Github: used to maintain the code repository, and for some readme edits and commits
    • Git
    • Gitpod: used for editing and for tracking code commits back to Github
    • Balsamiq: used for wireframing
    • Google Fonts: used to locate suitable fonts for website

    Validation

    HTML Validation

    CSS Validation

    Javascript Validation

    • No errors returned, when javascript was pasted into the jshint validator - however 10 unused variables were identified, which are the function names.
    jshint - no errors however the function names were identified as unused variables

    Accessibility

    The site was tested using the WAVE WebAIM accessibility evaluation tool. All pages pass with 0 errors

    Performance

    Performance for all pages was tested using the Lighthouse tool within Google Chrome. Performance was at 98% for the index page (intro modal).

    Performance: Index page

    Device Testing

    The website was tested on the following devices:

    • HP laptop
    • Samsung Galaxy S10 tablet
    • Motorola G(7) android phone

    Multi-browser Testing

    The website was tested on the following browsers:

    • Google Chrome v112.0.5615.138 (HP laptop)
    • Google Chrome v112.0.5615.136 (Samsung Galaxy tablet)
    • Mozilla Firefox v112.1.0 (Motorola g(7) phone)

    Testing User Stories

    User story testing

    Bugs and issues

    issue tracker
    Quite a few calculation and display issues were encountered during development, the above lists the issues encountered and resolved.

    Deployment


    * The site was deployed to GitHub pages. The steps to deploy are as follows: - In the GitHub repository, navigate to the Settings tab - pages - From the source section drop-down menu, select the Master Branch - Once the master branch has been selected, the page will be automatically refreshed with a detailed ribbon display to indicate the successful deployment.

    The live link can be found here - https://deemccart.github.io/CI_PP2_Humble_Numble/index.html

    • To fork the repository:
    • Go to the GitHub repository
    • Click on Fork button in the upper right hand corner
    • To clone the repository:
    • Go to the GitHub repository
    • Locate the Coe button above the list of files and click it
    • Select if you prefer to clone using HTTPS, SSH, or Github CLI and click the copy button to copy the URL to you clipboard
    • Open Git Bash
    • Change the current working directory to the one where you want the cloned directory
    • Type git clone and paste the URL from the clipboard($ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY)
    • Press Enter to create your local clone

    Credits

    Multiple sources were used in assembling this site.

    Content - Humble Numble

    • Inspiration taken from wordle.com

    Code - Humble Numble

    References

    The following sites were ued for research and better understanding while creating this website:

    Acknowledgements

    • I would like to sincerely thank my mentor, Mo Shami for his enthusiasm and support throughout.
    • I would also like to thank Derek and my family for their personal support.

About

A numbers version of the Wordle game, deliberately kept simple (Humble)

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published