Back in September 2014 when first introducing Win2D, we said:
“By no means is the API in its current state a complete representation of Direct2D in Windows Runtime. We believe that releasing the API early, even if it does not have all the Direct2D features, is useful. As a developer and potential user of the API you get the chance to influence the API design early and ultimately help build the best C#/C++ Windows Runtime 2D immediate mode rendering API.”
How things have changed since then! Win2D has grown into a rich and mature 2D graphics API. We have recently caught up with the feature set of the underlying Windows graphics platform that Win2D is built on top of, supporting all the functionality of Direct2D and DirectImage plus a good chunk of DirectWrite.
We are now going to take some time to stabilize what we have built. Once we are happy that everything is working well and our newer API designs are solid, we will remove the “experimental” tags, which currently warn that everything added since Win2D version 1.0.0 may be subject to change.
We still have a few loose ends to finish up, and will continue to fix bugs, support customers, and expose new features in Win2D when future versions of Windows add capabilities to the platform beneath us, but we have now successfully completed the typing-code-like-crazy-trying-to-catch-up-with-the-last-8-years-worth-of-Direct2D-features phase of the project. Therefore, we will reduce the frequency of updates from our current biweekly cadence. At a guess we’ll probably end up shipping more like once a month, but this is hard to predict as NuGet updates will now happen on-demand whenever we have worthy payload, rather than on a fixed schedule.
One of the most enjoyable parts of this project for me personally is the opportunity to engage 1-1 with developers, helping to understand your requirements and solve your problems. That isn’t changing, so please keep the questions, bug reports and feature requests coming! If you notice any flawed designs, now is the perfect time to point them out, while these APIs are still tagged as experimental…