Keeping a single tech stack allows your company to focus on a tech stack that can be hired and maintained.įeature teams: a common approach in mobile is to separate teams by platform (iOS, Android). Senior engineers are difficult to find, and it is harder to convince them to change between companies unless a decent offer is provided. One single tech stack: hiring in tech is generally an arduous task. We do not longer need to develop several of them to be deployed on multiple platforms, so certain tasks tend to get easier, such as bug maintenance. Quality increase: a single codebase is easier to maintain and audit. There are however multiple considerations as to why the cost is not the only aspect that can benefit from maintaining a single codebase: Some of the frameworks that have paved the way for KMP in the past With more or less success, those technologies aimed to provide a unified framework to develop multiple codebases, mostly focusing on the aspect of pricing (create code once, deploy multiple times). Since the advent of the mobile platforms we enjoy today, there has always been a certain market interest to push multiplatform technologies, such as Cordova, Xamarin, and others. JetBrains compiled a website listing some of the companies that are currently using KMP. Kotlin Multiplatform (or KMP, KMM Mobile, etc) has been widely used for a number of years in applications that are currently in production.
0 kommentar(er)
