I'm excited about Ouya because my entire professional life has been about seeing cheap and open beat the stuffing out of closed and expensive.
But I'm not a game developer. I'm a guy who knows a little about code, a little about web services, a lot about systems administration. It occurs to me there could be a need for something I'm actually good at.
Has anyone thought about public/private key sharing, user authentication / authorization ... basically anything that a game developer finds tedious and lame and 'not developing good product' but still important is something I might be able to do.
Comments, criticism, reply or PM.
~brian
Display some adaptability
bdunbar
Posts: 0Member
Comments
I first had looked at Hydra Mobile and it looks awesome and simple to use BUT (and this is a very big one for OUYA games) it simply does not support more than one player at a time, XBL-style (where you could pop up a dashboard for two players to sign in or something).
My second thought was to do everything on the client-side. For singleplayer games this would be fine (but linked to the console itself and not the user's account, meaning the user has to find a way to transfer game saves if they switch to another console), but for multiplayer this could get pretty messy.
If you want to pursue this, I would be interested especially if I could use this from a MonoGame project, and if I could log in and manage more than one player at a time (very important!)