6 ms·

> Google Pay switched to Flutter a few months ago for their flagship mobile app, and they already achieved major gains in productivity and quality. By unifying

by garrtt 6y ago

> Google Pay switched to Flutter a few months ago for their flagship mobile app, and they already achieved major gains in productivity and quality. By unifying the codebase, the team removed feature disparity between platforms and eliminated over half a million lines of code. from pay.google.com > Starting April 5, you won't be able to use pay.google.com to send and receive money from other people. To send and receive money, use the new Google Pay app.

shepherdjerred 6y ago
The easiest way to get rid of 500,000 lines of code is to delete your website
oh_sigh 6y ago
The website and the app are two different things.
- buzzy_hacker 6y ago
  > the team removed feature disparity between platforms
  - ewindal 6y ago
    Still doesn’t explain why you think removing LoC in a mobile application removes features from a web application.
    - ComputerGuru 6y ago
      The web application was deleted. That means there is no feature parity to factor into consideration.
      - ewindal 6y ago
        They are obviously talking about feature parity between the platforms android and iOS that their _mobile app_ targets. You cannot be this dense.
  - oh_sigh 6y ago
    Platforms being ios and android, not mobile and web.
rp1229 6y ago
The new Google Pay app on iOS is incredibly sluggish -- animations stutter, switching pages has hesitations. I'm not sure what they mean by "quality" in this case.
- eseidelGoogle 6y ago
  [Flutter Eng. Dir here] We were also not satisfied with the performance of the initial GPay release. We've been working with the GPay team the last couple months and have made significant improvements within both Flutter and the GPay app. Hopefully the next release of GPay will be out soon and others will be able to see the progress we're continuing to make with the team.
  - greatgib 6y ago
    so, if I read you well, you agree that Flutter or what you did with it clearly sucks? But still, you don't care that the Google blog post lie by telling the opposite of the real dev experience and the application user feedbacks?
  - deleted 6y ago
    [deleted]
  - ignoramous 6y ago
    Thanks. Not related to Flutter but Google in general: I recently hit a hard-to-reproduce bug with Jetpack's LiveData for which there's already an open issue created by a third-party developer. I don't recall but it had been open since 2018 with no updates whatsoever from Google engineers on its progress. And therein lies a frustrating problem for engineers not working at Google but using Google tech. There is simply no alternate universe where a third-party team gets the level of access the way you described the Google Pay team did. Of course, it helps that the stakeholders are in the same company, but my point is, shouldn't there be a Flutter Foundation where every developer can feel at home on equal footing with other Googlers? Flutter is so promising, and yet, at the same time, I don't want to end up being slave to its complexities with no way out as a third-party small development shop. Despite that, I'm 99% porting my cross-platform app to Flutter after strong reviews from other developers I know.
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 ago
  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...
  - dimator 6y ago
    That doesn't follow. There's any number of reasons the web app would be shut down, usage statistics being the most likely.
    - oblio 6y ago
      They claim a huge reduction in source code line count. After they've just decommissioned their web app...
    - fastball 6y ago
      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.
    - ehsankia 6y ago
      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.
      - The_rationalist 6y ago
adam12 6y ago
I have confused Google Pay with Google Play twice this week. I wonder how many other people get confused by this.
alfalfasprout 6y ago
Google pay is utter trash. Crashes and super slow. What quality are they talking about??
deleted 6y ago
[deleted]

by garrtt 6y ago

shepherdjerred 6y ago

The easiest way to get rid of 500,000 lines of code is to delete your website

oh_sigh 6y ago

The website and the app are two different things.

buzzy_hacker 6y ago
> the team removed feature disparity between platforms
- ewindal 6y ago
  Still doesn’t explain why you think removing LoC in a mobile application removes features from a web application.
  - ComputerGuru 6y ago
    The web application was deleted. That means there is no feature parity to factor into consideration.
    - ewindal 6y ago
      They are obviously talking about feature parity between the platforms android and iOS that their _mobile app_ targets. You cannot be this dense.
- oh_sigh 6y ago
  Platforms being ios and android, not mobile and web.

rp1229 6y ago

The new Google Pay app on iOS is incredibly sluggish -- animations stutter, switching pages has hesitations. I'm not sure what they mean by "quality" in this case.

eseidelGoogle 6y ago
[Flutter Eng. Dir here] We were also not satisfied with the performance of the initial GPay release. We've been working with the GPay team the last couple months and have made significant improvements within both Flutter and the GPay app. Hopefully the next release of GPay will be out soon and others will be able to see the progress we're continuing to make with the team.
- greatgib 6y ago
  so, if I read you well, you agree that Flutter or what you did with it clearly sucks? But still, you don't care that the Google blog post lie by telling the opposite of the real dev experience and the application user feedbacks?
- deleted 6y ago
  [deleted]
- ignoramous 6y ago
  Thanks. Not related to Flutter but Google in general: I recently hit a hard-to-reproduce bug with Jetpack's LiveData for which there's already an open issue created by a third-party developer. I don't recall but it had been open since 2018 with no updates whatsoever from Google engineers on its progress. And therein lies a frustrating problem for engineers not working at Google but using Google tech. There is simply no alternate universe where a third-party team gets the level of access the way you described the Google Pay team did. Of course, it helps that the stakeholders are in the same company, but my point is, shouldn't there be a Flutter Foundation where every developer can feel at home on equal footing with other Googlers? Flutter is so promising, and yet, at the same time, I don't want to end up being slave to its complexities with no way out as a third-party small development shop. Despite that, I'm 99% porting my cross-platform app to Flutter after strong reviews from other developers I know.

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 ago
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...
- dimator 6y ago
  That doesn't follow. There's any number of reasons the web app would be shut down, usage statistics being the most likely.
  - oblio 6y ago
    They claim a huge reduction in source code line count. After they've just decommissioned their web app...
  - fastball 6y ago
    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.
  - ehsankia 6y ago
    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.
    - The_rationalist 6y ago

adam12 6y ago

I have confused Google Pay with Google Play twice this week. I wonder how many other people get confused by this.

alfalfasprout 6y ago

Google pay is utter trash. Crashes and super slow. What quality are they talking about??

deleted 6y ago

[deleted]