Native all the way, until you need text (justsitandgrin.im)

Article summary

The author, a native macOS and iOS developer, attempted to implement a simple chat with Markdown support in a pure Swift/SwiftUI app, but encountered significant difficulties and limitations. They eventually turned to Electron, which provided a more straightforward solution. The author argues that while native development is often preferred, it can be limiting when it comes to certain tasks, such as rich text rendering. This experience led the author to question the advantages of native development for certain types of applications.

Main themes

• Native development limitations
• Rich text rendering
• Electron vs native development
• Cross-platform development
• Performance and optimization
• UI/UX challenges

What commenters say

• Electron is a viable alternative to native development for certain types of applications, despite its drawbacks.
• Native development frameworks, such as SwiftUI, can be limiting when it comes to complex UI and text rendering tasks.
• The importance of performance and optimization is often at odds with the desire for a native development experience.
• Some developers argue that the benefits of native development, such as better performance and integration, are not always worth the added complexity and limitations.
• Others counter that native development is still the best approach for many applications, and that the challenges can be overcome with sufficient expertise and resources.
• The use of web technologies, such as HTML and JavaScript, can be a good solution for certain types of applications, such as those requiring rich text rendering.
• The choice between native and cross-platform development ultimately depends on the specific needs and goals of the project.
• Some developers feel that the native development community has been slow to address certain challenges, such as rich text rendering, and that cross-platform solutions have filled the gap.