Questions about UMG ViewModel Roadmap, support and timeline

Development Programming & Scripting UI
, ,
1

Hello,

The UMG ViewModel feature looks great and our team is interested in exploring adding it to our workflows. We recognise it’s in beta though, so I wanted to ask:

  • Where does it sit in your roadmap? We don’t necessarily need a precise ETA but an indication of what to expect would help us know if this feature can fit our project timeline
  • Are there any changes coming or risks regarding this feature that are worth knowing about before we use it in our project? I know being beta should mean backwards compatibility and a stable API, but just checking
  • Are there any resources, example projects or anything helpful on the recommended idiomatic way of setting up and using this feature?

Thanks a lot for the help!

2

Steps to Reproduce
There is no repro, this is just a query

3

Hi,

Answers to your bullet points below:

Where does it sit in your roadmap? We don’t necessarily need a precise ETA but an indication of what to expect would help us know if this feature can fit our project timeline

We don’t have a specific roadmap, but we’re using the Viewmodel plugin heavily in our own internal projects and don’t have any significant feature work left. We have a few smaller feature requests on our radar and are fixing bugs as we discover them, but we’ll likely be able to move it out of beta soon.

Are there any changes coming or risks regarding this feature that are worth knowing about before we use it in our project? I know being beta should mean backwards compatibility and a stable API, but just checking

No breaking changes are planned, so it should be safe/stable enough to use. Feel free to report any issues you run into on EPS and we’ll investigate.

Are there any resources, example projects or anything helpful on the recommended idiomatic way of setting up and using this feature?

I’m not aware of any current sample projects that demonstrate the plugin, though I suspect you’ll start to see it being used in other unrelated sample projects since it’s the easiest way to handle complex widget binding. It’s tough to share best practices since it tends to be very project-dependent, other than a general recommendation to use more small VMs in lieu of a single huge VM when possible to lessen the impact of modifying the VM class to add/remove properties.

4

This is great to hear, thanks a lot for the answer!