We are supporting monthly billing. Here's how it works: CASE 1: Device Call 1) user downloads application and accepts monthly billing' 2) application starts up and queries a page on slideme, sending appId, userName, etc and asking if they are a subscriber 3) if they are a subscriber, the app starts up.
The developer is responsible for making this call from their code if they want to do a subscription model. Basically, the dev can specify monthly billing for an app, so when the user downloads, they agree to pay a monthly payment. It's up to the developer to provide any sort of authentication for the app. CASE II: Server Call 1) user downloads application and accepts monthly billing' 2) application starts up and queries the developer's servers 3) dev servers query back to slideme for billing subscription status 4) if they are a subscriber, the app starts up Case II gives the developer more flexibility if they already have an app that requires a login to use. It also allows the developer to have billing outside of slideme, since that is all hidden from the application. CASE I would be more for standalone applications. Shane On Fri, Oct 17, 2008 at 8:46 AM, j <[EMAIL PROTECTED]> wrote: > > Interesting...I notice that you site has an app that says it will > incur a monthly fee. Are you supporting monthly recurring billing? > > If yes, what if user uninstalls the app from his phone, will he keeps > getting charged? > > On Oct 17, 8:29 am, JP <[EMAIL PROTECTED]> wrote: > > Al, thank you for the clarification. > > > > It is not difficult to determine the permissions and other > > characteristics of an apk package. > > $ aapt dump permissions <package> > > prints permissions and I would find it very helpful to the buyer (and > > seller to assure buyers) if this information is used by the "conduit" > > web service before an app is downloaded, let alone paid for and > > executed. > > JP > > > > On Oct 17, 8:12 am, Al Sutton <[EMAIL PROTECTED]> wrote: > > > > > I think Joachim is referring to letting the user know the permissions > > > before they try to download it, so a user can see if a dialler app > wants > > > to access the internet, their personal data, and their mums handbag > > > before choosing to pull it down :). > > > > > Al. > > > > > Shane Isbell wrote: > > > > > > On Fri, Oct 17, 2008 at 6:34 AM, JP <[EMAIL PROTECTED] > > > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > > I am warming up to the idea of third party distribution. Do you > have a > > > > capability to pop the hood on an .apk and read the permissions to > > > > present them to the potential buyer? > > > > > > This is all handled by the Android platform; so yes, when the user > > > > clicks to install the app from sam, the permissions will pop up prior > > > > to install. > > > > > > Shane > > > > > -- > > > Al Sutton > > > > > W:www.alsutton.com > > > B: alsutton.wordpress.com > > > T: twitter.com/alsutton- Hide quoted text - > > > > > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
