diff --git a/README.md b/README.md
new file mode 100644
index 0000000..a790ab8
--- /dev/null
+++ b/README.md
@@ -0,0 +1,39 @@
+## RN2048
+
+### Background
+
+In the evening of the 25th May, 2021, I decided to task myself with a 4-day weekend build. I wanted to learn how to use the react-native-gesture-handler package and I decided to code the game 2048 with typescript React Native.
+
+This project took all 4 days, or effectively, 20 or so hours to complete. Days 1 and 2 were spent developing the game's main algorithm, day 3 was spent debugging and refining the code, and the final day was used to style, refactor, document, and release everything.
+
+### Technical Details
+
+Ths app consists of 2 pages, the main game page and a record page which displays all the games the user decides to save.
+
+Due to time concerns, animated movement for the tile on the grid have not been implemented. But this could be done with react-native-reanimated or other similar packages.
+
+#### Libraries Used
+
+Below is a list of all the node packages used for the project (React Native base packages **EXCLUDED**)
+- react-native-gesture-handler
+- react-native-modal
+- react-native-vector-icons
+- react-navigation (and all of its subsequent packages)
+    - the stack navigation package
+- redux (and all of its subsequent packages)
+    - react-redux
+    - redux-persist
+        - react-native-async-storage
+
+### Gallery
+
+|       Game Screen (Dark)        |       Game Screen (Light)        |         Gameover Popup Screen         |            Record Screen            |
+| :-----------------------------: | :------------------------------: | :-----------------------------------: | :---------------------------------: |
+| <img src='./img/game_dark.jpg'> | <img src='./img/game_light.jpg'> | <img src='./img/gameover_screen.jpg'> | <img src='./img/record_screen.jpg'> |
+
+
+### Maintenance and Future Updates
+
+As of now, there are no plans to maintain nor further develop this project, as this is only a weekend sprint build.
+
+Although there is no incentive to do so, the way the app is coded is prepared for further expansion, such as different sized boards. The algorithms were developed to be able to handle boards of all sizes. Adding new screens to accomodate for board size selection would also be easy as screen components are extracted and abstracted from the navigator itself.
diff --git a/src/game/board.ts b/src/game/board.ts
index d2b4bd5..1079f63 100644
--- a/src/game/board.ts
+++ b/src/game/board.ts
@@ -1,4 +1,4 @@
-import { cascade } from "../utils/array";
+import { cascade, compare } from "../utils/array";
 import { Direction } from "../utils/enums";
 import { CoordinatePair } from "../utils/types";
 
@@ -25,9 +25,12 @@ export default class Board {
 
     static swipe = (board: Board, direction: Direction): void => {
         let temp = cascade(board.board, direction);
+
+        if (!compare(board.board, temp.board))
+            Board.newTile(board);
+        
         board.board = temp.board;
         board.score += temp.score;
-        Board.newTile(board);
     }
 
     static validate = (board: Board): boolean => {
diff --git a/src/utils/array.ts b/src/utils/array.ts
index 5683801..0161bbc 100644
--- a/src/utils/array.ts
+++ b/src/utils/array.ts
@@ -69,3 +69,15 @@ export const cascade = (arr: Array<Array<number>>, direction: Direction): GameCo
     }
 }
 
+export const compare = (board1: Array<Array<number>>, board2: Array<Array<number>>): boolean => {
+    // assuming they are of same dimensions
+
+    for (let i = 0; i < board1.length; ++i) {
+        for (let j = 0; j < board1[i].length; ++j) {
+            if (board1[i][j] !== board2[i][j])
+                return false;
+        }
+    }
+
+    return true;
+}