3 ms·
You have two options: 1. Use a hosted service, and IF they end up shutting down either migrate to another similar service or roll your own. 2. Roll your own f
by tlrobinson 14y ago
You have two options:
1. Use a hosted service, and IF they end up shutting down either migrate to another similar service or roll your own.
2. Roll your own from the start.
I'm having a hard time seeing why option 2 is better. Just make sure the services you use give you a clean migration path.
A lot of game developers don't have experience building web services, so it makes sense to outsource the things that aren't their core competency. Do we really want every game developer rolling their own potentially unreliable, unscalable, insecure web services?
- josephlord 14y agoI came to the same conclusion for adding usage logging and promo codes to my app. Use Parse for now but try not to use too much of their API and to keep it to a couple of particular lasses that I access it through so that if I need to move it is just a day changing the app and one or two setting up and securing a server with a database. Not a game but a lists app focussed on reusable lists for things like shopping and packing with a couple of neat features. Http://iTunes.com/apps/fastlists. Free with in-apps if you like it. I haven't decided how to do shared lists yet, iCloud, Parse, custom server or something else.