FIT5046: Mobile and Distributed Computing Systems - Public APIs - IT Computer Science Assignment Help

Assignment Task :

An Overview:

• The assignment is an individual assignment.
• This assignment requires an interview.
• Demos/interviews will be held in the Tutorials and Consultation times in Week 11 and 12 (you should book a time with your tutor)
• This assignment requires submitting both NetBeans and Android project files AND a report with screenshots of each screen.
• The marks allocated for all the tasks in this assignment will add up to 100 marks and it is worth 30% of the total mark for this Unit.

Objectives and learning outcomes:

• To identify, develop and apply effective approaches and methods for building a mobile, distributed system (including both server and client sides) according to the specifications;
• To consider, evaluate and select Android building blocks that will achieve the specified tasks effectively and efficiently;

My Movie Memoir (M3)
The practical assignments (server-side and client-side) aim towards building a mobile and distributed, personalised diary application for keeping track of movies you watched and their details. The mobile app will be a movie memoir that allows people to create, delete, add or view a collection of memories that you had about the movies.
The mobile app will interact with the RESTful web service that you create in Assignment 1, and retrieve some useful and related information from public web APIs.
The assignment MUST be implemented in Android Studio.
You will invoke and consume at least three public APIs. These APIs include: YouTube, Twitter, and a movie related API (e.g. TheMovieDB). We have provided a tutorial for using the Google API as a starting point.
You need to make yourself familiar with the three APIs mentioned above by reading their online documentation. You will then SIGN IN to their FREE access only, and get a KEY so you can make http calls to their APIs (find out about the parameters you need to pass and their JSON response structure that you will receive and how to parse it to get the right information). This is part of this task.

• You will use YouTube API to get the trailer of the movie.
• You will use Twitter API to get up to FIVE comments posted about the movie (use the movie name + ‘movie’ as a keyword).

• You will use a movie API to get the details about the movie. This information must be retrieved: a synopsis/plot summary/storyline about the movie, genre, actors (up to 5), director(s), and review score (needs to be or converted to out of 10).

   

Task 1 Sign in (with a Sign-up option)  
a) The sign-in screen enables existing users to sign in, and allows a new user to sign up. Use only ONE screen here to sign in and a button to navigate to the sign-up screen. The sign-in screen will require a username (email) and a password.
This data will be verified with the data stored in the server-side database during the login.
You also need to follow the password design guidelines (refer to Lecture 7).  

b) The passwords should not be sent in the clear text to the server-side database. First, you need to hash the password on the client-side using the right libraries in Java.  

Task 2 Sign up form (User Profile) Screen  
a) The sign-up form will enable the new user to enter their information (i.e. first name, surname, gender, DoB, address, state, postcode, email and password).
In this screen, use a radio button for the gender, and for the state, use a spinner. Here our assumption is the users are from Australia. For DoB, use a date picker (a calendar widget to pick a date).

b) Data entry validation and error messages should be implemented where necessary.

c) You need to check/query that the email does not exist in the backend database already, and ask the user to re-enter it ONLY if there is a duplicate.

d) Your form should follow at least four form guidelines

e) The details of the new user should be added to the user table at the server-side database using the POST method.

Task 3 Home screen 
a) The home screen should welcome the user by their first name and display the app title, a related and meaningful picture, the current date, and the top five movie names, their release dates and rating scores given by the user for the current year (2020). The last information requires calling the right GET method 

b) The main page will use fragments and navigation drawer to navigate to other screens including Movie Search, Movie Memoir, Watchlist, Reports and Maps.

Task 4 Movie Search  
The Movie Search screen will enable the user to enter a movie name (case insensitive), and will display a list of matching movies with some basic information including the name, the release year, and an image (from Google or any other API). There could be cases that only one movie will be returned. The screen will allow the user to select one movie from the list. The details will be displayed in another screen, i.e. the Movie View screen

