Is UI support on your roadmap?

[buaaji]

Thank you creating this fantastic Workflow open source project!

Definitely, UI is very important for end users, I understand that currently UI is not a part of the project, but will it be on your roadmap? If yes, do you have any idea about "when"?

In addition, when this project is ready to shift from "experimental" phase to "product" phase?

[dmetzgar]

If by "product" you mean when is CoreWF going to be used in a product, it already is. If you're asking when will we publish a package with a version number that doesn't include the date and build number, I don't have an answer for that yet.

Most people I talk to that are interested in using CoreWF want the rehostable workflow designer. It didn't make sense in early .NET Core but now with Avalonia and MAUI it's technically possible. It would be a lot of effort to build and maintain. I don't know if there's enough demand out there to be worth the effort.

[buaaji]

Thanks @dmetzgar

If there is no UI support, a consumer wouldn't be able to create a new workflow, s/he wouldn't be able to visualize any existing workflow, which IMO is a big limitation. Being able to run a pre-defined workflow is quite useful, but not everyone knows how to manually edit a xaml file.

BTW, when you mentioned "rehostable workflow designer", did you mean a designer which is hostable on multi-platforms like desktop, web and mobile?