Modularize View Controllers about mobile HOT 3 OPEN

Judging by our conversations with Facebook, it doesn't sound like one of the big selling features of ReactNative is to share code between Android and iOS, as was our hope.

That wasn’t my take-away, mine was that code sharing was a nice side-effect of their choice to use ReactNative, not necessarily the reason they chose to use it.

from mobile.

I also didn't get dissuaded from taking React Native more seriously, quite the opposite. Beating deadlines, developer productivity and separation of app code vs foundational are really interesting aspects of a tech that I've yet to see other paradigms take. Being able port work to Android in the future is great, it's just not there yet.

I don't want to be forced into using RAC for my VCs. I think it's a nice abstraction but I won't build things in it. Just as right now we don't have rules around its usage in Eigen, I would imagine the same here. A View Controller can have its public API and so long as we have established patterns around User Auth, Routing, Networking and Global State it shouldn't matter if it's RAC, React Native or Stacks.

Agree with thing like model categories. MVVM sounds like an internal PodVC choice too, just like NetworkModels.

I occasionally write tests in Energy about ViewControllers inits not creating a view - think this is a good call, could get something like that in #31 (comment)

from mobile.

I don't think I accurately communicated what I meant about ReactNative; I'm not dissuaded at all from using it, just that my impression was that sharing code between Android/iOS is not its main selling point. As Orta said, beating deadlines and all that is 👍

I definitely don't want to force the VCs to use RAC – but I would push for a network layer written in signals. One that is also exposed as regular callbacks. The VC shouldn't care or know that it's RAC, but exposing the RAC signals would be helpful in many cases.

from mobile.