Deutsch English Français Italiano |
<MPG.40a0cd174fe8043798970c@paganini.bofh.team> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail From: Jim the Geordie <jim@jimXscott.co.uk> Newsgroups: comp.mobile.android Subject: Re: Samsung Wallet vs Google Pay Date: Sat, 4 May 2024 23:54:51 +0100 Organization: To protect and to server Message-ID: <MPG.40a0cd174fe8043798970c@paganini.bofh.team> References: <MPG.409f83d1f0ea877d98970a@paganini.bofh.team> <l9mc4kFeg3dU2@mid.individual.net> <v1525o$12v5a$1@dont-email.me> <edfhgkxdv5.ln2@Telcontar.valinor> <v164b6$1cjj9$2@dont-email.me> <1o9got62136hu$.dlg@v.nguard.lh> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Injection-Info: paganini.bofh.team; logging-data="2807060"; posting-host="+XbyLv1SaxDwJ2fBrKZCbQ.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A"; User-Agent: MicroPlanet-Gravity/3.0.11 (GRC) X-Notice: Filtered by postfilter v. 0.9.3 Bytes: 4436 Lines: 60 In article <1o9got62136hu$.dlg@v.nguard.lh>, V@nguard.LH says... > > Do you really want to give your very expensive smartphone to a table > jockey that doesn't tote around an NFC reader, but has to walk to a > terminal to register the transaction? When a waiter comes to my table > for me to pay my tab, he has no means of using my phone at the table. > Many restaurants do not have a front desk where you pay for your meal. > You're expected to pay before you leave the table. The waiters use > terminals to enter the transaction, not hand-held readers. > > I'd much prefer handing over a plastic card to a waiter who takes it to > a terminal to enter the transaction than hand them my phone with the > mobile pay app prepared to perform a transaction when the waiter gets it > back to the terminal. I rarely put my phone into the hands of others, > and even then with great hesitation. Getting a replacement card is > free. Replacing a phone is very expensive. Yep, there are still plenty > of retailers that have no means of reading your phone when you are not > at their front desk or cash register station, if they have one. > > What about the contractor that, say, cuts down a tree, and wants to be > paid? He has his phone, but can your mobile pay app using NFC connect > to his mobile pay app via NFC on his phone? I've seen many SOHO folks > that plug in a USB card reader into their phone, and that's how they get > paid by sliding your card through their card reader attached to their > phone. I've even had contractors that don't even have the USB card > reader. They have to manually write down the credit card number, CVV, > and expiration date onto an invoice that you sign. Wave the phone all > over the invoice paper, but it ain't gonna work. > > I see mobile pay apps as convenient only when they are so. That they > exist doesn't mean those apps are the most convenient payment method. > Many users don't leave their phones on in trying to preserve battery > power for when they do want to use their phones. Oh joy, wait to power > up the phone, hope it has enough power, wait for it to load the OS, wait > to load the mobile pay app, select a payment method, and then wave the > phone near the reader. Hardly convenient having to wait several minutes > to commit the transaction. > Where in the world are you that waiters don't have hand held card scanners. Do you really allow a waiter to wander out of your site with your debit/credit card? > Do the mobile pay apps run as a service? If not, how long does it take > to load them? No, not refocus to a backgrounded app, but to load the > app, and then select which card to charge? Android leaves apps > backgrounded until memory is needed for a newly loaded app whereupon a > backgrounded app gets unloaded. That means backgrounded apps eventually > get unloaded, and you have to load them again. If ran as a service, or > as a sticky app, Android will reload the service or sticky app when it > finds the app is not loaded. Otherwise, it's up to you to reload the > app. For various reasons, some folks use task killers to eliminate idle > backgrounded apps, but services get restarted or sticky apps reloaded > (and why task killers cause consternation amoung their users not > understanding why a killed app will reappear). > -- Jim the Geordie