Update README.md

README.md

@@ -37,7 +37,7 @@ To be able to run the mobile application in a development environment, several s
 
 ## System
 
-In this section, we will go through the framework and libraries used, as well as how the application work and what it consists of. There will also be examples of how navigation, networking, and state is implemented. 
+In this section, we will go through the framework and libraries used, as well as how the application work and what it consists of. 
 
 The application is currently a thin client, and relies on the server to get data. The image below shows a visualization of the system architecture. 
 
@@ -78,7 +78,7 @@ We divided the frontend into roughly four modules; home, camera, profile and adm
     <img src="images/edit_location.png" alt="edit location" width="200"/>
 </p>
 
-The home module is the first a user sees when they log into the application. A map containing all registered locations are displayed, including the user's current position if they have allowed the application to use it. If the user long press on the map, a new marker will be added and a button to add a new location will appear. 
+The home screen is the first a user sees when they log into the application. A map containing all registered locations are displayed, including the user's current position if they have allowed the application to use it. If the user long press on the map, a new marker will be added and a button to add a new location will appear. 
 
 When a user wants to add a new location, they will be taken to a modal screen where they can give the new location a name and a radius. The radius is simply used for aesthetic purposes to highlight the area covered. When the location is registered, the user will be taken back to the home screen, and the newly created location will show on the map. 
 
@@ -86,13 +86,20 @@ The user can also edit existing locations by clicking on the locations, and the
 
 #### Camera Module
 
-[Bilder??]
+<p align="center">
+    <img src="images/camera.png" alt="camera" width="200"/>
+    <img src="images/processing.png" alt="processing" width="200"/>
+    <img src="images/register_salamander.png" alt="register salamander" width="200"/>
+</p>
 
 The camera screen is the second destination on the bottom tab navigator. The screen consists of two buttons, one where the user can upload an image from their phones gallary, and one where the user can take a new picture while using the application. When a picture is uploaded, the user can start processing the image. When an image is being processed, an activity indicator will appear. The algorithm will try to isolate the abdominal pattern and straighten the image, and return this to the user for approval. This process may take some time depending on the internet speed (approximately 15-50 seconds).   
 
 When the processing is completed, the user will be redirected to a modal screen where they can look at the processed image. If the pattern looks good, the user can start to fill in data about the salamander. The mandatory data includes location, species and sex, and the optional data includes weight and length. It is important that the mandatory data is correct, as the algorithm will only try to match against salamanders with the same location, species and sex. 
 
-[Bilder??]
+<p align="center">
+    <img src="images/match.png" alt="match" width="200"/>
+    <img src="images/no_match.png" alt="no match" width="200"/>
+</p>
 
 When the data is provided, the user can click on the "match"-button. If there is a match, a green popup with information about which salamander it was matched against will appear. If there were no match, a new salamander with a new ID will be registered in the database, and the user will be notified through a white popup. When the user clicks "ok" on the popup, they will be redirected to the camera screen, and can process a new image.