Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enact 2.0 Roadmap #1504

webOS101 opened this Issue Mar 16, 2018 · 5 comments


None yet
4 participants
Copy link

webOS101 commented Mar 16, 2018

The focus of the 2.0 release is a generalization of the components built within 1.x to enable us to create new experiences for other platforms beyond the 10 foot experience. We also want to improve the overall developer experience of using Enact


  • Expanding @enact/ui to provide generalized, unstyled base components on which we can build themed versions for difference experiences
  • Expand and improve our developer tooling provided by @enact/cli
  • Add touch and gesture support
  • Add multi-platform support beyond webOS
  • Add components to support webOS digital signage products
  • Add support for voice control of components


  • Improve the integration of @enact/i18n with @enact/moonstone by supporting asynchronous retrieval of internationalization resources
  • Improve component-level render and update performance across the framework
  • Revisit our unit test architecture to provide better coverage and faster run times

This comment has been minimized.

Copy link

elijahdorman commented Mar 31, 2018

Is there any plan to add support for the Pointer API? It now has native support on every browser except Safari and has a good polyfill for that case. Seems like a more forward-looking solution than "touch support".


CanIUse Page


This comment has been minimized.

Copy link

ryanjduffy commented Apr 2, 2018

@elijahdorman Thanks for the feedback! I agree that pointer events support needs to be part of our roadmap. We're somewhat constrained right now because our current generation of webOS platform does not yet support pointer events. That said, it would be worth investigating how a polyfill would work with our existing work-in-progress support. Appreciate the idea!


This comment has been minimized.

Copy link

nghiatv commented Jun 8, 2018

Does Enact 2 support full webOS 4 SDK?


This comment has been minimized.

Copy link
Contributor Author

webOS101 commented Jul 9, 2018

@nghiatv You can see which API's are exposed natively in the webos module here. Any other API's can be access through LS2Request.


This comment has been minimized.

Copy link

ryanjduffy commented Aug 3, 2018

I've updated the roadmap to reflect the work included in the 2.0.0 release of Enact. One feature and two quality improvements were not built for 2.0.0 but are still on our near term roadmap so remain here.

We're in the midst of 2.x planning now so we're open to feedback from the community on what they'd like to see added and improved in Enact. Once we have some initial plans on features and which minor release they will land, we'll update this post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.