Task 5 Movie View  
a) The movie view screen will display the following information for the movie selected in the Movie Search screen (in addition to the movie name and release date that will be passed from the Movie Search screen):
an official trailer (from YouTube) 
the genre, the cast, the release date, the country, the name of the director(s), a synopsis/plot summary/storyline (from a movie API). To get some information like the cast, you might need to make two calls to the API. 
rating scores given by the public (from a movie API), and displaying scores as stars instead of numbers (supporting both half and full stars) 
Five posted tweets about the movie from Twitter in a scrollable container 
a) This screen should also provide two options/buttons for adding the movie to Watchlist or the Memoir.

• When the user clicks the button to add the movie to Watchlist, first you need to check if the movie already exists in the local database (refer to Task 6). If it exists, you should provide a message about it. If it does not exist, the movie will be added to the Watchlist table described in Task 5, and display a relevant message. 
• When the user clicks on Add to Memoir (it means the user has watched it), the user will be directed to the Add to Memoir screen to enter more information 

Task 6 Database, Notification and Watchlist Screen
a) In this application, in addition to the data that is stored on the server-side database, you will also store data about the watchlist locally using Android Room. The database will have only one table. The Watchlist table will store the movies that the user has searched, selected in the Movie View screen, and then added to Watchlist so they can watch in future. The table should store the name of the movie, the release date (in case it is a remake), and the date and time it was added to Watchlist. The other information about the movie is not stored because it can be dynamically retrieved anytime using the APIs.

b) You need to check the entries in the Watchlist table, and if the date it was added to Watchlist exceeds seven days for one or multiple movies, the app will display a meaningful message with two options: OK and Ignore. If the ignore option is selected, no action is needed. If the OK option is selected, it will redirect the user to the Watchlist screen (the user can be on another screen) so they can view the movies and delete them. You will generate the notification automatically every week using Android concepts such as AlarmManager. To demonstrate this funcitionality during the interview, you need to add a button in the Watchlist screen to trigger/enforce this action to show the notification is working. 

c) The Watchlist screen will show all the movies stored in the local database (the movie name, release date, and the date and time added to Watchlist) in a list menu such that they can be selected. The screen should provide two options for the selected movie from the list: 1) Delete and 2) View. 

d) In the Watchlist screen, after selecting a movie from the list, if the view button is clicked, the user will be redirected to the Movie View screen where it will show the details of the selected movie (the same details that the Movie View shows for the selected movie from the Search screen, refer to Task 5). In the Movie View screen, the Add to Watchlist button must be disabled because the movie already exists in the local database. The purpose here is to allow the user to add the Watchlist movie to their memoir if they watched it.

e) In the Watchlist screen, after selecting a movie from the list, if the delete button is clicked, the movie will be deleted. Provide a confirmation message before delete. After the user confirmation, the selected movie must be deleted from the local database, and the watchlist screen must be refreshed.  
 

Task 7 Add to Memoir  
a) In Task 5, it was mentioned that after the selecting a movie, the user could add the movie to his/her movie memoir by clicking on the Add to Memoir button that redirects the user to the Add to Memoir screen. This screen will show some data passed from the previous movie view screen including the movie name and its release date, plus a related image (from Google or any other API), and asks for further information. For passing data between fragments and screens, there are a few options, refer to the Android lectures. 

b) The screen allows the user to enter more information about their movie memoir. This includes:

• The date that the user watched it (use a date picker) and time.
• The cinema suburb or postcode (e.g. Chadstone or 3148). You could use a spinner listing most popular suburbs/postcodes where cinemas are.
• A short comment about their memory, opinion and how they felt after watching the movie
• A rating score for the movie provided by the user using stars. You need to come up with a creative, dynamic and efficient way to support full and half stars for rating. Efficiency here means you must avoid repeating the same code and achieve the task with the minimum code, and also it should require the minimum effort from the user.

c) After all the information is entered, and the user clicks the submit/add button, the movie memory and cinema details must be added to the momoir and cinema tables at the server side (you might need two POST methods)

