4 ms·
Well of course Vs is an option. You just use View models and cover them with unit tests. Then you sacrifice one of your developers on the altar of Jobs and forc
by jamra 11y ago
Well of course Vs is an option. You just use View models and cover them with unit tests. Then you sacrifice one of your developers on the altar of Jobs and force him to implement your iOS code.
- viperscape 11y agoOur mac loving c# developers use parallels, perhaps that's an option for you
- V-2 11y ago:) The idea is that everybody works on Android and iOS alike, no specialization on the team. And the UI itself (Xamarin.Forms) takes the bulk of our development time, we're running into so many quirks, and the cross-platform abstraction is very leaky unfortunately. So your recommendation may be good, but I don't think it would pan out in our particular scenario. Especially since the team consists of people with no prior exposure to Xamarin (C#/MVVM devs + me, an Android dev with some half-forgotten familiarity with C#), so we've been learning on the job a lot