They survived several rounds of cost-cutting at a large company by constantly convincing management to let them rewrite their mobile app in some new framework because of X.
Start out with the native implementations, then they did Xamarin, tried PhoneGap, went back to native, then to React Native, and now on to Flutter. The pair of them keep their jobs constantly rewriting an app.
Now and then frameworks does backwards incompatible changes so you might as well rewrite the app. If you continue with the old version of the framework you are stuck with either security holes, bugs or that google and apple changes something that downprioritize your app into oblivion.
And if the UI/UX does not significantly change every 6 months, your users will give you one star reviews and "Old looking and ugly" comments. I don't envy app developers.
Yea if a framework makes breaking changes to the point where you can't upgrade your app, that seems like it could be a recurring problem so after the first rewrite you might as well learn native code and write it there.
Disagreed, the vast majority of business problems with tech are solved with some form of CRUD which frameworks are perfect for. If your framework all of a sudden doesn't support your business needs either you didn't plan ahead well or your business simply outgrew it, which can happen once a business becomes complex enough.
Virtually nobody in software is incentivized to look at long term software costs. Startups need to move fast, project managers move on, devs need to keep their skills up to date to keep flipping jobs, and managers would need to become technical.
They survived several rounds of cost-cutting at a large company by constantly convincing management to let them rewrite their mobile app in some new framework because of X.
Start out with the native implementations, then they did Xamarin, tried PhoneGap, went back to native, then to React Native, and now on to Flutter. The pair of them keep their jobs constantly rewriting an app.