News for hackers. Stuff that matters.
Re:Flutter: the good, the bad and the ugly by ryanwaggoner on Friday November 23, 2018 @05:51PM (#18519354)
I haven’t used their app, but scaling an app isn’t actually that difficult if the backend can handle it. I don’t think that their use of RN is relevant here unless you think there’s no way that a native iOS app of similar complexity couldn’t be built by two devs? But then you’d have to explain all the counterexamples, or even where a solo dev builds an app that goes viral and gets millions of users...
Re:Flutter: the good, the bad and the ugly by isoskeles on Friday November 23, 2018 @08:04PM (#18519824)
"Scaling" an app doesn't simply mean being able to use it on many devices (hence, "if the backend can handle it"). It also can mean you're able to be productive when adding new features to the application.
Re:Flutter: the good, the bad and the ugly by ryanwaggoner on Friday November 23, 2018 @09:38PM (#18520140)
I specifically was referring to scaling to millions of users. I’m a solo app dev consultant and some of the apps I’ve worked on have had big spikes of users. No big deal.

It’s kind of like saying your frontend framework is awesome because it scales to millions of users. Well yeah, they’re all running it on their own machines, so assuming you can deliver the code to them and the backend can handle it, you could scale to quadrillions of users.

Re:Flutter: the good, the bad and the ugly by chrisco255 on Friday November 23, 2018 @10:07PM (#18520235)
Yeah but the more people that use your app the more tested it gets. The more gnarly edge cases crop up, the bigger the impact if you accidentally ship buggy features, etc. Scale means even your front end has to live up to a higher quality bar. And given that app store downloads are driven by reviews, it's even more critical to avoid bad performance than on the web.
Re:Flutter: the good, the bad and the ugly by ryanwaggoner on Saturday November 24, 2018 @10:15AM (#18522335)
That’s true, and numerous people in this thread report that their app is nothing to be proud of.
Re:Flutter: the good, the bad and the ugly by k__ on Friday November 23, 2018 @07:04PM (#18519601)
"airbnb abandoning it shows it's bad, but other companies using it successfully doesn't sbow it's good!"
Re:Flutter: the good, the bad and the ugly by nv-vn on Friday November 23, 2018 @08:45PM (#18519952)
Abandoning something takes more work than using it, since it adds the cost of a rewrite. If Airbnb adopted framework X that wouldn't make me confident in framework X -- they haven't even used it yet! If they used it for a long time that would increase my confidence in X (in the absence of evidence to the contrary). But if everyone else started abandoning X I'd take Airbnb's experience with a grain of salt. I get that Discord is able to do well with it, but that doesn't mean everyone is able to do well with it depending on their needs. And who knows, maybe Discord is having just enough trouble that it hurts but too little to switch.
Re:Flutter: the good, the bad and the ugly by chrisco255 on Friday November 23, 2018 @10:05PM (#18520228)
Re:Flutter: the good, the bad and the ugly by ryanwaggoner on Friday November 23, 2018 @09:40PM (#18520147)
I was making a tongue in cheek retort about it “clearly” meaning that, since person I was responding to said it clearly meant they were dysfunctional. Probably could have made it more explicit.

I do think that scaling an app to millions of users says basically nothing on its own about the app framework / code quality itself. You’re scaling across as many devices as you have users. There’s no challenge at all there on the mobile dev side.