The new Google Pay repeats all the same mistakes of Google Allo
arstechnica.com
arstechnica.com
Google Play Music is the default, preinstalled music app. It's discontinued and can't even play my local MP3s anymore. YouTube Music is unfortunately worse. Play Music can't be uninstalled.
Google Photos is the default, preinstalled Photo Gallery app. Part of its service is discontinued. It can't be uninstalled.
https://blog.google/products/photos/storage-changes/
> Starting June 1, 2021, any new photos and videos you upload will count toward the free 15 GB of storage that comes with every Google Account or the additional storage you’ve purchased as a Google One member.
> Any photos or videos you’ve uploaded in High quality before June 1, 2021 will not count toward your 15GB of free storage. This means that photos and videos backed up before June 1, 2021 will still be considered free and exempt from the storage limit.
Reading further up this comment chain:
"I think he means that uploads beyond your free Google storage are not free anymore, not even for Pixel users."
Future photos, after June, will not be "grandfathered". Only existing ones are. This is the part of the service that has been canceled.
Except with Samsung you don't really know what you're uninstalling because a bunch of apps are weirdly named and not documented at all which leads one down the rabbit hole of inventorying each app and the permissions it has.
Android is a mess.
Now the app is gone and phones have removed the IR Blaster.
Compare apples to apples - Samsung and their Android version are a mess. Most vendors do the same because they can and to differentiate themselves and earn extra money ( like having Facebook crap preinstalled). Android would have never worked if it weren't so open in the first place, and at least the workarounds are well documented and you can usually flash with LineageOS or something; it doesn't help your average Joe, but each manufacturer having their own custom OS with the same crap wouldn't have helped him either.
Well I went through three of them with T-mobile and all 3 had serious issues which varied, but all 3 had a very serious battery issue.
All 3 phones were new out of box, and all 3 needed to be charged multiple times per day, probably about 4 with light use. All 3 got hot, and I believe the culprit on all 3 was the front screen fingerprint reader. Upon checking advanced battery usage tab, screen took up 98% of the battery, something I've never even heard of.
Constant random reboots, loss of signal and having to reboot to re-obtain, so hot it was uncomfortable to hold or have in pocket.
I thought about getting a 7t McLaren or whatever, but decided against it due to lack if 5g at the time.
I really hope they ironed out the issues because I'm definitely over Samsung and can't wait to get rid of my current S20+. And the 8 was really a joy to use, wasn't even the pro version and seemed far faster than my s20. Shoot, it took me three failures to finally be forced to try another phone.
Edit: fix words.
With full charge on average I get around a day or two without recharging with mostly firefox, youtube, messaging apps open and some light gaming.
Battery saving mode gets me almost 1 hour more of usage when I'm at 15%
Haven't really had any signal problems and 5g isn't that much of an improvement around where I live so it's not really a concern for me but ymmv
Like Sony and Motorola used to be pretty good about that.
Problem is, it's hard to search those phone finder sites for "Android purity" so I have to dig deep to find out how bad it will even be. The more fancy features listed on the manufacturers marketing page the more confident I can be that the features are all preinstalled spyware that might offer a cute gimmick as a bribe, at best.
But some people might have to accept the presence of a Facebook shim for installation is such an incredibly mainstream proposition that they are in a vanishingly small minority wanting rid of it.
TBH, so is iOS if you start actually worrying about services running on the device that may not be necessary or helpful, but iOS just doesn't tell a regular user they exist.
https://web.archive.org/web/20210104200400/https://store.goo...
The only killer app that still keeps me on Android is Firefox with uBlock Origin. If Apple allowed functional 3rd party browsers, I'll switch in a heartbeat.
uBlock on Firefox doesn't have that limitation, and if you use Firefox on desktop you can important synchronization between those.
But:
* The filtering language is basically just ABP rules.
* There is only a cap per “extension” so apps with lots of rules just expose many extensions.
Also, the qualitative experience, subjective as it is, is so much higher for me, having owned both Android and Apple.
That said I wish open source phones with Linux were a thing (not just Purism, but popular in general)
Android allows app to read gps status, do background stuff that is impossible on iPhone:
- you can't upload photos using e.g. Google Photos or Nextcloud in the background
- there are no custom apps that could do phone tracking (it is available to find my device) e.g. like GPSLogger on Android
Can you integrate a ~smart/dumb watch to do action that you want? (e.g. send a http request, make a call)?
Basically iPhone doesn't have Tasker like functionality and for me that is a no go.
Also is there a way to search for an app that is installed or should I still browse a long list and play "finding nemo"?
The iPhone does have a search for apps. Plus they now also will group your apps into categories on the last screen.
And apps like Google Photos on the iPhone do upload photos in the background.
You need to start the app and only then they will notice the new photos. (my life is miserable because my wife has iPhone and I have to deal with strange limits on iOS).
You are very much behind the times here. The newer Android (since 10 I think?) behavior for the last 2 years are permission prompts just like Apple. In fact many apps are not allowed to request background location updates anymore either.
I'm on Android 11.
You can. I use PhotoSync to upload my photos in the background to my Nextcloud server via WebDav. Nextcloud and Dropbox have their own special functionality to automatically upload photos in the background.
You can certainly upload/sync to your personal NAS at home with third-party apps. Many of my beta users use Resilio Sync, PhotoSync, or SyncThing. Synology and QNAP both have their own proprietary sync apps as well.
1. sudo apt-get-install android-tools-adb
2. Connect phone using usb, choose file transfer
3. In terminal type: adb shell
4. On phone allow dialog that appeared
5. In terminal in adb shell type: pm list package
6. Find which app is it and uninstall it: pm uninstall -k --user 0 com.facebook.servicesThe problem GP is pointing at is that uninstalling an unwanted app shouldn't be hard like that.
For a programmer sitting in front of a desktop that already has Linux on it, following those instructions would take less than five minutes. Easy.
For a typical Android user, they wouldn't know what they were looking at even if they had a Linux machine, which they don't. And would then get turned around by a simple typo like "apt-get-install" instead of "apt-get install" if they even make the attempt.
But because it's already "easy" for the people with the expertise to make it easier, the only people who could solve the problem are the people not experiencing it.
This command does not however always work (or at least wouldn't for some bundled software in older Androids).
Its more that companies provide some hard to use escape hatch for their anti features which silences all criticism "You just run this command" while still keeping it out of the hands of the normal user. The problem has already been solved, you don't have to run abd to remove apps on android, unless the app is specifically preventing you from using this feature.
https://github.com/A2L5E0X1/debloat-adb
Sometimes the scripts on xda-developers come bundled with an older adb version specifically because they don't expect people to know how to install it themselves.
Although, on a second thought if a user then decides to run the `debloat-google.sh` without knowing what he does the user might end up quite frustrated as a result. So I guess you're right.
I think google has been gradually restricting what adb is able to do.
Who writes makefiles such that 'make install' doesn't have 'all' (or whatever the default target is) as a dependency? It's even mean these days not to automatically configure with the default options if no configuration has previously been specified.
Thus grandma should really only have to do the much simpler
(mkdir /tmp/granny; cd /tmp/granny; curl https://my.example.com/download/latest.gz|tar xfpBz - ; cd * ; make install)How has she made it this far in life?
And this is even worse with brands like Oppo. They have good hardware but so much crap wasting battery and cpu running on by default which cannot be disabled or uninstalled.
I was able to disable/uninstall with adb a lot of it but with every "Security update" it gets right back on the phone and then I have to do it all over again (SOs phone). Also it's getting more and more restrictive and even adb fails on half of these apps like Game center, etc nowadays :/
On the other hand clearly carriers and vendors loading up their products with crapware and junk is a serious problem. Lets be clear though, this is about poor judgement, bad execution and incentives that are severely miss-aligned between vendor and customer. It's not fundamentally a technical issue.
adb shell pm disable-user --user 0 com.samsung.android.email.providerAs another comment mentioned, you can disable them for the single user over adb. On my sony phone you can disable OEM apps the same place you'd normally uninstall them in the GUI.
It took some clicking (tapping?), but I disabled a bunch of cruft 2 years ago when I bought the phone and haven't had any issues.
> any app
I was not able to uninstall the Samsung Pay Framework (com.samsung.android.spayfw) with this method; it hangs forever. Trying to uninstall via the gui tells me that it cannot be uninstalled since it is required by the device administrator. Going to the device administrator screen shows nothing enabled, so I cannot disable whatever is preventing the uninstall.
Instead I'm inundated with societal shit: amber and silver alerts at 2am (yes I have been woken up when my phone was on silent in the middle of the fucking night. What the fuck am I going to do while I'm boondocking in the middle of the ari-fucking-zona desert to help a child abducted by a dad at 2 am in the state of Washington - but the parent's are originally from Phoenix?)
I'm so damn sick of Android.
If it's a basic operating system functionality (dealing with files, viewing photos) it's fine if you can't uninstall it, but then it better not come with any kind of separate user agreement, separate updates, changes in functionality, upselling attempts etc.
Which is the case for Google Photos. It is also a messenger (not kidding), shows notifications with "moments" it automatically created from your photos, lets you create photo books which you can order and so on.
I would prefer a smaller default gallery app with Google Photos being an optional extra.
I checked the Google Photos app and opened my account settings. According to the information in the app, free & unlimited storage of photos in "high" (not original) quality will still be available for me after June 1st 2021. But uploads from other devices will count toward the available space quota.
So Google Photos works as always on the Google Pixel 3a.
It's a clean Android and it's utterly well supported on the Pixel line of phones.
Google only supports these phones for a few years. That is useless to me, who intend to use my tools for much longer than that. LineageOS has provided that support with a minimum of fuss.
I'm reminded of Paul Graham's essays about this and payments ticks two of the major themes: it's both unsexy and it's a schlep. And that's why Google won't succeed in this space.
Apple uniquely seems to have maintained the ability to tackle these problems. I remember when Apple Pay launched and was derided (here and elsewhere) but every few weeks there'd be another announcement where another group of financial institutions were brought in to the ecosystem. You keep plugging away at that, customers will start using it and after years of schlep you'll have mature payments infrastructure.
Google chat apps were a meme internally even when I was still there (2017). Deprecating Hangouts features, copying Slack, creating new orgs to make the same mistakes all over again (but hey, lots of people got promoted). It was a joke and still is.
And all they had to do was copy iMessage. That's it. Apple had the foresight, market power and wherewithal to push iMessage onto resistant network operators (who were all too happy to continue nickel-and-diming customers with massively profitable SMS charges long after any cost arguments had disappeared).
I mean, have millions of pissed off users when you're a startup and you're probably toast. Have millions of pissed off users at Google, and as long as they are still using Google search, and viewing webpages where Google ads are displayed, and it probably doesn't matter, at least in the short term.
Not only that, but Google monetarily incentivizes frequent product (re)launches - it's the quickest way of getting a promotion and/or more bonuses, but maintaining an old product does nothing for your career or your team (unless you're Search). At some point, I assume the Google brand will lose enough goodwill that someone in leadership will finally address this.
Disclaimer: I'm not a Googler, but information on how Google measures performance and promotes staff is pretty much public information now.
Probably now part of the institutional culture and impossible to eliminate.
Wrong. Googlers are just like other normal humans and they respond to incentives presented to them. I worked at Google and observed their promo / bonus / compensation practices closely. The safest way to get big bucks was to launch something, invest some metric to measure something and make sure there is a lot of movement on that metric, repeat that N times in your promo packet and get your peers to do the same in their peer reviews, get promoted and immediately jump to the next sexy project.
Maintaining an existing service wasn't considered important early on. Then it started getting lip service. After a few years, it started getting some token awards every quarter or so. Finally, some smart VPs even started promoting 1-2 maintainers just to make a statement and have those counter-examples in their arsenal in case someone brought up the incentives for maintaining existing products. But the vast majority of promotions still went to launches.
When people see their peers getting promoted and earning more money by showing "leadership" and "launch"ing some new project vs. optimizing for end user happiness then this will be the outcome.
Changing culture is very hard because all the people who decide on the employees promotion are those who hacked their way up. So it probably will never change
Is it that new products/features == growth in share value for shareholders?
I'm sorry I can't hear you over all this money roaring past my ears! Beside Adsense the rest is just a hobby/status game for employees - and it shows.
Though it's understandable that shareholders are just looking at the next quarter.
Murdering dictatorships seem to have a problem letting go of control. So I'm saying yes, they had the wrong people advising them.
Ignoring the giant elephant that Saudi Arabia didn't even feign "don't be evil", in order to engage in global market capital. Not even temporarily during the IPO, they could have put on their good face to the western world.
Instead the top down crafting this IPO gave the "okay" to murder to WaPo journalist and create a global PR disaster because their feelings got hurt.
Yet as you mention they still need to diversify, eventually. I wonder how it all will turn out looking back in 5-10yrs.
The reward structure for quite a few of these (FAANG) companies is geared towards launching new features and/or products.
There is little incentive to improve existing software (as an IC). Which is why, for example, every "feature" at Amazon has a press release.
Behind every press release is a promotion for someone.
I'm devastated.
I've owned virtually every Nexus/Pixel phone, and have been an android user for 10 years. When I purchased my original Motorola Droid (after standing in line outside the Verizon store in 2009) I also decided to pay for gmail via (what was then branded) Google Apps for your Domain, under the assumption that if you're paying for it, you have more control, you can move the email address away from the custom domain, etc.
I've been nothing but happy with it for 10+ years. Sure, every now and then some newly-launched google product wouldn't quite integrate well, but especially over the past 5 years or so it has been "just another google account".
When I try and install the new Google Pay, I receive an "Account not supported: Enterprise accounts are not supported on Google Pay, please sign in with a personal account" message.
I really hope this is fixed soon, or an error, or there will be some alternative. I literally have given google money at every opportunity, but soon they will take away my ability to give _other people_ money with my phone.
You could also get another credit card, but what a hassle.
Obviously I cancelled Workspaces, but now my Fi account barely works, and I don't have the time/energy to deal with their idea of customer support (a community forum...) to fix it.
There was some bad UI with the web. It would pop up a window to warn you to only send money to people you know, but it was a window you couldn't move to see who you were sending money to, in case you clicked the wrong person!
But that's better than the experience I had with the app when I paid at a McDonald's recently. I was expecting a screen which said something like "You are about to pay $9.72 to McDonald's Corporation. CONTINUE/Cancel.
Instead, when I put my thumb on my phone's fingerprint sensor, here's the feedback I got: (vibrate)
No information on who I was about to pay or how much I was about to pay. And afterward, absolutely no information about who I just paid or how much I paid them.
I went into the payment history screen and they payment wasn't there either, although it showed up about a minute later.
How is that acceptable?
I would NEVER use the app unless I lost my wallet!
Using the Google Pay app at a point of sale was a terrifying experience.
Obviously not.
They’re different things: approval and notifications seem pretty appropriate for an app.
Amount and payee authentication is unfortunately not. It would require updating all payment terminals in the field – the last time we tried that (i.e. introducing chip support) it took literally decades (and we're still not done).
You don't need to unlock your phone to pay amounts under 30€ in my country. You just need the screen to be on.
I'm quite glade it's like this actually. If I had to fiddle with the phone every time I wanted to pay, I would just use my card.
nitpicking, but contactless cards as far as I am aware cannot be "skimmed" (a process of copying the information from a magnetic stripe and creating a cloned card). If the payment terminal can handle a chip, it will refuse to downgrade the security. In addition, countries are marked as chip only, which means it's almost impossible to get a bank to authorise a transaction for a card that should have a chip in a country where most readers are chip-capable. And if the card was suddenly used in a non-chip region, any good bank would block it.
All you can do with contactless is relay the signal over the internet, but that introduces delay and can sometimes be detected by the reader.
That's unfortunately how the contactless payments protocol works. Chip cards don't have a display, so user-visible on-device payment confirmation was never a design goal.
There's been some attempts in introducing it (apparently with mixed/bad results, since it's not a thing anymore), but it's ultimately not possible: Since the final payment amount is often not known at the time you tap/dip/swipe your card, what you'd see on your phone would differ from what is ultimately charged.
Arguably, not showing an amount rather than an estimate that will usually be either way over or under the actual amount is better.
As a foreigner, I have trouble understanding this.
How can the final amount of a transaction not be known when you are paying it? Is that one of the usual nonsensical shenanigans stores like to play with taxes in the USA?
This is different from having different amounts in the chip transaction and in the "actual" transaction amount fields.
The former is something that the card/phone can show and verify, as that is the actual amount you're authorising, even if you don't "spend" all of it.
You can also simply wait for the receipt to be closed before tapping, then the terminal will show you the full amount.
I - for example - use the pre-transaction tapping when buying groceries, it means I can just walk out when the last item is scanned.
It is a security risk - an attacker may add some expensive item to the session - but I think I can take it, the terminal will still show the total at transaction close.
Accordingly, this is what customers have become used to, and this assumption has been further baked into POS software.
Rather than forcing all POS vendors and customers to change this habit, the EMV standard was relaxed for the US (and a few other markets where this is common) to not necessarily include the final transaction amount in the payment data signed by the chip.
With chip cards restaurants now tend to bring the card machine to the table. This way you can enter the tip on the machine and complete the payment without the card leaving your hand. I don't know if this is because the machine is there anyways or because chip payments need to know the amount when the transaction is authorized.
In some countries, the switch from signature to PIN has coincided with the introduction of chip cards, and given that the terminal needs to be brought to the customer anyway for those (or vice versa), it's just simpler for everyone involved to include the tip amount right there.
Of course, the issuing bank may charge some extra fee on top afterwards, but the amount that the chip card sees and signs should be the exact same number that the POS system would print onto a receipt as the transaction amount.
That's written on the payment terminal. Google Pay is just a standard NFC payment. You might be prompted if the payment is large depending of the legislation in your country but for small amount, it's fast on purpose.
Of course this isn't how the payment system was designed as it was designed for cheap, simple cards. The saving grace is that you can perform a chargeback if the transaction is wrong. Not as elegant, but is basically as effective at the end of the day.
Untrusted by who? You?
The terminal is a trusted device in the payment system, and in most cases is the only trusted device in the store involved in the payment chain.
If I had to guess, I would say it is because they wanted to support some use-case that contactless cards currently do: presumably like I can pay at Safeway before knowing the amount - a feature I use very often to speed up the process.
In fact I would like the whole credit card system to be overhauled or replaced with a different system that gives consumers much more control over the access they give companies. Sure, some companies like online stores I might give full access like I do today as I plan to make many future purchases with different values, but I can also see a lot of uses for more restricted access like fixed monthly subscriptions and one time fixed-cost payments that don't give them access to charge me later.
The article explains why.
> Just like with Google Allo, SMS-based authentication means there's no desktop support at all. The Google Pay website is being stripped of all its useful functionality because a browser does not have a carrier SIM card and therefore can't be authenticated by the SMS-reliant system.
You are correct about the payment history though, mine was always missing huge chunks (sometimes weeks) of payments for some reason.
Not entirely sure why this story is throwing shade at Google Pay in India, since the service there has been a runaway success. It's a furiously contested space, but GPay came out of nowhere to grab the #1 or #2 spot depending on what metric you use:
https://yourstory.com/2020/12/google-pay-phonepe-upi-market-...
But I agree with the article that while going aggressively mobile-first/only makes a lot of sense in India, it's going to be quite different in a mature market like the US and the transition is going to ruffle a lot of feathers. The biggest sticking point is really how dysfunctional US banking is: in India, thanks to UPI you can pay anybody if you know their phone number, but this is not a thing in the US and that's why you can only do P2P transfers to other GPay users.
For what it's worth, though, I've been using GPay (outside the US) for quite a while now and I've never found myself wishing for a desktop client. P2P payments are almost always to people you're already messaging from your phone or physically interacting with.
From a UX perspective, it has been notoriously slow and is prone to failures. For example, if the transaction could not go through, it remains pending for 3-ish days while Google retries internally. For real-time transactions, like buying groceries from a street vendor, it isn't practical to wait so long to find out - and mostly results in people paying twice for a product.
Aside from marketing gimmicks and usage by vendors, who by the way use a single QR across 5 different UPI vendors, I'm not sure it really is a "runaway success".
Edit:
Another point to note is that GPay (and other vendors like PhonePe) went around sticking their own QR codes on every shop. This meant that if you wanted to pay by UPI at that shop, you had to install GPay.
This prompted NPCI to issue a circular and ensure QR codes were interoperable across UPI apps - but as I've seen, there still remain tons of shops which have only the GPay proprietary QR Code. Ref: https://razorpay.com/blog/npci-circular-on-upi-interoperabil...
Lethargy by vendors to move over to the new QR could also be one of the reasons why these 2 players hold the lions share in the UPI market.
I remember reading about some anecdote where a network of friends were doing thousands of transactions a day to game the scratch card system. I'm sure they plugged that loophole (if there was ever one) pretty quickly.
To be clear, the transaction isn't retried. The backend keeps trying to fetch the transaction status until it gets a definitive success/failure from the PSP/issuer.
I agree with your comment though; payments is a frustrating UX if the backend isn't nearly 100% reliable.
UPI in particularly has a dozen or so moving parts in the OLTP path each of which are 90-95% available at best.
From the insiders, I know that issuing banks aren't incentivised to invest in their UPI stack to make them highly available or reliable. That's because government has banned interchange fee on UPI transactions and it wants issuers to absorb the cost of maintaining their UPI stack. So the issuers let that tech stack languish doing their absolute minimum to keep it running.
This is a great example of forcing a party to participate in a transaction and at the same time not pay them to maintain the system. It ends up being counterproductive in terms of frustrating UX and more.
Or their UPI ID. it looks something like "myname@bankname"
With the above in place, it is just a matter of inputting your phone number into gpay, and it will send and receive a flurry of SMSes, figure out all your bank accounts and their details, and add them into the app. Very seamless and kind of scary.
Not true. You need the UPI ID of the person, which may probably be phone@bank or phone@paymentsbank. If you assume that everyone is using only Google Pay (or Paytm or PhonePe or Amazon Pay or pick another provider), then those providers would know the UPI ID to connect people to for payments. For people who don’t use these payment services but do have a bank account (say, HDFC or SBI or ICICI), there’s no way you could pay them only by knowing their phone numbers without knowing the bank they have the account with and the bank suffix they use for the UPI ID.
The article mostly seems to be complaining that good in India != good in US and that Google needs to adapt to the different markets.
You and others keep saying this, but you really need to mention which non-English languages you are talking about as at least some of them are pretty good.
I've been using ddg as a default engine and wasn't aware of this. (also !ddgde is a lot more to type than !g)
With google, I sometimes wish I had an easy switch like that when the terms are also available in English as currently this makes their results useless.
!ddgde is indeed a bit long, but as most of my searches are not local, I can live with it ;)
It's not "You and others keep saying this... provide some examples".
It's that you have a tiny scope of what you consider to be the world.
No, that’s something you put into my mouth.
This is why I was asking. Unlike others, I explained which language works great. "Doesn’t work" is useless without saying what it doesn’t work for. "Does/Doesn’t work for language X" is actually relevant information.
One of my clients have integrated their intranet solution with Microsoft and if I search on Bing while logged in I get relevant results from both the Internet and the company network!
Two observations:
- I'd not accept if Google did this (like many others I was a fanboy, and like someone said: Google have worked hard tp make me dislike them - and they have now succeeded. Between years of insultingly mismatched ads, search quality dropping 10 years ago and staying lower than before and the whole witch hunt affair a few months ago I now do dislike them.)
- Google had this, or at least search on my machine and on internet working with Google Desktop Search already back in 2006! (Of course they killed GDS after I think they'd ruined the market for everyone else by pushing the best solution for free for a couple of years.)
Edit: I suppose YouTube technically counts as a Google service, which I also use with high frequency.
That’s honestly the most important portion of trip. I don’t need to be navigated once I am driving on the highway.
Global market shares as of Feb. 2021 [1]:
* Google 92%
* Bing 2.69%
* Baidu 1.33%
* DuckDuckGo 0.64%
Alphabet made $182 billion last year, with a profit of $34 billion, making it the fifth most profitable private business in the world [2]. Much of that is off the back of search and AdWords.
The whole point of DDG is that I do not want a hyper personalized search experience, which may lead to worse top results, but probably not stop me from finding what I want within the first page of results, which for me is a more than great trade off for protecting my privacy.
Even if it's barely usable, I'm tired of the constant tracking and ads. Anyways, Google is already so full of SEO spam that I usually have to type in "[search term] [relevant web site]", and even DDG can handle that.
Summary: duckduckgo traffic seems to be increasing approximately exponentially for a while and as far as I can see the trend still continues.
This is extremely interesting, here are three thoughts:
- their are already profitable and have been for a long time already. This is probably very good money (operating costs probably scales slower than revenue)
- it means more search data for DuckDuckGo which will allow them to improve their engine
- it improves their position when they deal with partners (like Bing)
FWIW - I wrote this plugin[1] to recreate my workflow[2].
[1] https://github.com/jmathai/elodie/tree/master/elodie/plugins...
[2] https://medium.com/swlh/my-automated-photo-workflow-using-go...
Because with "new" Google Pay, all of those membership cards are gone. They didn't just not migrate the data over; this isn't a feature present in the new one. I don't see any reason to continue using it. Apple Pay is working better for me for tap-to-pay, and I'm instead trying to replicate some of the old membership card organization with Apple Wallet, albeit without much success yet.
(Can't believe we have to use "old"/"new" delimiters here either, while Google gets to pretend it's the same thing.)
https://support.google.com/googlepay/topic/10167683?hl=en
* I work at Google but not on Google Pay
Well, there's also the "old old" Google Pay...or Wallet, or whatever it was called when I tried to use it. That didn't work well, thereby helping to accelerate the end of my Android experiment. But apparently, according to a friend at the time, the new Google Pay worked much better. But not well enough, obviously, because now Google is rolling a "new new" Google Pay.
I quit using a lot of Microsoft products because of rebranding bullshit like this. Which one do I use, and why is this one better? Oh, if I'm going to go to all that trouble, I'll just try a different product entirely, then.
> (...) The old GP and the new GP were totally different teams, not even operating out of the same country (old GP was based in SF, USA - new was based out of Singapore). Around fall of 2018 the Singapore team was given complete control over all of Payments at Google due to the success of their app in India. The US based team was completely powerless and had to watch heartbroken as it was decided to shut down their product, the one they had been working on for 10ish years, in favor of the new GP. (...)
Thanks for the link.
But yes we all get paid, almost always whether the software (or product) is good or bad or useful to the world.
Yeah but I'm sure that dev team used the latest technology, like Flutter or Kotlin or something, and had an excellent well paid team.
Now the repo isn't some old dirty Java codebase either (made by another team of half-genuises 5yrs ago, gross!). Don't want our users having to deal with old codebases, with all of those fully battle-tested features and quirks figured out (yawn), written in some boring language and using old frameworks! It's bad for business.
https://developers.googleblog.com/2020/09/google-pay-picks-f...
In fact, I have no idea if the 'Google Pay' that I know and use is the same as the one mentioned in this story. Do people in other countries have different apps from google, but named the same as my local apps? That's pretty confusing. I cannot see any P2P (person to person?) features in my app, just the 'add credit or debit card' functionality.
If I traveled to India and saw Google Pay was supported at a checkout, I'd absolutely try and use my app.. but perhaps would be in for a bad time. Who knows?
I live in Europe and had the same reaction as you, and I have com.google.android.apps.walletnfcrel installed, which shows up as the mentioned (old app) in the US Play store[1]. So I guess, as usual with Google: Maybe we're affected?
[1]: https://play.google.com/store/apps/details?id=com.google.and...
[1]: https://play.google.com/store/apps/details?id=com.google.and...
The reason I know this is because I was the same. I did well at school, did well at university, got good jobs in tech, and then tried to do a startup and failed hard because I wasn't nearly as clever as I thought I was, and I had completely misunderstood the product I tried to make. It was quite the lesson.
You can be considered bright by other people or some metrics, yet make very poor life choices.
Another problem is again wrong incentives. If a product usage isn't in the hundreds of millions the management usually does the "move fast, break things, launch the new thing, get promoted, switch teams, rinse and repeat" approach which is a time tested strategy.
Whatsapp won because it realised for normal people phone number based authentication is way way easier than username/password. It's almost impossible to hack, can't forget your password, and it's way easier to use.
It's actually extremely easy to hack in a targeted manner...
You can either do it with social engineering at range or even intercept the sms if you're physically close enough to the recipient
It's simply more likely that the US has more high value targets, has more criminals/grifters doing this kind of fraud/scam, and non-US media talks less about these identity theft events.
I agree that the US' lack of federally issued modern and safe credentials that then tie into the private sector is laughably painful. (But it's not like the rest of the world is that much better.)
The actual US voting systems are pretty okay (mail ballots, extremely low voter fraud, results are counted in a few days), the way that turns into representation is the problem. The usual news about voter ID laws are pure fascist voter suppression.
Every single argument against their current system and arguments against ID is what we all do here? Think you're too deep into their political rhetoric here and peddle misinformation.
Then there are other ways to achieve the same thing without SIM swaps. SS7 level rerouting can be done globally ("this phone is now roaming from within our network").
For the average user having no password is 100x more secure than the rubbish password they picked.
For the high value target the opposite is hopefully true, then again solarwinds123
Meh, I guess I was right.
So at this point I just ignore new google stuff.
Even assuming that they're any good, google itself will mess them up eventually.
When it was first released it was very smooth compared to all the competition and the cashback was also pretty good.
But just a few months ago they released a new update (GPay) and I don't know what they did but it is now unbearably slow. Checking bank balance only works in 2 or 3 tries and transactions can fail multiple times. Instead of focusing on that they decided to make an UI update that made the interface incredibly slow. Unbelievable.
I have moved on to PayTM for now (it is much better), but I will continue to keep an eye on it. Maybe it will get better.
There was this announcement about GPay is reimplemented in Flutter. It could be related to that.
https://news.ycombinator.com/item?id=26315915
I don't know why they would ruin such a fast, successful app like this.
I still haven't figured that one out, and I'm not going to bother with whatever the hell this is.
The mistake was naming them both "Google Pay".
Imagine if Microsoft had taken that approach when they built Xbox, they knew some products are a marathon not a race.
Starting to wonder if any of the decision makers there even remember what the early moments of a product can be like.
Xbox nearly died in development, as Bill Gates was none too pleased with the decision. Fries recalls Microsoft's "Valentine's Day Massacre" in which Bill Gates furiously ripped apart the development team for circumventing his original idea.
But yeah, it doesn't exactly inspire confidence either...
Edit: Photos is 2015, so just over 5 years old.
Out of those 3, I'd vote only Photos is successful. Whilst completely anecdotal, I don't know anyone that uses Duo or YTTV.
Located in Australia.
The CEO is a McKinsey consultant, smart guy, nice, but he's a politician on top of what are layers of well-meaning politicians.
Google was never a highly organized company, which was advantageous the start, but eventually the lack of real corporate product discipline overcomes the ability of the otherwise great product leaders to maintain coherence over time.
Even established products like YouTube, gosh it hasn't improved in a long time. The 'creator section' is abysmal and was in beta for years. Think of how much more innovation has happened in a short time on TikTok.
Most top-down orgs fail, or turn into other kinds of beasts like Oracle. Apple has been able to maintain fidelity thanks to a long-running founder who established quite a lot of cultural consistency. It's frankly weird how they fire well enough on so many cylinders but they are only 1 CEO out from the founder.
Even Microsoft's Product/Competitive focused approach has been consistent for them.
Google will still make a lot of money for now so there won't be any pressure to change for the foreseeable future but I really can't imagine anyone but the founders coming in to make that happen, but I don't think it's in their DNA.
Last time I read the new app was actually doing very well.
1.https://www.pymnts.com/news/mobile-payments/2020/google-pay-...
I get the whole interbank exchange weirdness, but still. Banks basically transfer money akin to using analogue switchboards.
The most modern standard is SEPA Instant Credit Transfer [1] which does transfers in under 10 seconds. As of right now 57% of European payment service providers have joined with this scheme.
--
[1] https://www.europeanpaymentscouncil.eu/what-we-do/sepa-insta...
- 2013: Google kills Google Reader for RSS feeds. Never found a replacement I was as happy with.
- 2014: I loved the first version of AngularJS. Angular 2.0 was a complete rewrite of the first version. Switched to learning React instead (now I'm a huge Svelte fan, for the record.)
- 2017-2018?: Forget what it was called now, but Google's services for domains stops being free. I've got several family members on that and didn't want us to all lose Gmail, so I'm currently paying ~$6 per person and pretending our family is a "business".
- 2019: Google kills off Inbox. My email organization goes to shit. I'm trying hey.com currently, but still waiting/hoping I can use my google "business" on that so emails come from that domain, not hey.com...
- 2019: Google kills off the Works with Nest API, and my new Home Assistant installation can't talk to my smoke alarm. I cancel plans to buy a Nest Thermostat and get an EcoBee instead.
- 2019: I migrated off of Google Play Music and over to Spotify when they started dismantling the former and pushed people to use Youtube Music instead.
- 2019: Google Chrome slowly turning into surveillance software pushed me to switch back to Firefox.
- 2020: Google Fit used to track reps/rest time when weight lifting, but they removed that for some reason. Along with everything else they removed, I used FitnessSyncer to migrate all my health data to Apple Health.
- 2021: Now, the "new" Google Pay doesn't have the membership card feature from the "old" Google Pay, so I've lost all that data now. I'm going back to a wallet full of membership cards unless I can figure out how to add arbitrary cards to Apple Wallet.
I lost most of my faith in Google years ago, and they're still finding innovative ways to disappoint me.
"Instead, you have to sign up for the new Google Pay using your carrier's phone number."
My preferred phone number lives in Google Voice, and I have a grandfathered T-mobile 'net30' plan, with a phone number I give to no one, prefer to never use, and only get junk calls and spam on. Which I'll probably use forever unless there's real competition again... or several cellphone technologies come out and they refuse to support newer connection types.
At least here in Switzerland I've found TWINT, which is pretty much the same as this new GPay, to be significantly more widely useable because all you need for a transfer is the phone number. It even works with iPhone users who don't necessarily have a Google account.
I find these different wishes kinda funny - neighbouring HN topic will have people complaining how everything is bound to a single Google account and this topic has people complaining why their financials aren't bound to a Google account :)
retire to somewhere else?
work in another country for a bit?
evaid a stalker?
This service is destined to fail in the long term, and doesn't fit my own needs in the short term. It's all but become a personal religious level belief for me to not sign up with anything that requires a phone number.
You give people the new phone number. It's really not that hard (and I'm writing this as an expat using multiple phone numbers :) ).
Australia has a better system called PayID. Every bank is required to be in the system and you can send money to anyone, to any bank with their phone number or email address. There is no 3rd party and no fees.