Mobile application design comp1786

Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: _0206girl

Detailed Specification

Please read the entire coursework specification before starting work.

This assignment consists of two parts:

  • Part A (implementation) will be completed individually
  • Part B (report) must be completed individually
  • M-Hike: Hiker Management App
  • Many people enjoy going for hikes in nature in their free time. A community of hikers has approached you to create a mobile app which would allow them to record details of hikes they are planning and record observations during the hike.
  • You are to create a mobile app for use by hikers that they can use to record details of their planned hiked and then upload them to a server where they can later be shared with others. The app is to be called M-Hike and will allow hikers to record planned hikes and observations during a hike and to carry Out searches. The features the app should Support are given below:
  • Features a) to e) are to be implemented as a native Android app coded in Java.
  • Features f) andg) are to be implemented as a hybrid app coded usingXamarin/MAUI.
  • Feature g) can be implemented as either or both additionsto thenative android app or hybrid app.
  • Your final app is the culmination of all your hard work on this course, which should become a strong addition to your programming portfolio. You should produce an app that is well-designed, robust and useful. The GUI design should be clean, simple to navigate, and operate smoothly without sluggishness or crashes. The app should not require instructions or a manual to use.

Part A -- Implementation (80%)

Description of the application

  1. Enter details of hikes (10%):
  2. Note that users must be able to enter all of the following fields. Required fields mean that the user must enter something in this field; otherwise they will be prompted with an error message. Optional fields mean that the user can enter something if they wish, but they will not get an error message if nothing is entered.
  3. The user should be able to enter:

The user must be able to enter multiple observations for a single hike.

The app should store all details entered on the device in an SQLite database.

It should be possible for a user to select a hike and display all observations and view/edit/delete a specific observation.

  • Name of hike (e.g. "Snowdon•, "Trosley Country park", etc.) --- Required field

  • Location - Required field

  • Date of the hike - Required field

  • Parking available (i.e. "Yes" or "NO") - Required field

  • Length the hike - Required field

  • Level of difficulty - Required field

  • Description --- Optional field

  • Two or more other fields of your own invention --- be creative The app will check the input and if the user doesn't enter anything in one of the required fields, the app should display an error message.

    Once the details have been accepted by the app (e.g., no required fields were missing), it should display the details back to the user for confirmation and allow them to go back and change any details that they wish.

    Note : The GUIs should use appropriate controls for data entered and minimize the amount of time that users have to enter data manually. More information about Android controls can be found here https://developer.android.com/develop/ui

  • Store, view and delete hike details or reset the database (15%)

All the details entered by the user should initially be stored on the device in an SQLite database.

The user should be able to list all the details of all hikes that have been entered into the app, edit or

delete individual hikes and delete all the details from the database.

  • Add observations to a hike (15%)

Hikers will be able to enter observations during a hike. Observations could include sightings of animals,

types of vegetation encountered during the hike, weather conditions, conditions of the trails, etc. They

should be able to select a hike and then add the following details:

  • Observation - Required field
  • Time of the observation - Required field (ideally this should default to the current date and time)
  • Additional comments - Optional field
相关推荐
clorinda4 小时前
SQL 快速入门:题目单知识点精炼总结
java·数据库·sql
AI人工智能+电脑小能手4 小时前
大白话说Java设计模式-40-备忘录模式(业务实战篇)
java·设计模式·事务回滚·备忘录模式·状态保存·spring transactional·购物车快照
SimonKing4 小时前
白嫖国产多模态大模型:商汤 SenseNova 接入指南
java·后端·程序员
小江的记录本4 小时前
【ORM框架】MyBatis核心原理、ORM思想、MyBatis vs JPA
java·数据库·后端·spring·spring cloud·oracle·mybatis
_明月4 小时前
汇川技术股份有限公司面试--Java外包岗
java·面试·职场和发展
BD_Marathon4 小时前
Hadoop常用端口号
java·大数据·hadoop
青石路4 小时前
好好的OceanBase官方驱动你不用,非要用第三方驱动,ArrayIndexOutOfBoundsException了吧
java·后端
长谷深风1114 小时前
读懂 MCP:能力、传输与多 Server 连接
java·大数据·ai·ai agent·mcp·streamable http·agent设计
深念Y4 小时前
Makefile vs go run:Go 项目构建方式对比
java·开发语言·golang·k8s·编译·流水线·cicd
我命由我123455 小时前
Android Camera - 获取当前设备屏幕的旋转角度、保存帧到外部存储的私有空间
android·java·开发语言·java-ee·android jetpack·android-studio·android runtime