Our app uses PayPal to make personal payments for a publishing service, we're finished and in way to publish but when we got to the part of changing from Sandbox to going live with PayPal that's where things got complicated for us.
We're totally new to submitting anything to Paypal, I read the guide on this link and it couldn't be less clear on how to fill the form.
I filled the form to upload the mobile app, but we tripped with several doubts along the way, here I will list them:
our app is cross platform and we can only choose one platform, do we
have to submit both Android and iOS for revision separately? Even
though it's the same app?
we filled the form but there was nowhere to place an ipa or apk, only
a field asking for additional files like ad hoc stuff and such, how
do we submit our build for them to test?
I have to be honest, PayPal guides aren't clear and don't explain deeply many of the processes, as if we have already the knowledge of what to do, we searched the web for guides on how to go live but nothing came across our search.
We developed our app using Titanium Studio and the PayPal supports documents treat every submitted app as if they were natively developed, we are using a Titanium's module to make all the PayPal work, so we have no idea what API calls are made, apparently the module uses Adaptive API calls but we're not sure on this, we only make simple payments, do we still need to submit the app or should we be doing something else?.
As you can see we have zero experience with PayPal and while we wait for a response from PayPal and finish to pass every service we use to Production, we are trying to understand what to do with this submitting app phase.
We contacted PayPal support asking for a detailed explanation on what to do on our situation but no one has contacted us at all.
If the module is using the Adaptive Payments API then you'll need to submit the app for approval to obtain a live App ID for the Classic API's.
Login to your account at http://developer.paypal.com. Click on Applications and that will take you to a page where you manage all of your apps.
You should see "REST API apps" at the top and "Classic API apps" at the bottom. Click the link under the Classic section that says "Create and manage Classic API apps."
Then follow the steps from there.
Related
I'm developing an Android App where I needed to use the SDK provided by FB to enable login via FB.
Everything is OK and it works, but when I went at:
https://developers.facebook.com/apps/MY_APP_ID/settings/basic/
I saw that there is a button that says "Add Platform".
My question is, why should I add a platform for my APP if I have everything done without that?
Does anyone know when I might need to use that option, in which cases?
Any information would be appreciated.
Thank you in advance.
As the comments above indicate, this is pretty much the answer (fell free to correct me):
If your application is running in different platforms, this means that you should be able to login in the same account from different platforms, then that's where the "Add Platform" comes in play.
In my case, I had an Android App where users can sign up using their FB account.
If in the future, I want to create a website application, then obviously, the users should be able to access that application with the same FB account.
In this case, I add an Website as a Platform.
Currently, I'm looking to see if there is a way to sync the information we've obtained through an online site with the information we use on a phone application.
All I need to know is that the user that visited our site is the same user that is using our phone application, No stats and preferably no one needs to enter a thing.
You won't get that from Apple, because of their history with privacy concerns, but you could do something like generate an identifying number in your app, that your web site asks for, that would tie the two together. Of course, you'd have to make allowances if your app is deleted from the device, then re-installed, to either make sure you're generating the same number, or other such solution as befits your requirements.
The first thing that would come to my mind is Google Analytics, available for different platforms and services (i.e. Youtube, etc). You would have to go through Google Analytics API to figure out a way on how to track a particular customer visit across several location/platforms.
See Hello Analytics example of Google Analytics API
See Data Feed API
Ok, so far I've answered my own question for androids. Apparently you can pass a referrer param through google play which actually allows your app to receive the parameter and they even have an app that test this functionality.
https://play.google.com/store/apps/details?id=net.stevemiller.android.referrertest
now I have yet to test this, nor is it a possible solution for iOS.
I would just like to ask if there are any best practices for a shared subscription billing for iOS and Android.
Right now, we are developing a mobile app both on Android and iOS (both native sdk, not cross-platform). And we have this certain feature in the app which you need to subscribe in order to access. But this will be a shared subscription. A one time payment regardless of what device a user is using to subscribe.
Sorry, but I am not really good in explaining things so maybe I will give you a scenario. I hope it helps you to understand what I am talking about.
For example, a user has two phones, an Android phone and an iPhone. He then installed our app in both his iPhone and Android phone. Now, he opens our app in his iPhone and he wants to access that certain feature so he subscribed. With this, what we want as a developer is to make it so that when he opens the app in his android phone, he will already be able to access that certain feature since he has already subscribed when he used the iPhone app.
We are still hesitant to continue since Google and Apple have different billing schemes. But maybe there are solutions for this, or are there?
I am hoping that someone could give us light on how to do this in the best practical way possible.
Thanks in advance...
I am currently facing the same issues. That's what I have so far.
There seem to be cross-platform solutions but none of them seem to work through Google Play or Apple payment methods..
You can use your API/backend service to flag the current user subscription state and sync it across all your platforms (that might violate Apple in-app system conditions).
I'm currently looking for a way to communicate to both Google Play and Apple in-app payment system that the item has been already bought in a different platform. There should be a way but as said, still looking for it.
We'll keep that up to date.
My app is basically supposed to sell ebooks and need to distribute via Android Market. For payment options, I would like to use PayPal. So, straight to the point, am I allowed to use paypal as payment option for digital goods(in my case Ebooks)? I had googled for it a while. But nothing worth referencing came up to me.
I also read through Android Market terms and didn't quite get it whether they allow such option for in-app billing. All I see from their docs is referring to Google Checkout. Any help would be greatly appreciated.
Well, just for information, I refer to http://www.google.com/mobile/android/market-tos.html .
Just to keep up, http://www.android.com/us/developer-content-policy.html#showlanguages this link may well more specific to my situation.
In general, you need to be careful - the TOS of the Android Market generally require you to use Google's payment processing options to charge users (see "Paid and Free Applications").
That said, they name two exceptions, one of which seems to apply in your case - "Where payment is for digital content or goods that may be consumed outside of the application itself (e.g. buying songs that can be played on other music players)". If your app sells ebooks in the form of standard files (like epub or pdf), you should be in the clear.
I believe you can sell digital content using paypal via your app - however I don't think you can use Google's In-App Purchasing system - that has to go through the Market Place, and is linked to a Google Checkout account.
So you'd need a separate delivery and authentication system.
I am currently developing an application where I want to be able to have an option to allow the user to donate money for the app. Is there a particular way about doing this for android. I have tried looking at google but it mainly shows about paypal donation buttons for websites
I think it should be possible.
There's a similar discussion on Google Groups which basically says that donations are allowed as long as you don't offer additional functionality for that money.
Meaning no functionality is enabled after the donation is made.
Like #alocaly said, you're unable to recieve donations through a system different from android market payment or ads inside the application.
However, it is still possible to have your application on the Internet by free and with a donation button. The difference is that you cannot post it on the Android Market, so you'll have to do some extra work:
Upload to a webserver, so it can be downloaded to your phone.
Create a website (or post your application to another "illegal" market), so people can find your application.
Use some sort of advertising to let people know your application (Twitter retweets, community ads, GoogleAds, SEO, whatever)
Manage some kind of update system. Since you don't rely anymore on the Android Market, you don't have an automatic updating method (Android Market updates applications when you post a new version of it), so you should have a small class that checks a website looking for a new version (it's not that hard) and downloads a new version when there's one available.
Make work the Paypal button like #Tim said
However, you are able to do something that I've see out there: create a free version of your application and post it on the Android Market, and post another version of the same application called "Same program name (Donation)", costing some money. When someone wants to donate you, they'll only have to buy this version.
I hope it helps
I don't know what importance it has, but I think that the chart / terms of services we sign as android developers don't allow the usage of this kind of monetization.
As this is a subject that is changing a lot in Android world, with the soon to come API to pay in apps, I'm not sure it still has any importance, but you should still be aware of that.
Maybe you should take a look at this post, which explains how to integrate Paypal payments into an Android App witout leaving the App itself: How to integrate paypal donate in android app?