Почему вам не нужен Kotlin Multiplatform

Summary

The speaker, Kirill Rozov, discusses the practical challenges of using Kotlin Multiplatform for mobile app development across Android and iOS. He highlights the technology's promise of code reusability but points out the current limitations and complexities, especially when integrating with Swift. Rozov emphasizes the need to wait for more mature solutions and better tooling before fully embracing Kotlin Multiplatform in large-scale projects. He advises caution, recommending that businesses prioritize reliability and proven technologies over the potential long-term benefits that are not yet fully realized.

Takeaways

• 🔥 Kotlin Multiplatform is an emerging technology that promises code reusability across platforms but comes with its own set of challenges in practice.
• 👨‍💻 The speaker, Kirill Rozov, shares his experience with Kotlin Multiplatform, highlighting that while it's theoretically appealing, practical implementation can be complex, especially for those without prior experience.
• 🚧 Kotlin Multiplatform's support for sharing UI and other features is still in development, with the speaker noting that as of May 2024, JetBrains has just announced work on a solution for better interoperability with Swift.
• 🛠️ The script mentions the need for workarounds and third-party plugins to improve compatibility between Kotlin and Swift, indicating that the technology is not yet seamless.
• 📱 For projects already using native code with Swift, integrating Kotlin Multiplatform can be painful, requiring significant effort and potentially causing delays.
• 💡 The speaker suggests that for large-scale projects, sticking with native development might be more practical than attempting to migrate to Kotlin Multiplatform.
• 🛑 The script warns against the assumption that Kotlin Multiplatform will necessarily save time or money in the short term, as the learning curve and current limitations could lead to increased development time.
• 💼 The business implications of adopting Kotlin Multiplatform are significant, with the need for high-spec hardware for development and the potential for increased costs due to the need for skilled senior developers.
• 🔍 The speaker emphasizes the importance of good architecture and modular design when using Kotlin Multiplatform, which can be challenging for developers without a strong background in these areas.
• 📈 Despite the potential long-term benefits, the current state of Kotlin Multiplatform may not offer immediate advantages, and its adoption should be carefully considered based on project needs and resource availability.
• 🌐 The script concludes by advising caution and thorough evaluation before adopting Kotlin Multiplatform, especially for businesses that require reliability and guaranteed outcomes.

Q & A

What is the speaker's opinion on Kotlin Multiplatform in the current state?

The speaker believes that Kotlin Multiplatform is not yet ready for everyone and might require waiting for another year or more for it to mature with out-of-the-box solutions.

Why does the speaker suggest that Kotlin Multiplatform might not be suitable for all projects right now?

The speaker suggests that Kotlin Multiplatform has many interesting challenges when encountered in practice, especially without experience, and can lead to a lot of pain points, making it not suitable for all projects at this stage.

What does the speaker mention about sharing code between Android and iOS using Kotlin Multiplatform?

The speaker mentions that sharing code between Android and iOS is not straightforward due to the lack of out-of-the-box solutions and the complexity involved in making the shared code work seamlessly across platforms.

What are some of the challenges the speaker faced when trying to integrate Kotlin Multiplatform into a project with Swift?

The speaker faced challenges such as the need for third-party plugins to improve compatibility between Kotlin and Swift, losing certain features like value classes when the code is called from Swift, and the lack of guarantees in the code when used in iOS.

What does the speaker recommend for developers who are considering migrating from native projects to multiplatform projects?

The speaker recommends looking for alternative technologies and libraries, rewriting classes to be multiplatform-compatible, and considering the implications of serialization, suggesting that the process can be complex and time-consuming.

Why does the speaker suggest that Kotlin Multiplatform might not be cost-effective for businesses at the moment?

The speaker suggests that the need for high-spec computers to develop and debug across platforms, the time spent resolving compatibility issues, and the need for experienced senior developers make Kotlin Multiplatform potentially more expensive for businesses at this stage.

What is the speaker's view on the current state of UI development with Kotlin Multiplatform?

The speaker believes that Kotlin Multiplatform's UI development is in a beta stage and lacks out-of-the-box native UI components, requiring developers to build their own UI kits or find open-source alternatives.

What advice does the speaker give to businesses considering adopting Kotlin Multiplatform for new projects?

The speaker advises businesses to be cautious and clearly evaluate the risks and benefits, considering the current不成熟 state of Kotlin Multiplatform and the potential for delays and increased costs.

What does the speaker suggest about the job market for Kotlin Multiplatform developers?

The speaker suggests that the job market for Kotlin Multiplatform developers is not as large as for native Android or iOS developers, indicating that the demand for this skill set is currently limited.

What is the speaker's overall recommendation for developers with 2-3 years of experience considering Kotlin Multiplatform?

The speaker recommends that developers with limited experience should be cautious about jumping into Kotlin Multiplatform due to the complexity and potential challenges, suggesting that it might be better to stick with native development for now.

What does the speaker suggest about the future of Kotlin Multiplatform?

The speaker suggests that Kotlin Multiplatform is an evolving technology and advises developers to keep an eye on its development, but not to rush into adopting it without a clear understanding of the risks involved.