matej
11/18/2019, 1:44 PMSam
11/18/2019, 2:45 PMkpgalligan
11/18/2019, 3:27 PMAndy Gibel
11/18/2019, 3:58 PMkpgalligan
11/18/2019, 3:58 PMAndy Gibel
11/18/2019, 4:00 PMswitch
statement for instancematej
11/18/2019, 4:49 PMAndy Gibel
11/18/2019, 4:50 PMmatej
11/18/2019, 4:51 PMI think the issue would be if you’d change libraries if you moved away from KMP. Like maybe you’d switch off ktor?I'm imagining a scenario like the high profile exit of Airbnb from React Native, where after a while they figured it's not for them. After that point, they're stuck with RN in some sense forever until they do a full app rewrite. It would be the same for Xamarin. It's an all or nothing situation, whereas in the case or KMP you could draw a line and tell the iOS developers, for example, from today we're writing all new code natively for each platform. You keep your Xcode project, for now you continue consuming our KMP .framework, which we'll replace piecewise as part of our regular maintenance and refactoring effort, but with very little up-front effort, we can basically consider ourselves a regular native mobile dev shop going forward. Sure, we need to gradually replace parts of the API of our shared business logic KMP library with platform-native implementations if that's what we want, but we don't have to do it all at once. That's a pretty big selling point to bring up to stakeholders in my view.
kpgalligan
11/18/2019, 6:12 PMAndy Gibel
11/18/2019, 9:11 PMkpgalligan
11/19/2019, 2:11 AMDmitri Sh
11/19/2019, 2:46 AMAndy Gibel
11/19/2019, 2:49 AMkpgalligan
11/19/2019, 2:54 AMDmitri Sh
11/19/2019, 5:20 AMmatej
11/19/2019, 8:01 AMmkojadinovic
11/19/2019, 8:05 AM