Hey everyone,
I have been working with Ember for a little while & I want to know about how people approach building more complex UIs when projects start growing. I such as Ember’s conventions & the structure it provides out of the box but sometimes when I am dealing with deeply nested components or state that needs to be shared across different parts of the app; I start wondering if I am overcomplicating my setup.
Do you lean heavily on services; or do you prefer data-down actions-up patterns to keep things manageable? I have seen some folks experiment with state machines or even custom patterns to handle tricky flows; I want to hear about what is worked well for you in larger projects and what pitfalls to avoid.
I have been comparing frameworks lately just out of curiosity. While exploring a reactjs course online, I noticed some different approaches to component communication and state handling, which made me wonder how Ember devs tackle similar challenges.
Thank you….
4 posts - 4 participants