Roadmap and Philosophy

XAML Behaviors Roadmap

We will be releasing updates to the XAML Behaviors NuGet package on a quarterly release. Given the nature of open source, we want to be as transparent as possible about the plans and direction we want Behaviors to go in.

Philosophy and Project Goals

Behaviors will evolve as people contribute to the project. Laying down the philosophy and goals for Behaviors will help guide the types of contributions we receive.

Our broad goals for the project:

Targeting common interactive scenarios

Behaviors should be a toolkit that targets a wide audience of developers, and empowers them to be more productive. The Behaviors taken into the project should address common and core user scenarios that many people will find value in. To ensure that developers get the most out of what is published, Behaviors that address uncommon and limited scenarios will not be accepted (we encourage shipping these are other NuGet packages, that express a dependency on the core Behaviors NuGet package).

Writing Good documentation and samples

The Behaviors GitHub page, documentation, and sample apps should be good sources to teach new developers about Behaviors, and how to use them. Whether a user is new to building apps and using Behaviors, or experienced and looking to create their own custom Behaviors, the proper resources to do whatever a developer needs and wants to do should be provided.

Concentrating on the SDK and not on the tooling

Rather than concentrating on new tooling and the authoring experience behind Behaviors, building out the platform should be the goal. Behaviors are a toolkit for developers to leverage in their apps, instead of adding new value editors to Blend or Visual Studio.

Co-evolving C++ Behaviors evolve instep

Behaviors support both native and managed projects. While expecting more development and contributions on the C# side, there should still be adequate C++ support. If a Behavior does not utilize reflection, considerations should be made to add a C++ version to make sure no language gets left behind.

Schedule

Milestone	Release Week
RTM	30 Nov 2015
Update 1	22 Feb 2016
Update 2	23 May 2016
Update 3	Late August 2016

Feature Roadmap

Guided by our broad goals, we will evaluate the contributions made to the project. Additionally, going forward, based on the feedback we receive, will determine the direction of Behaviors. If there is demand to expand in a certain way, we want to move towards that.

Some areas we would like to consider:

• Cross XAML support (WPF, Xamarin)
• Workflow specific toolkits (i.e. Animation, Transitions and Effects, etc.)
• Visual Basic support