<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ollie on Medium]]></title>
        <description><![CDATA[Stories by Ollie on Medium]]></description>
        <link>https://medium.com/@norrisollie?source=rss-944d0535b428------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SWhJE2Cl5way7prq76rpPg.jpeg</url>
            <title>Stories by Ollie on Medium</title>
            <link>https://medium.com/@norrisollie?source=rss-944d0535b428------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:37:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@norrisollie/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Working with Javascript]]></title>
            <link>https://medium.com/@norrisollie/working-with-javascript-44abeab2ede?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/44abeab2ede</guid>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Wed, 14 Jun 2017 00:27:27 GMT</pubDate>
            <atom:updated>2017-06-14T00:27:27.652Z</atom:updated>
            <content:encoded><![CDATA[<p>I learnt the basics of Javascript whilst I was working as an intern for a company in Amsterdam. Before I started, I had very little knowledge of Javascript and knew the basics of jQuery.</p><p>I wanted to write my application is Javascript as when I was working as an intern, I was unable to use jQuery as it relies on a large library. Whilst jQuery has the advantage of making it quicker and easier to code, if you only need to use a small amount of jQuery on a website, you are loading a lot of code that is not going to be used. It does also sort out compatibility issues between browsers, however with the most recent version of Javascript, these are not so much of a problem.</p><p>I started off by creating a function called app. This function is used to contain all of the code required for the application to work.</p><p>The function is invoked by using the code on line 8. What this means, is that the function cannot run until the window has loaded. This includes content such as text and images. It is important that all elements of the page have loaded before the Javascript runs, as it may cause errors or may not work properly.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/56311b6f8393eefd205230a73793a057/href">https://medium.com/media/56311b6f8393eefd205230a73793a057/href</a></iframe><p>I then created a section that would contain all of the variables used to store elements in the DOM (Document Object Module). I wanted to include most variables within the app function, as this meant that the variable names could be used within all functions contained within the app function.</p><p>Variables that are declared within a function are local variables, meaning that they can only be used within that function. Variables that are declared outside of a function can be used throughout the whole Javascript file. Variables can be anything, such as text, integers and elements.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/401022803b2ba3d82abb00314dc1b4a9/href">https://medium.com/media/401022803b2ba3d82abb00314dc1b4a9/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f7e58e6c51cada91e4e8c6fa522b798c/href">https://medium.com/media/f7e58e6c51cada91e4e8c6fa522b798c/href</a></iframe><p>In order to ensure that the user is connected to a secure connection using https, I used an else/if statement. This code works by checking whether the page has a secure connection. If it does not, then it will automatically change to a secure connection through https. This is neccessary as geolocation only works through a secure connection and cant work if the connection is not secure. An else/if statement works by checking whether a specified condition. If the condition is met, the code will run, if the condition is not met, another piece of code will run instead.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/074b9d0eb574726b30a59ac6ce06007c/href">https://medium.com/media/074b9d0eb574726b30a59ac6ce06007c/href</a></iframe><p>The next step is to see whether or not the browser supports geolocation. If the the browser does not support geolocation, a message is logged to the console to state that the condition is met. If the browser does support geolocation, then a message is sent to the console to state that browser does support geolcoation. The code will then move on and run the next line of code.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1a80355abf20798918fe7a34e8ed225/href">https://medium.com/media/e1a80355abf20798918fe7a34e8ed225/href</a></iframe><p>The code will continue running until line 22 as the two functions “locationSuccess” and “Error” have not been called yet. Line 22 is a callback function, and this code will determine what function to run. If the browser does not support geolocation, the browser will run the error function. If the browser supports geolocation, it will run the locationSuccess function. It will then run the code within the opening and closing parentheses.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d7e8cb514441954cbc8ff0ddce0c715f/href">https://medium.com/media/d7e8cb514441954cbc8ff0ddce0c715f/href</a></iframe><p>Within the location success function, it will start by creating a console log to display the message on line 4. Variables are declared on line 7 and 8, the variables will store the users location. A callback function is then used to run the success function. This function requires two paramters, the latitude and longitude.</p><p>I needed to use the users coordinates as parameters, as it would allow me to use the user’s coordinates outside of the locationSuccess function.</p><p>The next step was to find the closest stations to the user. I created a function called findClosestStations. Within this function, a URL would be created using the “closestStationsURL” as a template. The two variables “userLatitude” and “userLongitude” would be replaced with the user’s coordinates to generate a URL which will be used to send an Ajax request to the server.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ccd7155fffebe9b588adf39a8c94d193/href">https://medium.com/media/ccd7155fffebe9b588adf39a8c94d193/href</a></iframe><p>Once the URL to make the request has been created, a request can then be made to the server. To do so, you will need do an Ajax request. The advantage of using an Ajax request, is that it is done asyncronousy. This means that the page does not need to be reloaded to get the data.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/70a0c3a7ae5dc909d6d51091ebdafa6d/href">https://medium.com/media/70a0c3a7ae5dc909d6d51091ebdafa6d/href</a></iframe><ul><li>Line 1 — A new request is created</li><li>Line 2 — The request is opened, the request type is a “GET” request, meaning that you are just going to get the data from the API</li><li>Lines 4–12 — If the request is successful, the function will run and any code within this function will run.</li><li>Line 5–12 — An if/else statement is used to determine the status of the request. If it is between 200 and 399, it is successful. If it is outside of these numbers, this means the connection is successful, however there may be an error with the request.</li><li>Lines 14–16 — If the request has failed, usually due to an error with the connection, then the error function will run.</li><li>Line 18 — this will send the request to the server.</li></ul><p>In order to generate the buttons, I needed to define a variable called closestStationsRes for the response data (if the request is successful). I then created another variable called closestStationData to access the array in the response data called “result”. This array contained all of the stations in order of distance.</p><p>I then used a for loop to go through the closestStationsData variable array. As I only needed the five closest stations, I set the loop to stop after it has gone through the array five times.</p><p>I created variables, named according to the information I needed from the API, to get the data I needed to use to create the buttons.</p><p>I used a console log to store all of the data I received from the API, and created a new variable as a template for the button.</p><p>On line 30, this code then inserts the buttons in to the closestStationsDiv.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6883a24ea8c085052aa90e0214e79459/href">https://medium.com/media/6883a24ea8c085052aa90e0214e79459/href</a></iframe><p>If there was an error, instead of leaving the user unsure about what has happened, I wrote some code that would insert a message informing the user that there was an error and the closest stations could not be found. On line 25, this code is required to run the function.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fbd8388b03d87960d0c3e616310dcaaf/href">https://medium.com/media/fbd8388b03d87960d0c3e616310dcaaf/href</a></iframe><p>The next step was to create a function that allows users to search for trains. I started off by creating an event listener that listens for a click event on the submit button for the form users will use to enter a station and perform a search.</p><ul><li>Line 2 — this is the click event, this will listen for the click event on the submit button, and run the function “searchForTrains”.</li><li>Line 5 — this is the function that will run when clicked. The “e” parameter is the element that is clicked.</li><li>Line 8 — this is the variable that is used to store the element that has been clicked, which would be the submit button.</li><li>Line 11 — this prevents the default action when a button is pressed, which is a page refresh.</li><li>Line 14 — this takes the value that the user has entered within the search form.</li><li>Line 19 — this is the template for the URL that will be used to make an API request. It will use the originValue variable to create the URL.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ec7e4075fe6e67b2be553285e04a85e1/href">https://medium.com/media/ec7e4075fe6e67b2be553285e04a85e1/href</a></iframe><p>The next stage is to create an API request to get the data that is required, such as train times, origins, destinations and other relevant information. I have not included this code as I have already explained how an Ajax request is made, and how the data is accessed from the response data.</p><p>The API used to provide me with information about trains sometimes returns data that is not useful for humans to understand. For example, if a platform number is not available, the server will return null.</p><p>In order to make this more useful to humans, I used an else if statement to determine whether the response was “null” and change it to unavailable instead.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/277bef147561dd4eb83dda3defb36385/href">https://medium.com/media/277bef147561dd4eb83dda3defb36385/href</a></iframe><p>Once all the data has been requested from the API and all the variables to store all the relevant data required, I then created a DIV template that would take all of the data, place them in the relevant DIVs and then insert it in to the wrapper for the search results. After it has been inserted, the clases “hidden” are then removed to display the wrapper and container, which will contain the train service information to the user. This code is contained within a “For” loop, the loop is repeated for the number of entries in an array, which will depend on how many train services there are. I used the “.length” property to find the length of the array. If for example there were 12 services, the loop would run 12 times, fetching the information required from each individual array, and generate the templates to show all of the information.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/65ea4ba824007b6547fddb21fbb11e20/href">https://medium.com/media/65ea4ba824007b6547fddb21fbb11e20/href</a></iframe><p>In order to retrieve the calling points, another ajax request was made to another API. The URL to retrieve the service information is generated using the service ID. This information is retrieved using the API used to get the service information. I used datasets to store the service ID in the “Show More” button. A click event is then added to the button. When the button is pressed, I am able to use the service ID by setting up a variable that takes the information from the dataset then creates a dynamic URL using the service ID. On line 13, the targetServiceId variable is the variable that is used to access the dataset that provides the service ID.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/00dcf0b7c4d4ab51dd3d14262d747594/href">https://medium.com/media/00dcf0b7c4d4ab51dd3d14262d747594/href</a></iframe><p>I have tried to explain the code in as consise and succinct way, however In total the script.js file has over 500 lines of code. The code is also available on Github and can be found at <a href="https://github.com/norrisollie/final-trackk"><strong>https://github.com/norrisollie/final-trackk</strong></a></p><p>I have commented the code clearly, with each comment explaing what each line of code does. I always make an effort to comment code, as it can be easier for people to understand and see what each line does. I have also spaced it so it is clear and understandable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44abeab2ede" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Development Process — HTML]]></title>
            <link>https://medium.com/@norrisollie/the-development-process-html-d23659f0c0ef?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/d23659f0c0ef</guid>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 21:19:58 GMT</pubDate>
            <atom:updated>2021-02-18T21:47:03.798Z</atom:updated>
            <content:encoded><![CDATA[<p>I started off the development process by downloading Skeleton and Bootstrap, both are CSS frameworks designed to make it easier to create and develop responsive website. I wanted to try to use a framework as it makes it easier to develop responsive websites, without having to create your own media queries to deign it to fit on to mobile devices. In addition, it also provides some consistent styling for elements, such as input fields, forms and buttons. Skeleton is a lot smaller and simpler, whereas Bootstrap has a lot more features. It also relies on using jQuery for certain plugins.</p><p>After playing around and experimenting with both CSS frameworks, I felt that it would be easier to not use one. Whilst they are useful, I felt that using frameworks for a small project was unnecessary and did not provide much use for my final major project. If the design was more complicated and used more elements, I would consider using a CSS framework.</p><h4><strong>Folder Structure</strong></h4><p>I started the development process by creating a folder for Track, in the folder I created three files:</p><ul><li>index.html — This file contains all of the HTML elements.</li><li>style.css — This file contains all of the CSS code</li><li>script.js — This file contains all of the JavaScript code</li></ul><p>These three files are the most basic components needed to create a website. After creating these three files, I created a new folder called img, this folder contains all of the images required for Track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mgb0BFyzuDjjrfSz8hzhLw.png" /><figcaption>The final file structure for Track</figcaption></figure><h4>Using Normalize.css</h4><p>When I was experimenting and playing around with Skeleton and Bootstrap, one of the files that comes with both is a file called normalize.css. Normalize is a small CSS file that makes it easier to develop websites that work consistently across major browsers. It helps tackle to small inconsistencies that occur on all major browsers and render elements consistently across all browsers.</p><h4>Using MAMP/MAMP Pro</h4><p>When I started to begin writing the HTML, CSS and JavaScript, it quickly became apparent that I would need to find a tool that allows a secure connection. Initially, I was going to work on Track by opening the index.html file through the browser to see what it would look like on an actual browser. I quickly realised that this was not possible, as geolocation requires a secure connection. Despite the file being local, there was no way to circumvent this restriction. After looking online at ways to be able to browse securely, I downloaded a trial of MAMP Pro. MAMP Pro allows you to create a local server to host a website on. It also allows you to create custom local domain names, such as name.dev or name.app which makes it easier to access the project from the browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EDPz-gwru_3GhhT5ttFn1Q.png" /><figcaption>The hosts panel on MAMP Pro, where you can set up and create custom local domains</figcaption></figure><p>MAMP Pro allows you to create “self signed certificates”, this makes it possible to work on websites that require the use of geolocation, as it tricks the browser in to thinking that there is a secure connection.</p><h4>The Index File</h4><p>The first file I created, was the index file. This file typically contains all of the HTML code required for a browser to be able to render elements in the browser window.</p><p>The main parts of a HTML file are:</p><h4>HTML tags</h4><ul><li>The HTML tag will typically contain all the elements of a web page within the &lt;html&gt;&lt;/html&gt; tags.</li><li>The browser must know what version of HTML the page has been written in, to do so you must declare the version by adding the &lt;!DOCTYPE&gt; declaration before the start of the &lt;head&gt; tag.</li></ul><h4>Head tags</h4><ul><li>The head tag is typically used to contain elements such as stylesheets, scripts, page titles and meta elements.</li><li>In HTML 5, you do not need to have a &lt;head&gt; tag, however it is good practice to include head tags as it can make it easier for humans to read the document.</li><li>The only element that is required for the &lt;head&gt; tag, is the &lt;title&gt; tag. If this tag is not included, the HTML would be invalid.</li><li>The &lt;meta&gt; tags are used to provide data about the HTML document. They are not visible to the page, though they are useful to browsers and search engines to provide information about the document, such as the description, author and other information.</li><li>The Meta viewport tag is important, as it is required to be able to use responsive layouts on mobile devices. Without this tag, a page will render how it would normally look on a large display.</li><li>The &lt;title&gt; tag is used to name the page, this name is typically displayed in the browser tab or window frame.</li><li>The &lt;link&gt; tag is typically used to link the HTML document to a CSS document to style elements. It can also be used to specify a favicon, a small icon that is displayed in the browser.</li><li>The &lt;script&gt; tag is used to link the HTML document to a script file, such as JavaScript. Whilst they can be placed within the head tag, it is usually placed at the bottom of the page within the body tag at the bottom as this loads all of the elements first before initialising the script.</li></ul><h4>Body tags</h4><ul><li>The body tag typically contains all visible elements within a page.</li><li>The body tag should always come after the head tag, and must be closed within the html tag.</li></ul><p>The typical index file for could look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7f4a599084ef7ddf91999807df31472/href">https://medium.com/media/e7f4a599084ef7ddf91999807df31472/href</a></iframe><p>When I create a HTML document, I typically include all elements within a DIV container. This makes it easier to wrap all of the elements within a single DIV and then use CSS to position the elements when neccessary.</p><p>For small elements, such as text, headers, images, forms and other similar elements, I also wrap these in their own containers as it makes it the code easier to read. It also makes it easier to style the elements. For example, instead of defining a class for all p elements in a DIV wrapper, I can use one CSS declaration to style all P elements within a certain wrapper.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d3d734d41baad88aa91318dbf5247142/href">https://medium.com/media/d3d734d41baad88aa91318dbf5247142/href</a></iframe><ul><li>All elements in the body tags are contained within a container DIV.</li><li>Elements that are to do with the logo are contained within the logo wrapper</li><li>Elements to do with forms and input elements are contained within a form wrapper.</li><li>The closest station section elements, such as the buttons and title of the section are contained within the closest station wrapper.</li><li>The search results are contained within the results container, they are also contained within a wrapper due to the way the results are styled and displayed.</li></ul><p>I like to write HTML that is simple and logical, and where possible to wrap all related elements within a container or wrapper. All of my HTML code can be found on Github at <a href="https://github.com/norrisollie/final-trackk"><strong>https://github.com/norrisollie/final-trackk</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d23659f0c0ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with APIs]]></title>
            <link>https://medium.com/@norrisollie/working-with-apis-c13a7ab2a633?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/c13a7ab2a633</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 19:28:21 GMT</pubDate>
            <atom:updated>2017-06-13T19:28:21.124Z</atom:updated>
            <content:encoded><![CDATA[<p>In order to get the train times and closest stations, I need to find APIs that provided me with this data.</p><p>There were a many APIs available for me to use to get this information, however there were a some issues that I faced when trying retrieve the information from the APIs. This meant I had to find ways where I could get the information I needed, whilst getting around these issues.</p><p>As I wanted to use the Node JS platform, these issues would not have been a problem. Unfortunately as I was unable to use the platform to develop my web application, I had to resort to using front end JavaScript instead. Whilst this was not ideal, I wanted to create something that worked and would be useful, even if this method was not necessarily best practice.</p><p>The issue with using front end JavaScript is that there are restrictions in place when using AJAX requests to retrieve data from APIs that are not on the same domain as the domain you are calling the request from. This means that the data is blocked. The only way to get around this problem is to ensure that the API is CORs enabled (Cross Origin Request). This was difficult as this has to enabled by the owner of the API. This meant a lot of APIs were out of reach as most APIs do not allow cross origin requests. There are ways to get around these issues, such as by creating a proxy server to make the API think that it is being requested on the same domain. Another way to circumvent this issues, is by using jQuery and by using JSONP. I did not want to use jQuery as I wanted to write the application using Vanilla JavaScript instead. This method is also unreliable as it only allows certain types of requests, and it not best practice.</p><p>I spent a long time looking online to find APIs that do not have these restrictions, and found two APIs that provided me with train time information. The first API I came across was TransportAPI. This provided me with all of the information I needed, however I soon realised that this API was not fit for purpose as it lacked some details that the official National Rail API provided.</p><p>I then came across a project called Huxley, which is a JSON proxy for the official National Rail API. This project made the development of Track much easier. The National Rail API is a SOAP API, which means that instead of returning JSON data, it uses XML, which is not easy to work with. In addition, the official API is also CORs enabled. The Huxley project converts the XML to JSON, making it easier to work with the data, it is also CORs enabled, meaning I did not have to worry about cross origin request issues.</p><p>I had hoped to use the CityMapper API to provide users with the time it would take to walk to each of the nearest stations, however this API is not CORs enabled. I also looked at alternative APIs, such as Google Distance Matrix and MapQuest, but all three APIs were not CORS enabled.</p><p>To find the stations closest to the user, I used an API called NaPTAN (National Public Transport Acess Nodes), which is an API that provides a list of closest stations, based on a set of coordinates. This API provides a list of railway stations, as well as other methods of transport. The stations at the top are the stations closest to the coordinates specified, and the stations at the bottom of the list are the stations furthest from the coordinates specified.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c13a7ab2a633" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Flow]]></title>
            <link>https://medium.com/@norrisollie/user-flow-71b846eda217?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/71b846eda217</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 16:28:07 GMT</pubDate>
            <atom:updated>2017-06-13T16:28:07.451Z</atom:updated>
            <content:encoded><![CDATA[<p>User flows are also a useful part of the development process, as it allows you to see potential ways that users will enter and ‘flow’ through a website or application. It also provides you with the opportunity to see all the pages you will need to design and develop once the flows have been created.</p><p>I started the design process by creating user flows. I looked at my minimum viable product and decided to create my user flow with this in mind. I created a user flow demonstrating how a user would conduct a search for train times from a certain station.</p><p>Whilst I did want to create user flows for the whole application and the features I wanted to include, I felt it was best to create a user flow that focused on what I wanted for the minimum viable product. If I was to continue working on this project after, I would consider creating a user flow with all of the functionalities and features I wanted to include.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ve66Q_yhINe3H3b_1DXUdw.jpeg" /></figure><p>Whilst the user flow is quite simple and basic, I did want to focus mainly on the development side of things, as opposed to the design and user experience. In hindsight I feel that I should have created the user flow with all features and functionalities as this would have shown my ability to show good user experience design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71b846eda217" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireframing]]></title>
            <link>https://medium.com/@norrisollie/wireframing-5670b260451f?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/5670b260451f</guid>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 13:19:36 GMT</pubDate>
            <atom:updated>2017-06-13T13:19:36.693Z</atom:updated>
            <content:encoded><![CDATA[<p>The next stage of the design process for Track, was to start creating some rough sketches and wireframes. Wireframes are useful as they are easy to create and can be used to quickly come up with some ideas for how an application or website could be designed. They can also be used to conduct some early user testing, giving some useful feedback early in the design process. Tackling issues with user experience early in the process is important as changed can be made quickly and easily. If user testing is not conducted early, it can be quite time consuming and costly to make changes to the design.</p><p>There are two main types of wireframes. The first type are usually called low fidelity wireframes, these wireframes are typically made using pencil and paper. They are quick and easy to make, and changes can be made quickly if something is not right and needs to be changed or rethought. The second type are usually called high fidelity wireframes, these wireframes are typically made digitally. They can be created using software such as Photoshop or Sketch.</p><p>Wireframes can also be created using HTML and CSS to create a skeleton of how it might look. The advantage to using HTML and CSS is that creating it using code can mean that it easier to design it with the browser in mind, as opposed to creating it digitally and trying to convert the digital version in to code.</p><p>Early high fidelity wireframes will also typically not include any colours as it is about focusing on the design and placement of elements. After the design has been finalised, these digital wireframes could then also include colours, textures and other aesthetics.</p><p>My final major project focused more on the development side, so I didn’t spend a lot of time creating wireframes and testing, however I did create some rough wireframes to help me come up with a potential design for my web application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EmDh2HfZ06Z-hpMuQ41WOQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VTVpRP3h9rJPG9Tf8hcHxw.jpeg" /><figcaption>The first set of wireframes</figcaption></figure><p>The first set of wireframes I created for Track were created under the assumption that I would be developing my final major project as a mobile application. I found that designing it as an application was quite a struggle, although I knew I was not going to be creating it as a mobile application, I felt that it would have to be designed as a mobile application, even though it was a web application instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bkJhj05eFwBKGcJiQ6wTFA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HRZH3ID3uY1gH7duTxOHuQ.jpeg" /><figcaption>The second set of wireframes.</figcaption></figure><p>I quickly decided to scrap the first set of wireframes and changed the whole idea I had for my web app. I decided to create some new wireframes with the idea that I would be designing it for the browser. The second set of wireframes were much more successful as I was happy with the outcome after conducting some informal user testing with friends and family.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5670b260451f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with Node.JS]]></title>
            <link>https://medium.com/@norrisollie/working-with-node-js-creating-the-app-js-file-1eff8cbb4e51?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/1eff8cbb4e51</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[npm]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Tue, 23 May 2017 16:04:38 GMT</pubDate>
            <atom:updated>2017-05-23T19:52:27.648Z</atom:updated>
            <content:encoded><![CDATA[<p>Prior to the start of the final major project unit, I’d never found the need to use and understand how the Node.JS platform works. I have used the platform before, but only ever knew the basics… where to write the HTML, CSS and JavaScript. I never needed to delve in to the deep, dark depts of the app.js file; the file which powers the whole application.</p><p>I looked at a number of different websites, tutorials and videos to begin to gain a better understanding of how Node.JS is used and how to start to create a Node.JS application.</p><h4>Starting a Node.JS project</h4><p>To create a new node application, you will need to create a folder for your project. This folder contains all the necessary folders and files for the application to work.</p><p>Below is the file/folder structure of a basic Node.JS application.</p><pre>nodeapp<br>|<br>|_package.json<br>|<br>|_node_modules<br>|<br>|_public<br>| |_css<br>| | |_style.css<br>| |<br>| |_js<br>|   |_script.js<br>|<br>|__views<br>|   |_stylesheets<br>|   | |_style.styl<br>|   |<br>|   |_layouts<br>|   | |_layout.handlebars<br>|   |<br>|   |_partials<br>|   | |_nav.handlebars<br>|   | |_container.handlebars<br>|   | <br>|   |_pages<br>|     |_index.handlebars<br>|     |_pageone.handlebars<br>|     |_pagetwo.handlebars<br>| <br>|___routes<br>    |_index.js<br>    |_pageone.js<br>    |_pagetwo.js</pre><h4>Creating a folder for the Node.JS application</h4><ol><li>Open the Terminal application</li><li>Navigate to the folder containing all of your projects, using the cd command. e.g cd ~/documents/projects/</li><li>Create a new folder in the projects directory for the application, using the mkdir command. e.g mkdir &lt;project name&gt;</li><li>Navigate to the newly created project folder, using the cd command. e.g cd ~/documents/projects/&lt;project name&gt;/</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kEYD6VAM_fRhPlPPUaRxzg.png" /></figure><p>You have now created a Node project folder in the directory containing your projects.</p><h4>Creating a package.json file</h4><p>The next step is to generate a file called package.json. This file is used to store information, such as the name of the project, version number, the applications entry point, a repository url, name of the author and license type. This file also contains a list of all the npm modules (known as dependencies, that are required for the application to work.</p><ol><li>Firstly, ensure that the Terminal window is pointing to the project directory. e.g. cd ~/documents/projects/&lt;project name&gt;</li><li>In the Terminal window, use the command npm init to generate a package.json file.</li><li>You will now be asked to input some information to generate the file. For each input, enter the required information and then press enter to move to the next field.</li></ol><h4><strong>What does the package.json file contain?</strong></h4><ul><li><strong>Project</strong> <strong>Name</strong>: by default, the name of the project is the name of the project folder. It can be changed, though it is best to use the default name. The name must be url friendly.</li><li><strong>Version</strong>: by default, the version number is 1.0.0. It is best to use the default version number. Version numbers should use the major.minor.status format.</li><li><strong>Description</strong>: you should enter a description of the project you are working on. It can be left blank.</li><li><strong>Entry Point</strong>: the entry point is the file used to configure the application. It contains the code required for the application to work, containing the server, requires, routes and middleware code. By default, the entry point is usually set asindex.js. It is best to change the file to app.js as this is the file name typically used by most Node developers. You can use any name for the entry point, but it is best to change it to app.js as this name is typically used by most developers.</li><li><strong>Test</strong> <strong>Command</strong>: this field can be left blank.</li><li><strong>Git</strong> <strong>Respository</strong>: you should enter the url to the repository for the project. You can leave the field blank if you do not have a respository.</li><li><strong>Keywords</strong>: this field can be left blank.</li><li><strong>Author</strong>: you should enter your name in this field. It can be left blank.</li><li><strong>License</strong>: this field specifies the license for the project. By default it uses an ISC license. It is best to leave the default license.</li></ul><p>Once all the information has been entered, you will be asked whether all the information is ‘ok’. You should enter the word ‘yes’ and press enter to create the package.json file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CaYGP_yK29OmqHzXmRlF0Q.png" /></figure><h4>Installing the Express Web Framework</h4><p>I will be using the Express Web framework, a framework used to make the development of mobile and web apps quick and easy. To install the Express Web framework:</p><ol><li>Ensure the directory is pointing to the project’s folder, using the cd command.</li><li>Enter the command npm install express --save to install the module to the node-modules folder. This folder contains all the required modules for the application to work. The --save flag is used to add the module to the list of dependencies in the package.json file.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DGBT3PusohmtmxvpDAQ5hg.png" /></figure><p>The Express framework has now been installed, the next step is to create the folders and files required for the application to work.</p><h4>Creating the Files and Folders for the Project</h4><p>When using the Express framework, there are two ways to create the folders and files required for the application. You can create the individual files and folders manually, or you can use a module called Express Generator, which will automatically create the required files and folders.</p><h4>Using Express Generator</h4><ol><li>Enter the command npm install express-generator -g in the Terminal window. The -g flag specifies that the module should be installed globally. This means that the module can be used on any project. It does not matter what directory the Terminal window is pointing to.</li><li>When installing modules globally, you may recieve an error saying that permission has been denied. If this is the case, use the command sudo npm install express-generator -g. This command runs the command as an administrator. You may need to enter the administrator password to install the module.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6zMVpSQar4aGOx-9xxCmfA.png" /></figure><h4>Running the Express Generator</h4><ol><li>To generate the files and folders for the project, you will need to enter the commandexpress --view=&lt;view engine&gt; --css=&lt;css engine&gt;.</li><li>Where it says &lt;view engine&gt;, you will need to specify the view engine you wish to use in the application. By default, the view engine is set as Jade. Other view engines include Handlebars, EJS, Pug and Mustache.</li><li>Where it says &lt;css engine&gt;, you will need to specify the CSS engine you wish to use in the application. By default, no CSS engine is used and you will have to use .css files insead. Examples of CSS Engines include Less, Sass and Stylus.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gNG8YOpAcramExaoZq55Wg.png" /></figure><p>4. Once you have run the command, as well as specifying what engines you wish to use for the application, you will need to install the dependencies the application relies on to work. Use the cd ~/ command to change the directory to the project directory, and run the command npm install to download the dependencies.</p><p>You have now created all the files and folders required for a Node.JS project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RTInXpWdpGnmrP1eIXV4sA.png" /></figure><h4>What is an Engine?</h4><p>Applications can sometimes have thousands of lines of code, making it difficult for developers to understand the code if it is all contained within one single file.</p><p>View engines work by allowing applications to be written in separate files, with each files containing manageable chunks of code that can be understood and easily read by humans. An engine will then take the files required to generate a page/css and compile it in to code, such as HTML or CSS that can be understood by the browser.</p><h4>Creating the Folder and File Structure Manually</h4><p>In some cases Express Generator may not be suited to the project, and it may be necessary to create the folder and file structure manually, depending on the needs and requirements of the project.</p><h4><strong>Creating the App.js File</strong></h4><ol><li>Open up a text editor and create an app.js (or the name of the file you specified as the entry point for the application).</li><li>You will need to define the Express module, to do so, add the following code at the top of file: var express = require(&#39;express&#39;). All modules must be defined before they are used, otherwise an error will occur. Most modules are defined right at the top of the app.js file.</li><li>You will need to define the path module, to do so, add the following code beneath the Express Variable: var path = require(&#39;path&#39;). The path module is used to work with file and directory paths.</li><li>To support the Express Handlebars view engine, you will need to install the module. In the terminal window, change the directory to the project’s folder using the cd ~/ command. Enter npm install express-handlebars --save to install the module and save the module to the dependencies.</li><li>You will need to define the Express Handlebars view engine, to do so, add the following code beneath path variable: var exphbs = require(express-handlebars).</li><li>The support using a CSS engine, you will need to install the module of the engine you will be using. I will be using Stylus as the engine supports the use of Node.JS. To install the stylus module, enter the command in the Terminal window: npm install stylus --save.</li><li>You will need to define the Stylus CSS engine, to do so, add the following code beneath the Express Handlebars variable: var stylus = require(&quot;stylus&quot;).</li></ol><p>The app.js file should look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/30720cdf84b64300f83671d8679d8ef5/href">https://medium.com/media/30720cdf84b64300f83671d8679d8ef5/href</a></iframe><h4>Defining the routes in the app.js file</h4><p>The next stage of the creation of the app.js file, is to define the home page and other pages of the application. I will be creating a home page, as well as two example pages for the application. These variables will then define the URL endpoints, required to access the page. e.g http://project.com/&lt;endpoint&gt;</p><ol><li>Firstly, point the Terminal to the project’s root using the cd ~/ command.</li><li>Use the mkdir command to create a folder called routes.</li><li>In the routes folder, create three files called index.js, pageone.js, and pagetwo.js.</li><li>At the moment, you will not need to do anything with these files yet.</li></ol><p>The next step is to define and require the three files in the app.js file.</p><ol><li>To define the index.js file, which is used for the homepage, add the following code beneath the variables requiring the modules: var routes = require(‘./routes/index’);.</li><li>To define the pageone.js file, which is used for the homepage, add the following code beneath the variables requiring the modules: var routes = require(‘./routes/pageOne’);.</li><li>To define the pagetwo.js file, which is used for the homepage, add the following code beneath the variables requiring the modules: var routes = require(‘./routes/pageTwo’);.</li></ol><h4>So far, the app.js file should look like this:</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb997dc07940fdd23df9ab7915a47ccc/href">https://medium.com/media/cb997dc07940fdd23df9ab7915a47ccc/href</a></iframe><h4>Initialising the Express Application</h4><ol><li>Beneath the variables defining the routes to the pages, add the following code to initialise the Express application: var app = express();</li></ol><p>The app.js file should look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/51d7ece8576059d0f20c4875a6ffd67c/href">https://medium.com/media/51d7ece8576059d0f20c4875a6ffd67c/href</a></iframe><h4>Setting the view engine</h4><p>The next step is to set up the views folder, and specify the view engine we will be using for the application. I will be using Handlebars as the view engine for the application.</p><ol><li>Firstly, point the Terminal to the project’s root folder using the cd ~/ command.</li><li>Use the mkdir command to create a folder called views.</li><li>Inside the views folder, create the following folders using the mkdir command: pages, layouts, partials and stylesheets. The purpose of these folders will be explained later in this post.</li></ol><h4>Setting the View Engine</h4><p>The next step is to set up the view engine that will generate and render the HTML for the pages. I will be using the Handlebars view engine for this application.</p><ol><li>Firstly, point the Terminal to the project’s root folder, using the cd ~/ command.</li><li>Use the mkdir command to create a folder called views.</li><li>Next, we need to set the location of the views folder using: app.set(‘views’, path.join(__dirname, ‘&lt;location of pages directory&gt;’));<br>This sets the location of the folder wherethe files for the content of each page will be.</li><li>Next, we need to specify the engine we well be using to generate and render the views, using: <br>app.engine(‘&lt;view engine&gt;’, exphbs({defaultLayout:’&lt;location of default layout&gt;’, partialsDir: __dirname + ‘&lt;location of partials directory&gt;’}));<br>This specifies the view engine, sets the location of the default layout, and sets the location of the partials directory.</li><li>Finally, we need to specify the view engine we’ll be using.<br>app.set(‘view engine’, ‘&lt;view engine&gt;’);</li></ol><p>The app.js file should now look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6d3668f2c5af030ee56e57047093aa71/href">https://medium.com/media/6d3668f2c5af030ee56e57047093aa71/href</a></iframe><p>We have now finished setting up the view engine, specifying the location of the views directory, specifying the location of the layout file, the partials directory, and specifying what view engine the application will be using.</p><p>The views folder should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-tQMc6xR5Pkmdl2nip5mnA.png" /></figure><h4>Setting up the Stylus Middleware</h4><p>The next step is now to set up the Stylus middleware. The stylus middleware is used to specify the location of .styl files, and where they should be located when they have been compiled and converted in to CSS.</p><p>The code below is what the Stylus Middleware should look like, it should be place beneath the code that specifies the view engine.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bf912e15e63c9296b87a23d45868c55/href">https://medium.com/media/5bf912e15e63c9296b87a23d45868c55/href</a></iframe><ul><li>Line 2: this line specifies that we should use the Stylus middleware</li><li>Line 4: this line specifies the source location of the .styl stylsheets</li><li>Line 6: this line specifies the destination location of the compiled CSS stylesheets, which is in the public folder.</li><li>Line 8–11: these lines are the function used to compile the .styl files to .css files.</li></ul><p>The app.js should now look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f966c748bcac9d899da3f1ef1baa19ea/href">https://medium.com/media/f966c748bcac9d899da3f1ef1baa19ea/href</a></iframe><h4>Setting the Static (public) Directory</h4><p>The next step is to create a folder called public. The public folder is the only folder that is accessible to the browser, this folder will usually contain files such as compiled CSS, JavaScript files for the front-end and images or video.</p><ol><li>Use the cd ~/ command to point to the project’s root file.</li><li>Use the mkdir command to create a directory called public</li><li>In the app.js file, beneath the Stylus middleware, we need to use the app.use object to specify the location of the public folder. Add the following piece of code:<br>app.use(express.static(path.join(__dirname, ‘&lt;location of public folder&gt;’)));</li></ol><p>The app.js file should now look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9aee5b0a79907b826dfd70ddbe1065a3/href">https://medium.com/media/9aee5b0a79907b826dfd70ddbe1065a3/href</a></iframe><h4>Configuring Routes Middleware</h4><p>The next stage is to use the app.use object to configure the routes and specify the end point to access certain pages.</p><p>For each page, including the home page we need to add the following code for each page of the application:</p><p>app.use(‘&lt;end point&gt;’, &lt;variable of route&gt;);</p><p>For example, if I wanted the user to access a page at http://website.com/page, I would neet to set the end point to page and the variable would be the variable I specified for the page near the top of the app.js file.</p><p>For example, if I defined the page as a variable called page, the code would be app.use(‘/page’, page);</p><p>An app.use object is required for every page in an application.</p><h4>Setting the Server Port</h4><p>The final step we need to do before the application can run, is to specify the port number it will be accessing.</p><ol><li>At the end of the app.js file, add app.listen(&lt;port number&gt;)</li></ol><p>Where it says &lt;port number&gt;, you will need to specify a number between 1000 and 9999. For example, if the port is set as app.listen(9000), when the application is started, you would access the application by using the url localhost:9000</p><p>The final app.js file should look like the following:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/91553d903dde069677645461e18c70ba/href">https://medium.com/media/91553d903dde069677645461e18c70ba/href</a></iframe><h4>Configuring Individual Page Routes</h4><p>The next step is to open up the index.js, pageone.js, and pagetwo.js files in a text edior. These files contain code that fetch the required files in the view folder and compile and render the code in to HTML that can be understood by the browser.</p><ol><li>Open up the index.js, pageone.js, and pagetwo.js files in the routes folder.</li><li>Define and require the Express module in each file. Add the following code at the top of the file. var express = require(&#39;express&#39;);</li><li>Define and require the Express router beneath the Express module. Add the following code: var router = express.Router();</li><li>You will now need to use the router.get function to fetch and render the required files to compile and render them as HTML in the browser. Add the following code beneath the router variable:</li></ol><pre>router.get(&#39;&lt;url endpoint&gt;&#39;, function(req, res) {</pre><pre>res.render(&#39;&lt;name of file in views folder, e.g &#39;index&#39;&gt;&#39;);</pre><pre>});</pre><p>5. Finally, you need to add the following code beneath the router.get function: module.exports = router;</p><p>Below is an example of a basic routes file for a page. Each individual page require a file in the routes folder. All files contain the same code, with the only changes being the url endpoint in the router.get function and the name of the file in the res.render object.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7bc614f801e4a30d92348acb4c89b0f5/href">https://medium.com/media/7bc614f801e4a30d92348acb4c89b0f5/href</a></iframe><h4>Creating files in the Views Folder</h4><p>Pages in a Node.JS and Express web application use a folder called views to store all the files required to generate the pages required for an application.</p><p>There are four folders within the views folder that are used to generate and render the pages for an application. These are stylesheets, layouts, pages, and partials.</p><h4>What will these folders contain?</h4><p><strong>Layouts — </strong>this folder will contain the layout for each page. Typically, the files contained within this folder will be the code that is the same on every page. For example, it will contain the &lt;head&gt;, &lt;header&gt; and &lt;footer&gt; tags, as these sections of the page are the same on every page of the application. The files contained within this folder will also have the .handlebars extension. Below is an example of a layout.handlebars file.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0dc8cc8ecc38b4ce3fc2a6e94ec97671/href">https://medium.com/media/0dc8cc8ecc38b4ce3fc2a6e94ec97671/href</a></iframe><p>The {{&gt; container }} and {{&gt;nav}} tags are used to include partials. The {{body}} tag will include the body content of a page. This file typically is stored in the pages folder, and contains the content of a page.</p><p><strong>Pages</strong>: this folder will contain all of the content for each of the pages. The files contained within this folder will have the .handlebars extension. These files will contain just the content that will be displayed on the page.</p><p>Below show a couple of examples of what may be included in the files in the pages folder.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/177b5e1c444b9e917164856dd3b723b1/href">https://medium.com/media/177b5e1c444b9e917164856dd3b723b1/href</a></iframe><p><strong>Partials</strong>: this folder contains the partial sections of the layout, such as the navigation and side bar. Partials are used to separate code in to manageable chunks that are easy to understand and read.</p><p>Partials are included in to the layout.handlebars file, using the following code: {{&gt; &lt;file name of partial file e.g section.handlebars }}</p><p><strong>Stylesheets</strong>: this folder contains all the stylesheets required for the application. The stylesheet files are not .css files, they are .styl files. A command can be used to compile the .stylus files in to .css files that can be understood by the browser.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1eff8cbb4e51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technologies I will be using for my FMP]]></title>
            <link>https://medium.com/@norrisollie/technologies-i-will-be-using-for-my-fmp-34a681eae049?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/34a681eae049</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Thu, 18 May 2017 16:52:30 GMT</pubDate>
            <atom:updated>2017-05-18T16:52:30.601Z</atom:updated>
            <content:encoded><![CDATA[<p>The main purpose for my final major project is to develop my skills and learn how to use technologies that will be useful in the world of work.</p><p>I have been looking at various technologies that I could use to build and develop my web application for my final major project.</p><p>As I am already familiar with using JavaScript for the front end, with this in mind I have decided to take a look at using the Node JS platform to build the application. I will be using Node JS as a back end for the application, and use HTML, CSS and JavaScript for the front-end.</p><p>I have decided to use this platform as it seems to be a popular platform to use to run, build and develop applications. It seems sensible to look at learning how to develop applications using the platform.</p><p>Node JS is used in conjunction with NPM, a JavaScript package manager for the JavaScript Language. NPM provides developers with ‘modules’. These modules are small pieces of reusable code that provide functions and features to add to your application, as well as modules that can simplify the development process.</p><p>The application will make use of Express JS, a web framework which makes it easier to develop web and mobile applications.</p><p>I will be using the CSS pre-processor Stylus as I am already familiar with how to write Stylus code. In addition, it was also designed and developed to be used with Node JS, whereas some other popular pre-processors, such as SASS were designed and developed to be used with the Ruby language.</p><p>CSS pre-processors are typically used to write CSS for larger applications that have lots of lines of CSS code. The syntax for most pre-processors are largely similar as CSS, however they also have a lot of useful features, such as nesting, variables, functions and much more.</p><p>In order to make the development process quicker and easier, I will be using Grunt, a JavaScript task runner which is used to automate tasks that are repetitive and time consuming. It works in a similar way to the NPM package manager, allowing you to download plugins through the NPM package manager to provide reusable code to automate tasks.</p><p>Some examples of grunt plugins are:</p><h4>JSHint</h4><p>This plugin is used to check whether there are any errors within the JavaScript files.</p><h4>Watch</h4><p>This plugin is used to look for any changes in a file, for example when you change a piece of code it might run a task that restarts the Node JS server.</p><h4><strong>Stylus</strong></h4><p>The stylus plugin is used in conjunction with the Stylus pre processor, and is used to automatically compile the stylus files in to CSS files that can be read and understood by the browser.</p><h4>Concurrent</h4><p>This plugin is used to run certain tasks at the same time, such as ‘nodemon’ and ‘watch’. For example, when a file has been modified and saved, concurrent would run the watch task and the nodemon at the same time, looking for the changes and then restarting the Node JS server.</p><p>Throughout the development process, it is expected that I will be using more modules, depending on the needs and requirements of the application.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34a681eae049" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Track — Minimum Viable Product (MVP)]]></title>
            <link>https://medium.com/@norrisollie/track-minimum-viable-product-mvp-df28e01de036?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/df28e01de036</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Wed, 03 May 2017 09:38:44 GMT</pubDate>
            <atom:updated>2017-05-18T14:27:54.609Z</atom:updated>
            <content:encoded><![CDATA[<p>When you are devloping a product, a good starting point is to come up with the miniumum viable product. The minimum viable product could simply be just a list of features that you want to include on the website or application.</p><p>It’s good practice to come up with an MVP as you are able to focus on designing and developing the most basic features the application or website will need to function. Once you have the basic idea for your application or website designed and developed, you are then able to begin to add the more advanced features of the website or application.</p><p>A minimum viable product is not necessarily a finished product, but its a starting point to start building an application that is functional and works. The idea then is to begin to test on real people. With the feedback, you then change the application based on the feedback you recieved when conducting user testing.</p><p>My final major project will enable to me to look at technologies that I have not used and worked with before, and begin to learn how to use it. I will be creating a number of versions of the application, each update will add a new feature and/or include new technology that I have managed to learn.</p><p>In my second year, I received some good advice from a guest lecturer we had for one of the units. His advice was that when you are developing an idea you have for an application, website or whatever… it is best to start off small and simple, and then gradually add the more complicated and dificult to develop features.</p><p>With this advice in mind, I have decided to start off by developing the most important feature of the app; the ability to search for live train timetables.</p><p><strong>Version 1 </strong>— Would be the minimum viable product.</p><ul><li><em>The ability to look and search for live train timetables</em></li><li><em>The ability to look at service issues, such as delays, work and cancellations</em></li></ul><p><strong>Version 2</strong> — would expand on version 1, and include:</p><ul><li><em>The ability for users to register for an account</em></li><li><em>The ability got users to set home, work and favourite stations</em></li></ul><p><strong>Version 3 </strong>— Would expand on version two, and include:</p><ul><li><em>The ability for users to set up and receive disruption alerts</em></li><li><em>The ability for users to see and submit crowding information</em></li><li><em>The ability to see a breakdown of how often each train service is on time, late or cancelled</em></li></ul><p>The next stage of the development process, is to begin to draw some basic wireframes using paper and pencil, this will give me some ideas of how I could present the information to users. This will also allow me to conduct some user testing to see whether users understand how to use the web app.</p><p>I will also be looking at some potential coding languages and technologies that will be used to develop the web application.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df28e01de036" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What have I found from doing competitor analysis?]]></title>
            <link>https://medium.com/@norrisollie/what-have-i-found-from-doing-competitor-analysis-8d0bdd8cb0dc?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d0bdd8cb0dc</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 14:25:47 GMT</pubDate>
            <atom:updated>2017-04-27T14:25:47.478Z</atom:updated>
            <content:encoded><![CDATA[<p>By conducting competitor analysis, I’ve taken a look applications that are similar to what I will be designing an developing for my final major project.</p><p>I have drawn up a list of features that I would like to add to Track, the application I will be designing and developing for my final major project.</p><p>These features I have decided to include are based on what I think works well in the applications I have looked at and reviewed, and what I think would work well in my application. From this, I will be drawing up a “Minimum Viable Product”. The minumum viable product is the starting point for designing and developing an application, and usually consists of the features that an application needs to be of use to the user.</p><p>Some of the features I want to include within Track, but not neccesarily be in my minimum viable product are:</p><h4>The ability for users to log in</h4><ul><li>This is an important feature, as I will be making the prototype as a web app, with the intention of then creating it as a mobile app, it would require a user log in to be able to save the data for the user when they use the app. In addition, two of the four applications I looked at had user log ins to extend the user experience.</li></ul><h4>The ability for users to search live timetables</h4><ul><li>This is the most important feature, as the whole purpose of the application is to design and develop a live timetable application</li></ul><h4>The ability for users to set “favourite” stations or services</h4><ul><li>This is a feature that was found on every application I looked at. This feature could also include the ability to set home and work stations.</li></ul><h4>The ability for users to see quick views of favourite stations or services on the home screen</h4><ul><li>Most applications had the ability to set favourite stations or services, in addition some applications also had quick views of their favourite stations or services, showing information about the next service, such as times and price, as well as other related information.</li></ul><h4>The ability to see quick views of any disruption (on their routes)</h4><ul><li>Most applications had some sort of quick view, with Citymapper having a quick view showing any disruption on particular routes. This would be useful to help users to quickly see whether there is any disruption,.</li></ul><h4>The ability to set disruption alerts</h4><ul><li>Disruption alerts were only obvious on the National Rail Enquiries application, however I have never used them so I don’t know if they work. One of the comments I received from the user research is that they wanted “<em>disruption alerts that work properly</em>”.</li></ul><h4>The ability to see crowding information for individual services</h4><ul><li>I asked respondents of the user survey whether crowding information would be useful, the majority of respondents agreed that it would be useful.</li></ul><h4>The ability to see how often a particular service is on time, delayed or cancelled</h4><ul><li>I asked respondents of the user survey whether being able to see a breakdown of how often a particular service is on time, delayed or cancelled. The majority of respondents agreed that this would be a good feature.</li></ul><h4>Show information about trains, such as on board facilities, carriage length etc</h4><ul><li>A number of respondents thought that the application should have information about train services, with some users asking about facilities on board like table and plugs, cafe/buffet services and carriage length.</li></ul><h4>The possibility of adding a way to collect statistics and earn badges</h4><ul><li>This feature was only found on Citymapper, however I think it could be an interesting way to encourage people to continue to use the app, however at the moment I am unsure how it could work.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d0bdd8cb0dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Citymapper — Review]]></title>
            <link>https://medium.com/@norrisollie/citymapper-review-68e0ee824741?source=rss-944d0535b428------2</link>
            <guid isPermaLink="false">https://medium.com/p/68e0ee824741</guid>
            <category><![CDATA[citymapper]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[competitor-analysis]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Ollie]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 12:51:58 GMT</pubDate>
            <atom:updated>2017-04-27T12:51:58.213Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qX2zoaQ9PuuPyTS1UIHP3A.png" /></figure><p>Citymapper is a transport planner, making it easier for its users to go from place to place. Unlike National Rail Enquiries and Trainline, it does not just focus on trains and provides journey planning for many methods of transport such as buses, trains, taxis and walking. This review will mostly focus on how the application presents information about train services.</p><p>When the user opens the app, they are taken straight to the home screen, this home screen contains all the features of the app.</p><p>The home screen features a map which shows your location, it can be enlarged to take up the full screen by swiping up or pressing on the map. When the map feature is enlarged, there are a number of buttons, each button is a method of transport. These buttons are also accessible when the map is small, but only show a few transport methods. This feature makes it easy for users to be able to see where the nearest bus stops and train stations are, in addition to other methods of transport. You are also able to save individual bus stops and train stations to your favourite, your favourites can then be saved on a map for easy access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uTJvWtmSKVPtz9yXJRcxHA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nVft-P35dHW3EfAUDA_nqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DArx2JKdlamTA66qLef_Q.png" /><figcaption>Screenshots of the map feature.</figcaption></figure><p>When a button is pressed for a method of transport, it brings up a quick view of the closest stops and stations. These quick views are different depending on the method of transport, however they mostly show information such as the name of the stop or station, the time it takes to get there from your location, the service number (for buses), the destination, the time of expected departure. For trains it also show how many minutes until the service arrives. this section also lets the user save the location to their favourites, this is done by pressing the three dots next to the name of the station.</p><p>The user is able to see more information about a particular service, however when pressed the user is taken a what appears to be a live timetable for the particular station. The user is then required to find the particular service. this section displays each service in a clear way, providing information such as the time, the status of the train, the destination, calling points, the time until the service arrives and the platform number. This section also show the most recently viewed route the user has looked at. The user is able to press on a particular service, this lets the user see the route on a map, as well as the time the train will reach each station.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9yY0SL8wGtksTmlyKuZKfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wraL-gZ2aoskRXtDiMZ9w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJ2-M2_4uJ9__kPcAz5vHQ.png" /><figcaption>Screenshots showing train services.</figcaption></figure><p>Back to the home screen, the next section to look at is the “Get Me Somewhere” feature. This feature lets the user search for a particular location and shows them how to get there using a number of different transport methods. When pressed, the section is expanded and the user is asked to enter a location. There is also a list of locations, these locations are based on ones you have saved to your favourites, recently searched locations or your home and work locations. If you have not already saved these locations, you are able to do it in this section, otherwise you are able to do so on the home screen. There is also a map view, this allows you to use an advanced search to be able to plan when you would like to leave.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LaPTul_lXi8tWUp3gNDJtg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kz5PmFPrmopXVlZS10v35A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kX6HVmbViO9SQL9UUZZWXQ.png" /><figcaption>Screenshots of the “Get me somewhere” feature.</figcaption></figure><p>When the user conducts a search, they are shown a number of methods to get to their chosen destination, such as by walking, cycling or using a taxi service such as uber. In addition there is a “suggested” method, which is the quickets method of transport. Users are able to click on their desired method of transport to be shown how to get to their destination.</p><p>When the user selects to use the trains, they are given the option to choose which service they want to get. This section shows the user the total time of the journey, including the time taken to get from their location, to the station and the duration of the train journey. It also shows the time of departure, destination and platform number. When the user has chosen their options, they will need to press go and they are given a map of their journey, this map contains all the information they need to make their journey.</p><p>You are able to use the app when you are on a journey, at the bottom of the screen on the home section, you are able to quickly access the current trip.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWBnS2R8nLkyLyrO0dbTfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jyQixVrTyV44i0Ga045DZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1x9NJdogvSFdG8t6H-hekg.png" /></figure><p>There are a number of other sections of the application that are quite useful, when you set up a home and work section you are able to quickly access the “commute” section, this shows the recommended routes to take when you either want to get to work in the morning, or get home in the evening. It is unclear whether the user is able to change the time of their commute, or whether it is based on the current time. It give users quick access to information, such as the time of service, the destination, whether it is on time and the time of arrival.</p><p>There is a “Trips” section, this section shows the most recent trips you have made. This gives you quick access to be able to make the same trip again.</p><p>There is a “Lines” section, this section quickly shows whether there is any disruption on any lines. You are also able to search and favourite specific lines, giving you quick and easy access to see whether there are any problems.</p><p>There is a “Trip Stats” section, which shows the user statistics, such as calories, trees and saved. It’s not clear as to what this means, however it is an interesting way to encourage people to continue using the app.</p><p>The app also lets you access transport maps, such as the tube map and night tube map. This saves the user from having to close the app and search the web.</p><p>Overall I think Citymapper is a really well designed application, it seems to be very reliable and works well. It is definitely aimed at commuters, however I think its main target audience is for people that do not know much about the area they are in, such as visitors and tourists as it show information for other methods of transport.</p><p>As a commuter, I would have thought that they would be able to know their way to work and back. On the other hand, it does come with a number of useful features to make it simple and easy to know when there is disruption.</p><p>It is well designed, though in some areas I think there are a number of features that are complex and the user’s journey could be simplified. Out of the three applications I have looked at so far, this is definitely the best one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68e0ee824741" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>