This simple use case is proving trickier than I would have thought it would be. My app is designed to operate while the phone is in airplane mode.
1) A user downloads the app, runs it once with wireless connectivity to get a license. Then there are two cases to consider: 2a) User requests a refund with the permitted timeframe, and 2b) User is happy with the app, and switches to airplane mode forever. My initial approach is to set the validity timestamp preference to some date far in the future. This is fine for 2b, but what about 2a? During the refund period, seems to me that my app should interact with the license server just like any standard ServerManagedPolicy-based app would, and only after the refund period expires would I set the cache validity horizon to forever. Can I rely on refund mechanism deleting my app and stored preferences thereby making 2a a non-issue? It occurs to me that a very useful server extra would be a boolean indicating whether the refund period has expired. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
