This is far from easy to solve, but it's quite high priority. Currently there's no policing of names used, meaning two people could use the same name, causing a clash in the remote highscores DB.
It would be nice to solve this without placing requirements on the user (e.g. using something like IP address to identify them), but I don't think there's a viable way to achieve this.
The solution will probably need to involve communicating with the server to check whether a requested username is available. There will then need to be verification - the standard solution is password with email backup... (or e.g. google/facebook login?).
To complicate things further, the app should still be user-friendly in the case there's no internet connection, and there should maybe be a way to turn off uploading highscores.
This is far from easy to solve, but it's quite high priority. Currently there's no policing of names used, meaning two people could use the same name, causing a clash in the remote highscores DB.
It would be nice to solve this without placing requirements on the user (e.g. using something like IP address to identify them), but I don't think there's a viable way to achieve this.
The solution will probably need to involve communicating with the server to check whether a requested username is available. There will then need to be verification - the standard solution is password with email backup... (or e.g. google/facebook login?).
To complicate things further, the app should still be user-friendly in the case there's no internet connection, and there should maybe be a way to turn off uploading highscores.