3 ms·
Does anyone know how far down Kotlin Multiplatform is likely to scale, because most engineering org charts are not the shape and quality of Netflix's engineerin
by brudgers 6y ago
Does anyone know how far down Kotlin Multiplatform is likely to scale, because most engineering org charts are not the shape and quality of Netflix's engineering org chart?
At what size and level of expertise/experience does it make sense to consider it?
What are the prerequisite knowledge/skills/abilities that a two pizza team needs to keep the learning curve practical?
- chrisweekly 6y ago+1 I love this question; it doesn't get asked enough. (Also, I have interest in hearing others' answers for Kotlin Multiplatform in particular.)
- rapsey 6y agoMainly depends on the depth of the apps. If they are just UI and API calls then no. If there is a lot of processing snd state management going on then the more there is the quicker it makes sense
- maxsilver 6y ago> What are the prerequisite knowledge/skills/abilities that a two pizza team needs to keep the learning curve practical? Just my personal experience, but if you have a good Android/Java "two-pizza team", you probably already have the makings of a good Kotlin team, given the appropriate time for folks to pick it up.
- billjings 6y agoI think it's more a matter of expertise/experience than size. The different platform teams have to have gelled enough to agree on the core architectural abstractions, which is a level of maturity that goes a step beyond necessity. So the platform teams need to have shared prior knowledge of how to build with the same architectural patterns, and they need to be sold on the possibility and merits of using those same patterns and coordinating on their plans of implementation.
- brudgers 6y agoI mention size because it tends to correlate with institutional experience and availability of relevant expertise in the org chart.
- snappytrap 6y agoExactly - the team from the article went with a shared architecture from the start. They set themselves up to make this kind of thing possible.
- jillesvangurp 6y agoIf you know Kotlin already, starting a multiplatform project is pretty easy; it's mostly just Kotlin. I've done a few small things with it. Mostly the sweet spot is doing those things for which multiplatform libraries already exist so you don't have to reinvent wheels. For a two pizza team, I'd recommend not overthinking it and to just give it a try if it makes sense for you or not if it doesn't. Hard to tell; it all depends on your requirements and how good your people are.