News for hackers. Stuff that matters.
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.