App development (GPS location marker) -- 2
Budget: £20 – £60 GBP
create an Android mobile app that will record individual GPS locations
(in terms of their latitude, longitude – but not altitude). The app should also be able to store, with each
recorded location, a name and a short note. Such an app will be useful as a surveying tool for example
or as a generic geolocation recorder.
A general description of the app’s expected functionality will be given here. You must try to achieve
all of the functionality described here but you are not supposed to go beyond this functionality by
adding more features. Doing so will take unnecessary time from you without earning you any
additional marks. Also, you may risk losing marks if any additional functionality you choose to
implement interferes negatively with what is expected.
Once launched, the app should continuously track and display the geolocation (latitude and longitude
only) of the device it is running on. The user can choose to store their location at any moment they
choose under a name and a short note. This should be allowed to happen multiple times (i.e., the user
should be able to store multiple locations). The user should be able to view all saved locations in a list
and also be able to view the details of, edit (only the name and note) or delete a single stored location.
They should also be able to delete all stored locations in one go if they choose to.
You are not expected to draw any maps or show geolocations on maps. The app should be as simple
as possible and only be satisfying the requirements described above.
The app should record data in permanent/persistent memory (for example an SQLite database) on the
host device for maximum marks (see marking scheme below). If you choose to store the details of the
saved locations in a volatile memory structure (for example array, linked list etc.) you will attract less
than maximum marks for this feature.
The app should be created so that interaction with it is as convenient/efficient as possible (i.e., with
minimum number of button presses, selections, navigation between screens, unnecessary scrolling
etc.) whilst minimising the potential for error on the user’s side.
!!Must use API 27: Android 8.1 (Oreo) as the SDK for the project
(in terms of their latitude, longitude – but not altitude). The app should also be able to store, with each
recorded location, a name and a short note. Such an app will be useful as a surveying tool for example
or as a generic geolocation recorder.
A general description of the app’s expected functionality will be given here. You must try to achieve
all of the functionality described here but you are not supposed to go beyond this functionality by
adding more features. Doing so will take unnecessary time from you without earning you any
additional marks. Also, you may risk losing marks if any additional functionality you choose to
implement interferes negatively with what is expected.
Once launched, the app should continuously track and display the geolocation (latitude and longitude
only) of the device it is running on. The user can choose to store their location at any moment they
choose under a name and a short note. This should be allowed to happen multiple times (i.e., the user
should be able to store multiple locations). The user should be able to view all saved locations in a list
and also be able to view the details of, edit (only the name and note) or delete a single stored location.
They should also be able to delete all stored locations in one go if they choose to.
You are not expected to draw any maps or show geolocations on maps. The app should be as simple
as possible and only be satisfying the requirements described above.
The app should record data in permanent/persistent memory (for example an SQLite database) on the
host device for maximum marks (see marking scheme below). If you choose to store the details of the
saved locations in a volatile memory structure (for example array, linked list etc.) you will attract less
than maximum marks for this feature.
The app should be created so that interaction with it is as convenient/efficient as possible (i.e., with
minimum number of button presses, selections, navigation between screens, unnecessary scrolling
etc.) whilst minimising the potential for error on the user’s side.
!!Must use API 27: Android 8.1 (Oreo) as the SDK for the project