For games, would you perform security or usability?

I plan to create a game that mainly works over the Internet through mobile phones. I mean, how I will process authentication both for a very reliable point of view (login, credential creation, etc.), and for a very convenient point of view (client-based device authentication, no action is required).

Since I'm the only one in my development team (lol), I am interested in hearing your details about this issue. In my opinion, I would like to implement usability due to the lack of gameplay and how impressed I am with services like scoreloop (who does not require and / or does not bother the user to enter / password / create an account). But it also introduces some uncertainty and lack of control for the user.

For the game, which is more important for you? Or is there an implementation that you can come up with is a marriage of two?

+4
source share
1 answer

It completely depends on what game you are trying to build. If the game you are about to make is a really simple fast multiplayer game, it hardly makes sense to include heavy security, just entering a name will be enough to make it playable.

On the other hand, I don’t really like to keep a log in all of this, but it would be ideal if the server just recognized my phone ID and used this as an identification. The only problem is that if you use a different phone, you will have a new user account.

But then again, how many people own multiple Android devices that they use for games ...

+3
source

All Articles