Task 8 Movie Memoir  
a) This screen will display a list of all movies stored on the server-side database. This list will show the movie name, the release date, an image (from Google or any other API), and the date that the user watched it, cinema suburb/postcode, user comment/memory, and the user’s rating score as stars. It requires calling a GET method to retrieve all these movies from the server-side database.  

b) The screen will provide three sorting options (i.e. based on the date, the user given rating scores as stars, and public review scores (from a movie API) as stars. The filter options can include different genres (use a spinner).  

c) This screen will be scrollable. Each movie can be selected. When a movie is selected, further details about that movie should be retrieved from the APIs including the official trailer. The details will be similar to the results of Movie View (Task 5).  

Task 9 Report  
The Report screen will provide the user with two types of reports that will require querying the movie memoir table calling the right REST methods.
a) Pie chart: the top section of the screen will include a date picker to allow the user to enter a starting date and an ending date, and a pie chart that will display the total number of movies watched per suburb/postcode (as percentage %) for the selected period. The labels and percentages should be shown on the pie chart. 

b) Bar graph: the bottom section of the screen will include a spinner to allow the user to select a year (2015 to 2020), and a bar graph to show the total number of movies watched per month for the selected year. For your interview, make sure you have sufficient data for a few months in a year. 
 

Task 10 Map  
a) The map screen will show the user’s home location. You need to programmatically convert the full address of the user based on their address and postcode into latitude and longitude values (using either Google Geocoding API or Android built-in libraries like Geocoder). Then use the latitude and longitude values for displaying the location on the map. This requires a GET method to retrieve the user information from the server-side database. 

b) Similar to the task 9 (a), convert the cinema suburbs/postcodes into latitude and longitude values and show them on the map. This requires a GET method to retrieve the user information from the server-side database. To easily see the results of (a) and (b) during the interview, make sure in the database you enter your address and at least one cinema in the same or neighbouring suburb.  

c) When the user taps on a cinema marker on the map, display its name (e.g. Village Cinemas Doncaster).  

d) The marker for the user location and cinemas should have a different colour.   
You can use any map API to complete this task.

Task 11 Advanced Features  
To achieve this task you need to select only ONE of the following options and fully complete it. These are features, which have not been taught during the semester but will require applying similar steps and problem-solving skills learned during the semester. These features are:
1) Post a message (e.g. your newly added Watchlist movie name) to a social media platform (FB, Twitter, Instagram, or else). This requires finding the right SDKs and incorporating it to Android and addressing all the compatibility, versioning or missing libraries issues.

2) From the app, connect to your Google calendar and display your next event if it is a cinema event (to demonstrate this functionality during the interview, you must add a fake cinema event to your Google calendar). This will require using certain Google SDK and an authorization method, involving sending an AuthorizationRequest to Google with all the required information such as secret key, a callback URL, and then receiving a URL. When users open this URL, they will be directed to the Google login page, where they will be asked if they grant permission to the app to access their Google calendar or not. If they grant the access, Google will send a http request to the callback method provided in AuthorizationRequest, which contains a token. Then, this token can be used (until it has not expired) to access the calendar of the user who granted permission.

3) Use Firebase or Cloud Firestore to store Watchlist data. You need to support adding and deleting the watchlist movies and retrieving all the watchlist

This  IT Computer Science Assignment has been solved by our  IT and Computer Science Experts at My Uni Paper. Our Assignment Writing Experts are efficient to provide a fresh solution to this question. We are serving more than 10000+ Students in Australia, UK & US by helping them to score HD in their academics. Our Experts are well trained to follow all marking rubrics & referencing style.

Be it a used or new solution, the quality of the work submitted by our assignment experts remains unhampered. You may continue to expect the same or even better quality with the used and new assignment solution files respectively. There’s one thing to be noticed that you could choose one between the two and acquire an HD either way. You could choose a new assignment solution file to get yourself an exclusive, plagiarism (with free Turnitin file), expert quality assignment or order an old solution file that was considered worthy of the highest distinction.