5 ms·

Do you think that's good for users though? Especially with Google's lax oversight of the marketplace? If the developer using their own payment method changed th

Do you think that's good for users though? Especially with Google's lax oversight of the marketplace? If the developer using their own payment method changed their PayPal redirect to a phishing site, would users notice? What if you implemented your own credit card payment? Where's the guarantee that you're PCI compliant? I can tell you that 99% of your users won't know what PCI compliance is. If Google allows users to become accustomed to entering their credit card info to each individual app, there could be major liability issues that I'm sure Google doesn't want to deal with.

jamespo 13y ago
On that basis maybe Google should stop Chrome allowing credit card form submissions.
- freehunter 13y ago
  But instead of doing that, they now offer to remember your credit card numbers in the browser. That's a big no thank you from me.
darklajid 13y ago
Reeaally? So, is Chrome now filtering the internet to catch you entering your CC number to some vague service online? Because that's what we're talking about. Shopping (for an in app purchase, but still) online, in a browser. I wonder how Google checked if Amazon is PCI compliant.. If you're entering your CC everywhere that's not something Google can (or should - no need for a nanny..) fix. There's no way in my world that Google _could_ be liable for these kind of things. You're trying to understand their motivation for banning alternative payment methods. We both have a theory. Mine is 'greed', yours is 'protecting the user and protecting the company against evil worldwide'. I really think you're giving them too much credit here.
- rmrfrmrf 13y ago
  There's a very clear difference between native apps and web apps in my mind. EDIT: I should make very clear to non-developers out there that, with a native app, you're able to display a web browser without a URL bar or any other UI, which makes it exceedingly easy to trick people into thinking that they're at an official PayPal site or other shenanigans that the unscrupulous dev wants to try. More information: https://developer.android.com/reference/android/webkit/WebView.html https://developer.android.com/reference/android/webkit/WebVi...
  - ceejayoz 13y ago
    > EDIT: I should make very clear to non-developers out there that, with a native app, you're able to display a web browser without a URL bar or any other UI, which makes it exceedingly easy to trick people into thinking that they're at an official PayPal site or other shenanigans that the unscrupulous dev wants to try. Nothing's stopping a non-standard browser (Opera, Firefox, etc.) from doing that, and they're permitted on Android. Hell, you could do it on iOS, too.
    - rmrfrmrf 13y ago
      are you trying to miss the point?
      - ceejayoz 13y ago
        Are you? A custom browser can be designed to quietly send people accessing PayPal off to a phishing site just as easily as an app integrating a PayPal payment method. If Google's going to use that sort of attack as a reason to prevent non-IAP payments, they should be banning non-Google browsers too.
fauigerzigerk 13y ago
So where does that leave your "do the dirty work yourself" argument? Apparently you don't want developers to do the dirty payment systems work themselves. Neither does Google. So I suggest you reconsider your rather hostile attitude towards the developer who complained about Google's inactivity.
- rmrfrmrf 13y ago
  Wait, now I'm the hostile one? lol ok.

jamespo 13y ago

On that basis maybe Google should stop Chrome allowing credit card form submissions.

freehunter 13y ago
But instead of doing that, they now offer to remember your credit card numbers in the browser. That's a big no thank you from me.

darklajid 13y ago

Reeaally? So, is Chrome now filtering the internet to catch you entering your CC number to some vague service online? Because that's what we're talking about. Shopping (for an in app purchase, but still) online, in a browser. I wonder how Google checked if Amazon is PCI compliant.. If you're entering your CC everywhere that's not something Google can (or should - no need for a nanny..) fix. There's no way in my world that Google _could_ be liable for these kind of things. You're trying to understand their motivation for banning alternative payment methods. We both have a theory. Mine is 'greed', yours is 'protecting the user and protecting the company against evil worldwide'. I really think you're giving them too much credit here.

rmrfrmrf 13y ago
There's a very clear difference between native apps and web apps in my mind. EDIT: I should make very clear to non-developers out there that, with a native app, you're able to display a web browser without a URL bar or any other UI, which makes it exceedingly easy to trick people into thinking that they're at an official PayPal site or other shenanigans that the unscrupulous dev wants to try. More information: https://developer.android.com/reference/android/webkit/WebView.html https://developer.android.com/reference/android/webkit/WebVi...
- ceejayoz 13y ago
  > EDIT: I should make very clear to non-developers out there that, with a native app, you're able to display a web browser without a URL bar or any other UI, which makes it exceedingly easy to trick people into thinking that they're at an official PayPal site or other shenanigans that the unscrupulous dev wants to try. Nothing's stopping a non-standard browser (Opera, Firefox, etc.) from doing that, and they're permitted on Android. Hell, you could do it on iOS, too.
  - rmrfrmrf 13y ago
    are you trying to miss the point?
    - ceejayoz 13y ago
      Are you? A custom browser can be designed to quietly send people accessing PayPal off to a phishing site just as easily as an app integrating a PayPal payment method. If Google's going to use that sort of attack as a reason to prevent non-IAP payments, they should be banning non-Google browsers too.

fauigerzigerk 13y ago

So where does that leave your "do the dirty work yourself" argument? Apparently you don't want developers to do the dirty payment systems work themselves. Neither does Google. So I suggest you reconsider your rather hostile attitude towards the developer who complained about Google's inactivity.

rmrfrmrf 13y ago
Wait, now I'm the hostile one? lol ok.