Visit the Site
Source Code on Git Hub
The 24 hour challenge.
Build a game of connect 4 within 24 hours.
Git & Git Hub
To create this application as a sole developer, working remotely, within the given time frame.
Time was of the essence, but failing to plan is planning to fail. I needed to visualise the task ahead, so I created a Wireframe 1 to give me a picture of the end product. As well as this, I created User Stories 2 that helped to break down the tasks, but also keep me on track.
I divided the User Stories into two categories, essential and desirable. This ensured I would complete what was essential to the general functionality first, before getting lost on something more peripheral. I also rated each User Story with a difficulty rating to give me an idea of the length I could expect to take on completing each one.
- As a user, I want to see an empty board with multiple play buttons
- As a user, I want to see whose turn it is and their color, after every turn this should change to reflect the current player and their color
- As a user, when I click the play button I should see my piece fall into the correct area
- As a user, when someone gets 4 in a row, the game should stop, notify the winner and reset itself for another game
- As a user, I would like sound affects for the game play
- As a user, I would like a total score keeper
- As a user, I would like an enhanced UX
I decided to use NPM as a way to manage my frontend dependencies and also to give me access to any helpful 3rd party libraries I may have come across.
I used Git to maintain a local repository of the project and a remote repository on GitHub.
Lastly, I decided to deploy my application on Heroku using their CLI, to further enhance my knowledge of Hosting, DNS and Domain Names.
Building an application of this nature from scratch meant there were numerous tasks and problems that needed to be solved. Given the limited scope of this work I will attempt to name a few to give you an insight into the generic challenges faced and my approach to them.
- Create the HTML for the view and position elements using CSS.
- After the User clicks a play button have the piece fall into the correct slot in that row.
- Somehow detect if there are 4 of one color in a row and notify the users of a winner.
- Thanks to my Wireframe, I had a good idea of what I wanted to achieve. The challenge was to achieve that using HTML and CSS.
Given these are both not actual programming languages I believe people actually underestimate the level of understanding and skill required to use both these technologies.
I stubbed out the elements I would need to achieve the look of the landing page
That was easy enough, but currently they simply remained in the normal flow of the page, stacked on top of each other and consuming the entire width of the view.
Normally, I would have gone straight to bootstrap to utilise their grid but I was keen to learn something new and find something better. Welcome CSS Grid!
The learning curve is not too arduous and the results are truly amazing. A technology I believe, will become the go-to for positioning elements on a page.
2. I had the view looking how I wanted, so it was now time to focus on the actual gameplay.
Everytime a user clicked one of the buttons above a row, their color piece would have to fall into the correct slot.
The game board was designed using a table.
Using the HTML(5) data attribute I could give each cell in the table a number.
Now all I had to do, was based on the users click add the piece to the correct cell.
I did this by tracking the amount of clicks on each button above a row, and depending on how many times it had been clicked, that would determine which cell the playing-piece should display in.
Now every time a User clicked on a button to place a piece, they could be assured it would appear in the correct cell every time.
3. This was by far the hardest aspect of the project.
My approach was to conduct a proximity search.
This means, every time a piece was placed on the board, I would look at the square to the right of it and see if that was the same color, if it was I would go to the right of that square and see if the next one was also the same color, and so on and so forth until there were 4 in a row, in which case I had a winner.
This proximity search needed to be done in all directions including diagonally, but as I had given each cell a number in the data attribute, it was simple math which allowed me to check the contents of each cell.
Great, now I could ignore the actual html and simply detect a winner using this array.
Given I would have to run a function for every direction (except for Up), that meant 7 functions would be running every time a piece was placed. In order to make this more efficient, I worked out that you wouldn’t have to always check in every direction, in fact very rarely would you have to run all 7 because only in the middle center of the board would there be a possibility of winning in all 7 directions.
With this proximity search in place, I was able to detect a winner and notify the users.
Note: These were not necessarily the hardest problems or challenges faced when building this application, for more complex functionality please feel free to look over the source code on Git Hub. However, the idea is that you can get a feel for some of the problems and my systematic approach to them.
Given the frontend nature of the project I was able to test thoroughly using the browser, chrome dev tools and the DOM.
In the time given I was able to complete all the essential User Stories, although I did not have time to attempt the desirable ones.
At the time of writing there were no known bugs to me and everything was working fine, however, I have now noticed that sometimes a winner is not detected when it should be. Thus, I would need to look over the proximity search to find and fix this bug.
Feedback from my codementor was positive.
This project was unique. Not only did it come with a rigid time-limit, I was also given no guidance or instructions. I was the project manager, developer, designer all in one. Given this, at the outset, I was concerned whether I could pull it all together and could I achieve the required functionality.
However, in some respects this allowed me to learn and grow the most. I had to work out how to do things from scratch as well as tackle any bugs. This also forced me to learn new technologies along the way such as NPM and CSS Grid.
Although, if I was to do the project again I would consider using another package manager as opposed to NPM. At its core, NPM was designed to manage packages on the backend with nodejs and therefore it turned out to be quite fiddly when using it on the frontend. Moreover, Heroku is also designed to host full-stack applications, so it would have been easier to deploy on a static-only host.
Going forward, this project will stand me in good stead. It opened my eyes to really taking full ownership of a project and how learning new technologies such as CSS Grid and NPM can be a game changer in terms of development.
1: Wireframing is a way to design a website service at the structural level. A wireframe is commonly used to lay out content and functionality on a page which takes into account user needs and user journeys. Wireframes are used early in the development process to establish the basic structure of a page before visual design and content is added.↩
2: A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.↩