Hacker News Reader

Comment by jasonvorhe | Hacker News Reader

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?

View on HN

"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?"

Let 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...

That doesn't follow. There's any number of reasons the web app would be shut down, usage statistics being the most likely.

They claim a huge reduction in source code line count. After they've just decommissioned their web app...

Yes, 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.

The 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.

Flutter web isn't production ready, it's false adversiting.

I think it’s disingenuous to imply that the savings were purely from sharing a code base vs removing features.

> 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.

Reply on news.ycombinator.com