stretch VS react-native

The most common is flexbox (an attempt to a cross-platform engine at https://github.com/vislyhq/stretch).

There's a few critical subtasks here: - determine the data flow model we'd like to use for our UI. We'd like to integrate tightly into the ECS, but need to figure out how to reduce the boilerplate and improve reliability around working with hierarchies. - swap our layout library. Our current dependency stretch implements the flexbox algorithm, but is unmaintained and has critical bugs :( The three main options here are to fork flex, move to the new morphorm crate, or write a layout library from scratch - consider rearchitecting our UI to be more flexible and compositional: splitting the massive Style component into several parts and moving to a "UI is a collection of behaviors" paradigm - build out more widgets! - more docs and examples!

That would probably entail integration with bevy, or some other game engine to get the UI drawn. Our TUI crate uses https://github.com/vislyhq/stretch/ to lay out the elements, so I imagine you could use that but just draw with WGPU.

Are there any plans to make yoga fully conformant to the web implementation of flexbox? For example, migrating to use stretch instead?

https://github.com/vislyhq/stretch exists, I don’t know how well it would do at all this.

There was always a tiny sparkle in me telling me that I want to develop mobile apps but I never pursued it. It always felt a bit complicated for me to learn development processes in a completely different industry. I did try developing mobile apps using React Native but it never felt right for me. Also, I already tried to write some Kotlin code and so far I like it, but the whole Android ecosystem is still pretty new to me and I feel there will be a lot to learn. Nevertheless, I will try to learn it in parallel with Elixir but Elixir will be my primary goal, and Kotlin / Android will go along depending on how much time I will have.

This is a modified version of the file from the react native cli template

Recently, there has been a notable shift in mobile application development practices. Rather than creating separate applications for each native platform, many developers are opting for hybrid mobile frameworks like React Native.

React Native [ https://reactnative.dev/ ]

Versatility: JavaScript is not limited to web browsers. It's used in a variety of environments, including mobile app development (using frameworks like React Native), game development (using libraries like Phaser), and even serverless computing (using platforms like AWS Lambda).

In the competitive landscape of mobile app development, user experience (UX) has emerged as a critical differentiator. React Native, with its robust framework and versatile capabilities, offers developers a powerful toolkit to create seamless and engaging user experiences. This blog post delves into the design principles and best practices in React Native app development, uncovering how developers can elevate user experience to new heights and drive success in the digital realm.

You can find the React Native documentation here and Flutter Documentation here.

Additionally, React Native, an extension of React.js, enables developers to create hybrid mobile applications with ease.

You don’t know what to do with your time while applying the 5th rule? Start small, tiny steps. If you can’t read much, start small, 15 minutes a day reading a technical article or even a book like Effective Java, by Joshua Bloch. You don’t like to read? Create small projects by using a framework you want to learn. Check for example: React framework.