CS计算机代考程序代写 Excel android js IOS DEPARTMENT OF COMPUTING

DEPARTMENT OF COMPUTING
COSE60594 MOBILE APPLICATION DEVELOPMENT
Module leader: Jan Lawton
Assignment 1 – Worth 30% of module marks (LO 3,4)
Assignment 2 – Worth 70% of module marks (LO 1,2,4)
University Regulations
The University Regulations regarding exceptional circumstances and academic misconduct will apply. Please ensure that you are familiar with these regulations. For further information please see https://www.staffs.ac.uk/students/course-administration/academic-policies-and-regulations/home
Submissions
• All submissions are done using Blackboard
• All reports / designs must be uploaded in word or PDF format and readable on a PC
• All presentations must be uploaded in PowerPoint or PDF format and readable on a PC
• All zipped files must be in .zip format NOT .rar
• All links must be available to staff until results are released in July 2021
• Standard submission rules apply:
• Late submissions attract ZERO marks for that section
• Failure to submit on Blackboard may forfeit your opportunity to present or demonstrate your work
• Failure to attend the presentation or demonstration on time may result in 0 marks for that component of assessed work
Important Dates
Assignment 1
• Hand in date (electronically on blackboard) 22.02.21 @ 23:59
• Presentation / Demo WB 22.02.21 (dates and times on Blackboard)
Assignment 2
• Hand in date (electronically on blackboard) 16.05.21 @ 23:59
• Presentation / Demo 17.05.21 (times on Blackboard)

Learning Outcomes
On completion of this module you will be able to:
• Develop an application for multiple mobile devices, spanning different operating systems, that showcases the device’s capabilities.
• Design an application which considers the features and limitations of mobile devices.
• Critically evaluate the differences between leading mobile platforms.
• Demonstrate a systematic understanding of the processes involved in developing and publishing applications for mobile devices.
Assignment 1 – Worth 30% of the module marks (LO 3, 4)
This will be assessed in a 10-minute presentation.
You will need to hand in the following
• a copy of your presentation slides
Produce a researched and referenced presentation which addresses the following marking criteria: 

Criterion 
Marks 
• comparison of current design guidelines for Android and iOS, illustrated using relevant examples, to show how designs differ across devices and operating systems
25
• a critical evaluation of the differences between native, hybrid and PWA development approaches for Android and iOS devices
25
• discussion of the processes required to publish mobile applications using native, hybrid and PWA, on Android and iOS devices
25
Overall discretionary mark
• the thoroughness of your research
• the relevance and timeliness of your references
• the structure of your presentation
• your reasoning in any answers to questions
25
TOTAL 
100
 
Where criteria are marked out of 25, marks are allocated as follows. 
0 = no evidence of meeting criteria
1-9 = poor attempt at meeting criteria
10-11 = some attempt at meeting criteria
12-14 = average attempt at meeting criteria
15-19 = good attempt at meeting criteria
20-25 = excellent attempt at meeting criteria

Assignment 2 – Worth 70% of module marks (LO 1, 2, 4)
This will be assessed in a 20-minute demonstration/presentation.

You will need to hand in the following
• a copy of your testing documentation in a word document
• a copy of your applications in two zip files
• a link to your PWA on the internet
You have been asked to show your skills in mobile application development by building two mobile applications:
• a native application for Android built in Kotlin
• a progressive web application (PWA) built in HTML, CSS, JS and associated frameworks / libraries (i.e. no server-side technologies)
You can implement either the same application twice or two different ones. The applications will be assessed using the following criteria:
Criterion
Marks
• Android – Content and Navigation
• contain at least 4 screens
• provide suitable navigation to move between screens
• contain well-laid out and appropriate content, with no Lorem ipsum
• use suitable colours for the application and device
• have suitably formatted text of correct size using appropriate fonts
• use suitable and optimised media of the correct file format
• respond appropriately when the user changes orientation
• respond appropriately to different screen sizes and resolutions
• work offline, showing fall backs when accessing online data sources
10
• Android – Appropriate use of data handling
• getting input from the user
• passing data between screens
• reading data from an external API or JSON file
• reading data from and writing data to a local data source
10
• Android – Sensors / features
Use at least 3 of the following, ensuring they are suitable and relevant:
• camera, access to contacts, accelerometer / gyroscope, geolocation, proximity sensor, ambient light sensor, dark and light mode, use any other feature agreed with your lecturer
10
• PWA – Content and Navigation
• contain at least 4 screens
• provide suitable navigation to move between screens
• contain well-laid out and appropriate content, with no Lorem ipsum
• use suitable colours for the application and device
• have suitably formatted text of correct size using appropriate fonts
• have suitable optimised art-directed multi-resolution images on at least 1 of the pages using the correct file formats for graphics on mobile web
• a HTML form which must
• validate its elements using HTML5
• use three different input type attributes

10

• PWA – responsiveness
Conform to the definition of a progressive web application and must:
• respond appropriately when the user changes orientation
• respond appropriately to different device screen sizes and resolutions
• be able to be viewed across browsers on different mobile devices (iOS, android)
• be able to be run without the browser shell (using a web app manifest and associated files)
• be offline first when offline, showing fall backs when accessing online data sources
10
• PWA – Appropriate use of data handling
Contain appropriate data and use appropriate offline strategies including:
• reading data from an internal flat file format (JSON)
• reading data from an external API
• reading from and writing to local storage or indexedDB
• using appropriate caching strategies for all content
• showing an example of appropriate alternative content when offline for online data sources
10
• PWA – Sensors
Use at least 3 of the following, ensuring they are suitable for mobile devices:
• dark and light mode, geo-location API, persistent storage API, battery level API, use of accelerometer / gyroscope, use of network information / performance observers / device memory, camera access (via getUserMedia), general sensor API, ambient light API, store / retrieve state when there is a visibility change (app goes in the background, gets resumed, gets suspended, has previously been discarded), any other feature agreed with your lecturer
10
• Android Testing
Live android testing of the native Kotlin application on the emulator or mobile phone
• PWA Testing
Live testing of the PWA to contain all items that are needed to get a high score (over 90%) in each of the following Lighthouse and Page Speed Insights test categories (tested incognito) on all pages
• Performance, Accessibility, Best practices, SEO, PWA
• Responsiveness testing (Android Application and PWA)
• different orientations of the device
• different device emulations (from mobile phone to tablet size)
10
Overall discretionary
• quality of applications
• understanding of code
• appropriate Android design following guidelines for mobile interface design
• appropriate PWA design for a phone or tablet device
• demonstration of your mobile development skills
• your consideration of good practices for each application
• your use of innovative approaches to the problem
• robustness of the final applications
• ability to answer questions
20
TOTAL
100

Marking Criteria
Where criteria are marked out of 10, marks are allocated as follows. 
0 = no evidence of meeting criteria
1-3 = poor attempt at meeting criteria
4-5 = some attempt at meeting criteria
6-7 = good attempt at meeting criteria
8-10 = excellent attempt at meeting criteria

Where criteria are marked out of 20, marks are allocated as follows: 
0 = no evidence of meeting criteria  
1-7 = poor attempt at meeting criteria  
8-11 = some attempt at meeting criteria  
12-15 = good attempt at meeting criteria 
16-20 = excellent attempt at meeting criteria