Submitting a NativeScript Feature Request

By
Rob Lauer

While managing a free and open source project, the NativeScript team has strived to be as open as possible about the framework's roadmap. Allowing the community to suggest features, comment on them, and vote them up 👍 or down 👎 is a critical element of this process. We combine this direct input with community surveys, one-on-one interviews, and market research to develop a complete roadmap.

Up until now, we admit that we've been a little scattered in terms of exactly how we have received this input from you. While we read your blog post comments, forum posts, support tickets, Github issues, and our ideas portal, we have not been as upfront as to how you should directly provide feedback.

This changes now as we transition to utilizing Github for all feature requests! With the introduction of reactions on issues, Github allows us to not only track issues and feature requests, but to also allow the community at-large to effectively vote issues up or down with a 👍 or 👎 (not to mention provide more context in the comments).

vote up a feature on github


👍👎😄😕❤️🎉 let you tell us what you really think!

We do ask that you use the feature label to tag your feature requests in the NativeScript repo.

Here is a handy link that acts as a mini ideas portal for you.

This does mean that the old ideas portal is being deprecated. But don't worry, we are transferring over all of the most popular items to Github that haven't already been added.

And yes, we will still keep listening to you here on the NativeScript blog, forum posts, and support tickets. It is you, the community, who helps drive the direction of NativeScript, so your input is truly invaluable.


Share this article

Comments


Comments are disabled in preview mode.

Stay connected with NativeScript

NativeScript
NativeScript is licensed under the Apache 2.0 license .
© 2017 Progress Software Corporation. All Rights Reserved.