lmilunovic / mine-field-alarm-android

📱Android application that triggers alarm when user comes near a minefield.

mine-field-alarm-android's Issues

About alarm

It should be decided how alarm will response.

Lets say user aproaches near unsafe area and triggers the alarm.
User leaves area and enters again within 5-10 seconds - alarm triggers again.

It could be annoying and bad UX.

Resources out of their position

Those resources need some cleanup or to be moved in res folder from app/src/main

https://github.com/Ladislav92/Mine-Field-Alarm-Android/tree/master/MineFieldAlarm/app/src/main

GPS API

Instead of using geolocation API we should consider GPS API since it is probably more precise.

When I started implementing the app I tested Geolocation precision a bit. In an urban area, it could make mistakes from 50m to 150m with 3G / H+ network. So that has to be accounted when making a decision about triggering the alarm.

Never tested it in open field.

Ask for location permission

The user should be explicitly asked for permission for location if the app has no permission. Right now that is not implemented and it should be.

Turning off tracking service breaks the app

When I want to turn off the tracking service, by clicking on the radio button, app crashes.

Logcat says: FATAL EXCEPTION: main
Process: com.example.ladislav.minefieldalarm, PID: 2748
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Context.getPackageName()' on a null object reference

Points to the SettingsActivity.java , line 34.

Populating database with actual data

Right now, the application is supposed just to connect to the database that already contains data.

Maybe some other option could be introduced, even client-server app or something.

User interface

UI is really basic and should be improved for different screen sizes etc...

Implement custom Geofence class

Geofences API doesn't let tracking more than 99 geofences simultaneously, so I would like to implement custom geofence class because I don't want to rely on API for such important question.

We have some math ahead there:
So we need to implement a mechanism for the collisions of a user and minefield border.
We need to calculate (depending on the precision of received location) safe area to come near the minefield - we don't want the app to trigger an alarm when a user actually enters in.

If someone has a good argument not to do this, go on.

Remove about organisation activity

The first idea for this application was to be a part of UDAS organization, but since we decided to "spread the word" this activity has no meaning anymore.