Native mobile development. You bitch.

You dont know how good you have it until you spent 3 hours on making a button work in flutter or react

@zemaitis dir don't know how good your have it until your try to save streaming data using dagger2/rxJava/retrofit during an orientation change.

But yes.

Using react native now. Still a bitch.

mobile development is a bitch.

mobile developer here 🙋

Coming from web, it is utter bitch.

@polaroidkidd I thought I was alone with that opinion. But the lib combos currently employed in mobile dev reminds me of javascript npm and framework chaos. I specifally made the jump from web to android to avoid this... Now its turning into the same shit....

@noyb and here I am going the other way hoping thatvi went have to deal with configuration changes, context loss and complex wiring when it comes to support libs, and honestly, so far it's been pretty relaxed compared to android.

I'm just glad I don't have to second guess my choice of architecture at every turn (MVP Vs MVVM and all of the complications that fine with it)

@polaroidkidd Haha i can understand where you ´r coming from. I think the complexity arises from the stateless nature of the web and the best effort principle of TCP-IP whereas in android it is its single thread architecture and the huge variety of devices and stuff. We just build stuff on top of it and created the illusion of 24/7 availability...

best bitch out there

I use nativescript

So I got that going for me which is nice

@polaroidkidd Use ViewModel and LiveData which are lifecycle aware and problem solved. Im telling you again you dont know how good you have it.

@zemaitis the new android arch components? Are they decent?

Cheers for the tip, I'll give them a whirl!

@polaroidkidd yeah man they save lives

Well I finally launched the app. Took us 8 working days. And then.. we had to deal with Play Store. 🤦‍♂️