BEFORE YOU GO ANY FURTHER
New conversations should be started on GitHub Issues instead of in this forum.
Welcome to the Xamarin.Forms Evolution discussion board. You can help shape the future of Xamarin.Forms by discussing proposals, roadmap items, and ideas for Xamarin.Forms by participating in this forum.
This subforum is specifically for discussion about specific ideas for the future of Xamarin.Forms. Discussions or questions not related to a specific proposal should use the Xamarin.Forms subforum. Comments about specific releases should be contained to the corresponding Xamarin.Forms release thread to help our team answer your questions and investigate your issues.
As such, the following policies will be enforced in addition to the Xamarin Forums Rules & Guidelines.
In order to ensure all proposals have an appropriate of detail for discussion, we ask that you follow the following format:
[NAME OF YOUR PROPOSAL HERE]
##Summary Please provide a brief summary of your proposal. Two to three sentences is best here. ##API Changes Include a list of all API changes, additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some "example" code of usage of your new API. e.g. In order to facilitate the new Shiny Button api, a bool is added to the Button class. This is done as a bool because it is simpler to data bind and other reasons... var button = new Button (); button.MakeShiny = true; // new API The MakeShiny API works even if the button is already visible. ##Intended Use Case Provide a detailed example of where your proposal would be used and for what purpose.
The following topics should generally not be proposed for discussion as they are non-starters:
Open proposals are still under discussion. Please leave your concrete, constructive feedback on this proposal. +1s and other clutter posts which do not add to the discussion will be removed.
Accepted proposals are proposals that both the community and core Xamarin.Forms agree should be a part of Xamarin.Forms. These proposals are ready for implementation, but do not yet have a developer actively working on them. These proposals are available for anyone to work on, both community and the core Xamarin.Forms team.
If you wish to start working on an accepted proposal, please reply to the thread so we can mark you as the implementor and change the title to In Progress. This helps to avoid multiple people working on the same thing. If you decide to work on this proposal publicly, feel free to post a link to the branch as well for folks to follow along.
Once a developer has begun work on a proposal, either from the core Xamarin.Forms team or a community member, the proposal is marked as in progress with the implementors name and (possibly) a link to a development branch to follow along with progress.
Rejected proposals will not be implemented or merged into Xamarin.Forms. Once a proposal is rejected, the thread will be closed and the conversation is considered completed, pending considerable new information or changes..