4 ms·
It's not clear what you're arguing for or against. Google Pay is a product with multiple features and one of them is being phased out. What's that to do with th
by jasonvorhe 6y ago
It's not clear what you're arguing for or against. Google Pay is a product with multiple features and one of them is being phased out. What's that to do with the benefits they're claiming from the rewrite of the mobile app?
- fastball 6y agoLet me try: > Flutter 2 supports web now! > We've re-written GPay in Flutter 2! > We're dropping support for using GPay on the web...
- dimator 6y agoThat doesn't follow. There's any number of reasons the web app would be shut down, usage statistics being the most likely.
- oblio 6y agoThey claim a huge reduction in source code line count. After they've just decommissioned their web app...
- fastball 6y agoYes, exactly, it doesn't follow. You've just re-written your app using a framework that allows you to run one codebase in multiple places, including the web, and instead of doing that, you decide that you no longer want to support the web at all.
- ehsankia 6y agoThe web version isn't shut down, but losing crucial functionality. If Flutter let's you run the same code across multiple platforms, then what reasoning is there for one platform getting less functionality after switching to a framework that, if anything, should increase cross platform feature match.
- The_rationalist 6y agoFlutter web isn't production ready, it's false adversiting.
- deleted 6y ago[deleted]
- AlphaSite 6y agoI think it’s disingenuous to imply that the savings were purely from sharing a code base vs removing features.
- SamBam 6y ago"I have a website and a mobile app. I unified my codebase with Tool X and saved a million lines of code!" "Didn't you simply delete the website?" "Yeah, what of it?"
- garrtt 6y ago> removed feature disparity After April 5, I will have to use the app so that I can get back functionality that I once had on the web.