As a front-end developer that started our as a designer, building highly polished and accessible UI components that also has a great developer experience is really imporant to me. Ember has been a powerful tool to accomplish this and Octane has made huge improvements to the overall quality of the code.
But, this wouldn't be a Ember 2019 roadmap blog post if there weren't a desire for improvement.
When I design a new component I mock up the visual and UX design to make sure it will look good, function well, and be fully accessible. Part of that design process is figuring out the UX for the developer. I like to start with the desired invocation API and work my way backwards to the implementation. However, when you start building really complex interactive components you quickly run into limitations with Ember.
For example, if you were to try to re-implement the native
select in Ember with custom
<Option> components you would quickly run into walls. Take this hypoth