For games, would you implement to security or to usability? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

I plan to create a game that is largely online-based via mobiles. I have in m开发者_JAVA技巧y mind how I would handle authentication for both a very secure standpoint (login, credential creation, etc), and also from a very usable standpoint (device authentication, client based, no action needed).

Since I am the only one in my development team (lol), I am interested to hear your input about this problem. In my mind, I would like to implement to usability due to the lackadaisical nature of gaming, and how impressed I have been with services like scoreloop (who dont require and/or pester the user for login / password / account generation). But it also brings a certain amount of uncertainty and lack of control to the user.

For a game, what is more important to you? Or is there an implementation you can think of that is a marriage of the two?

---

It completely depends on what kind of game you are trying to build. If the game you are going to make is a really simple quick multiplayer game it hardly makes any sense to incorporate heavy security, just entering a name would be enough for it to be playable.

On the other hand, I don't really dislike logging in all that much, but it would be ideal if the server would just recognise my phoneID and would use that as an identification. The only problemn this would cause is that if you use another phone you would have a new useraccount.

But then again, how many people own multiple android devices they use for playing games...