cool, that's good to hear.
Thanks for the response Kris.
On Wed, Dec 18, 2013 at 10:30 PM, Kristopher Micinski
krismicin...@gmail.com wrote:
To answer your question, no such thing applies to the cloud save API
in the way you're describing. If your app isn't easily serializable
in an
I don't see why this would be at all problematic. It seems completely
within the guidelines that says this is a bad idea. The Cloud Save
API is just that, an API: so I'd use it however it worked best for
you!
Kris
On Wed, Dec 18, 2013 at 3:08 PM, Sheado chad...@gmail.com wrote:
Hi Android,
Thanks for the response Kris,
I ask because none of the conflict resolution docs recommend this solution.
See: https://developer.android.com/training/cloudsave/conflict-res.html
I'm also concerned that if it doesn't meet their quality guidelines, then
it would not be considered for featuring.
Uhh.
Hate to break it to you, but there is basically no way you are going
to considered for featuring anyway, that's a whole 'nother ballgame
:-). You can argue with people about how to make that happen, but I
can basically guarantee you that they're not going to decompile your
code and
haha.. you're right, the chance of getting featured is practically zero. We
probably have a better chance with the lottery.. or a lightning bolt.
But, for example, Amazon has a Developer Select program in which you get
additional exposure on their app store if you implement a set of features
and
To answer your question, no such thing applies to the cloud save API
in the way you're describing. If your app isn't easily serializable
in an incremental fashion, then an explicit save point sounds like a
perfectly reasonable thing to do...
Kris
On Thu, Dec 19, 2013 at 1:07 AM, Chad Ata
6 matches
Mail list logo
