Reference no: EM132789208

You may hard-code data into the app but to achieve the highest marks in this part, your application should connect to a public, web-based service (see Assessment Criteria below) e.g. to retrieve live information such as the ingredients and nutrients for a selected product.

As part of the app you will need to maintain a small database to store the products and their mapping into lists.

For this you will use an SQLite database. An example database is provided for you and you are free to build from scratch or extend it as you wish. This is a simplistic database with just three tables named ‘lists', ‘products' and ‘products_to_lists'. The first table holds the details of each list (id, name, description, perhaps colour). The second holds details for each product (id, name, ingredients, nutrients etc.). You can use the openfoodfacts API to see the available data. The latter table uses foreign keys to match products to lists. This is illustrated in the figure below:

Figure 1: Schema of the ‘products', 'lists' and ‘products_to_lists' tables

In the "products" table the ‘code' is the primary key (it can take values such as ‘20503550', ‘3052X22A', etc.) The ‘name' is the product's name (e.g. "Kellogs Corn Flakes"), ‘grade' is a text-based rating of the nutritional value of the product (usually ‘A', ‘B', ‘C', ‘D', and ‘E'). Similarly, the nova group is a numerical rating of the nutritional value of the product. The ingredients and the nutrients can be text-based descriptions of the contents of the product (like "sugar 50%, salt 5%", etc.) Note this is only one way to (simplistically) hold the information. You could also hold the structured data you receive from the openfoodfacts API in separate tables, or perhaps as a JSON-formatted string which continues to hold the information. Additional data you could include are ‘vegan', ‘vegetarian', etc. (SQLite does not directly support Booleans. Instead, you could use integers where 0 is false and 1 is true).
The "lists" table holds data about the lists you use to organize the products. At the very least they include an ID, name and description, but you could further customize with colour, icons, etc.

Finally, the ‘products_to_lists' table is used to provide mappings from products to lists. The two fields together form the primary key, and individually are foreign keys to the corresponding products and lists tables. Adding an entry introduces the mapping of the product to a list. Removing it eliminates the mapping. This way you can have multiple mappings of the same products in multiple lists, and multiple products in the same list. SQLite has a simplified set of data types compared to other database engines such as MySQL.

THE BRIEF/INSTRUCTIONS

Your coursework assignment is to design then develop a mobile application. The following pack outlines the basic components and advanced features your application needs for assessment. The second route is pre-defined - this is the route for you, if you would prefer to be told exactly what to create. Both the routes are assessed in the same way, there is no one route better than the other. It is personal choice for each individual student.

Either way, in the first part of the assignment, you will design the user interfaces of your application, which is worth 40% of the overall mark. In the second part (implementation), you will create a working mobile application that corresponds to your designs, which is worth the remaining 60% of the overall mark. You must submit the mobile application including all relevant files to re-compile.

You must gain 20% in each of the two parts to pass overall, please see the Assessment Criteria for further details.

Design
Create at least four screen designs (whether you are following Route One or Route Two) which convey your ideas for the app you plan to create which includes the above pieces of functionality (targeting phone devices, not tablets). These should follow the prototyping process you have learnt in the labs (low to high fidelity, hand drawn to Figma). These screens should be part of the same application. For each of the four screen designs you must provide a written description of 100-200 words justifying your worki.e., explain why you have designed the UI the way you have, and how this has been informed by the sources you read. The designs must be created before the app is implemented, no marks will be given for screen captures from an Android emulator/phone or from within

Route Two
You are to develop an app that provides nutrition facts and information to users. The app should:
1. Contain a list of products (minimum 20 products) so it can be tested. Each product must include at least its name and its nutrition grade (i.e. A, B, C, D, E). You will be able to add more products using screen #2.
2. A screen for adding new products. The user should be able to type a product's barcode or scan a barcode to add it. The data must be automatically loaded using the openfoodfacts API. If the product is found, enable the user to ‘save' it to the list of products (i.e. screen #1).
3. A screen where you can view individual products. For a selected product you should be able to see a description (name), ingredients, and nutrients. Also, you should be able to add (or remove) products from custom lists (see screen #4 below).
4. A screen for managing custom lists (like ‘favorites' or ‘avoid' or ‘healthy'). This screen should enable you to add more lists or delete existing ones. Clicking on a list should show the list of products in that list.

Minimum Requirements
There are minimum requirements that your app needs to include. The application should:
• have followed the design process and created a meaningful user interfaces for your application.
o In addition to the Android Design Guidelines (https://developer.android.com/design/), find a selection of between 2 and 5 additional sources relevant to mobile user interface design and read them. Try to find a range of high-quality sources such as guidelines published by reputable sources, research papers, journal papers, book chapters, etc.
• be developed using Flutter and must be deployed on either Android, iOS or Web (where appropriate).
• include local storage (this is so you can save information to the device, such as login details or settings etc.) using an SQLite database.
• display information to users using multiple methods (list, form, card etc).

Advanced features
In order to access the advanced part of the assessment you should consider the following:
• Create an annotated bibliography: this is simply a list of useful sources you found where each has an associated paragraph summarizing why the source is useful i.e. what information does it provide that can help you create a high-quality usable mobile interface. Use the Harvard Referencing Style for your citations and bibliography.
• Demonstration of networking capabilities, usually by connecting to a free/open API.
• Integrate cloud storage from Google's Firestore to store and retrieve data.
• Utilisation of a specific device feature (Camera > QR reader, GPS, etc.)

Attachment:- Work mobile computing.rar