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
相关推荐
g***B7382 分钟前
Java 工程复杂性的真正来源:从语言设计到现代架构的全链路解析
java·人工智能·架构
期待のcode2 小时前
MyBatisX插件
java·数据库·后端·mybatis·springboot
醇氧4 小时前
【Windows】优雅启动:解析一个 Java 服务的后台启动脚本
java·开发语言·windows
sunxunyong5 小时前
doris运维命令
java·运维·数据库
菜鸟起航ing5 小时前
Spring AI 全方位指南:从基础入门到高级实战
java·人工智能·spring
古城小栈5 小时前
Docker 多阶段构建:Go_Java 镜像瘦身运动
java·docker·golang
MapGIS技术支持5 小时前
MapGIS Objects Java计算一个三维点到平面的距离
java·开发语言·平面·制图·mapgis
Coder_Boy_5 小时前
业务导向型技术日志首日记录(业务中使用的技术栈)
java·驱动开发·微服务
盖世英雄酱581366 小时前
springboot 项目 从jdk 8 升级到jdk21 会面临哪些问题
java·后端
济南壹软网络科技有限公司7 小时前
企业级盲盒系统:Java高并发架构在多元化抽奖电商中的设计与实践
java·架构·开源源码·盲盒源码·盲盒h5·盲盒app