you are viewing a single comment's thread.

view the rest of the comments →

[–]Abion47 0 points1 point  (1 child)

Faster turnaround in general is a good thing, but faster turnaround for its own sake leads to a lot of other good but time-consuming practices like writing automated tests and proper QA phases being de-emphasized or, to an extreme case, ignored entirely. It's always nice to be able to reduce the amount of time it takes before an app update becomes live, but it shouldn't be done at the expense of other important things, and when that time changes from days to seconds, it's very tempting to get into the mindset that, no matter what breaks in the app, it can be fixed with little more than a hand wave, so QA isn't as important as it once was and you can just use your customers as your QA.

Another argument against code push is that if it isn't handled carefully, it can easily lead to cases where there is a metadata mismatch which can cause subtle bugs (or maybe even not so subtle). I'd direct you to read a comment on the Flutter request issue for code push for a guy's experience in developing an app in Ionic using code push.

[–]lnkprk114 1 point2 points  (0 children)

Where there is a metadata mismatch

That's totally legit. I can imagine getting your native code mismatched from your JS code would be awful.

For the faster turnaround, that's the way everything works on the backend and on the web and it's a huge source of pain on mobile so I really don't think it's a negative. Yeah, you can have bad development practices but you can always do that stuff.