COMM049 Mobile Web Applications Project Handout Date: 12th October 2018 Deadline: 16:00 on Monday 19th November 2018 Written Feedback: 3rd December 2018 Assessment Weighting: 50% Academic Misconduct: Coursework will be routinely checked for academic misconduct. Your submission must be your own work. Please read the Student Handbook to ensure that you know what this means. Do not give your code to anyone else, either before or after the coursework deadline. Purpose: ……………………………………………………………………………………. 1 Problem Definition: …………………………………………………………………….. 1 Requirements (Marks): ……………………………………………………………….. 2 What to Submit: …………………………………………………………………………. 3 End of Coursework Description …………………………………………………….. 3 Purpose: The purpose of this assignment is for you to demonstrate your ability to: 1. Develop an interactive Web App; 2. Use Web Standards to implement in-browser functionality. This will involve you building a Web App using either Node.js or Ruby on Rails as the server (or an alternative not covered in the course if you prefer). The choice is yours, with no difference in marking between the choices. You will not be required to implement significant functionality on the server side as this assessment is to test your understanding of developing the responsive client side of an application. Problem Definition: Your first task is to select an application that you wish to develop. We are not constraining your choice so that you have an interest in what you are developing, and scope to make it your own: it is important that each of your applications is clearly differentiable from the other submissions. You should not, however, replicate one of the examples that have been used in the lectures! If you are finding it hard to come up with an idea, then do take a look at the Apple and/or Android App Stores for inspiration. Please Note: • Replicating, using your own software design, behaviour of your favourite App in whole or in part is acceptable; • Reusing the code-base of an existing application in whole or in part is not acceptable; • Using open source libraries or JavaScript modules to assist with building an exciting project is acceptable. Requirements (Marks): We are expecting to see a fully functional client side application. Again, we emphasise that significant back-end server-side functionality is not required – there is no need to save user registration details on the server side, for example. Note that you will not only be marked on what you have done, but also on how well you have done it. In your project, you are required to: 1. Demonstrate usage of HTML5 semantic elements: [10 marks] 2. Demonstrate usage of CSS3 animations. [10 marks] 3. Demonstrate usage of HTML5 forms with client side validation (use of native HTML5 validations, Angular.js or alternative JavaScript validations are all acceptable). [10 marks] 4. Demonstrate use of responsive design (including media queries). [10 marks] 5. Demonstrate usage of SVG or Canvases (you are free to choose which). [10 marks] 6. Ensure the application works consistently across the latest versions of: Chrome; Firefox; Opera; and one of IE or Safari. [10 marks] 7. Ensure the core behaviour of the application works when the user is offline. [10 marks] 8. Demonstrate usage of Local and Session Storage. [10 marks] 9. Demonstrate usage of the Geolocation API. [10 marks] 10. Ensure the code base is clearly structured, following the examples provided in the course. [10 marks] What to Submit: You can use whatever development tool you like to develop your application. However, you must include a ReadMe file explaining clearly how to install and run your application. To follow University of Surrey processes you must also upload an archive of your project into SurreyLearn by 16:00 on 19th November 2018. For a valid submission, you must: • Ensure the archive that you upload into SurreyLearn contains all the code needed to unpack a fully functional version of your project, and up to date links provided that capture any dependencies for correct installation and execution (if you are using Rails on the server side you only need to ensure the Gemfile is present, and don’t need to bundle the gems themselves into the archive). End of Coursework Description
