• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

central data repository for client applications?

 
James Elsey
Ranch Hand
Posts: 228
Android IntelliJ IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

(this question is about the android platform, but themed around a game so I'm hoping that posting in the Android section is correct, sorry if my assumption is incorrect)

I would like to create an application in Android, it will be a simple game like tic-tac-toe

If I create this using local data storage, it will be fine for a "single player" game. I can store games, user statistics and such locally, either in some file structure, or using SQLite

However, I would like to allow this to be a multiplayer application, therefore I can't really use data storage on the local device, I would need some central database of some kind to house this. If I store data locally, then how can I see that my friend Lee has played x games and got x number of points? Or even more importantly, how can I interact with him?

This way, the central DB can hold the game data such as "games", "users/accounts", "high scores" and so forth.

What is a good viable solution to this, should I purchase a SQL database on the net, and use JDBC to connect to this? Or is there an alternative, possibly even free solution?

How else could I create a multi-person application? It could be possible that I could "sync" all clients running this application, but that feels such a dirty way of doing it I might go take a shower...

Apologies for a slightly confusing question, I'm still trying to understand my idea and to identify its limitations
 
David Newton
Author
Rancher
Posts: 12617
IntelliJ IDE Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It'd be easy to expose a web service that takes oauth-ed info and updates the app. There's no (documented) JDBC available on Android, and what's there is really designed for the on-board DB (SQLite), not remote DB connections. A service call would be substantially easier, and more versatile. There's a JDBC "wrapper", but that's also for the local SQLite DB.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic