7

8 months ago, me and my teammate developed an API and a web application for one of our client. The API was supposed to be consumed by mobile app which another team was working upon. Now my suggestion for the mobile team was to use something like ionic or react-native. This was purely to keep technical debt on lower side since hybrid apps don't deviate too far for both Android and iOS platforms. But mobile team went with the native apps and developed two separate apps which both have some differences.

The client didn't even use the iOS app since past 6 months. Now all of a sudden she reported several bugs and the person managing the mobile devs put that all on us. I tested some of the bugs and seems like the same feature is working on Android but not on iOS.
Came to know later that the iOS developer who was working on the app had resigned and left the company exactly 6 months ago. Right after the apps first launch. And since then mobile team hasn't put any replacement person for the project. That fucker was trying to buy some time by putting it all on us.
And now here I am, experimenting again with Flutter. So far it seems quite decent.

Comments
  • 2
    And that is an use case perfectly describing a need for flutter, react native, ionic, etc. :D
  • 0
    Native app used to mean something. They distinctively look better than a hybrid app.

    Then something happened and native apps look exactly like web apps.
  • 2
    @iceb

    Because most "native" nowadays is web in a "native" (read, Android chrome or iOS shitfari) WebView.
Add Comment