Our approach to product feedback & feature requests

Here at SciChart, we take product feedback extremely seriously.

We have built our company from the ground up by listening to customers, their team members and prospects – by taking their ideas & suggestions on board – to build the best WPF, iOS & Android Charts in the world!

We use your feedback to identify the most important features, ideas, pain points, and opportunities so that you can get more value from our product as efficiently as possible.

How to give us your product feedback

Submitting your feedback couldn’t be simpler! We have just implemented a new Feedback & Feature Request System, which will allow you to submit your requests directly to us.

To use it, click the button in the right sidebar of the website.

Request a Feature

To request a feature, click on the button ‘Submit a Feature Request’. Please give us as much detail as possible including images to show what you need and why.

Vote on Features you want

You can vote on features. If you want something, vote on it, or click the ‘I want this’ button. If you don’t want something, click the ‘I don’t want this now’ button.

Set your Feature Priority

Prioritise your features by using the sliders in the app. The priority will tell us what you need the most.

Leave Comments and Discuss!

Don’t forget to leave comments or discuss feature requests. The more info we have from you, the better!

What Happens to your Product Feedback

Any of our customers, trial users and prospects with a scichart.com account can request a feature, or vote on a feature-request by clicking the link in the right of the website.

New Requests

All new requests are set to ‘Awaiting Feedback’ status so that more people can vote, prioritise and give us information. This allows us to gauge demand, gather use cases and automatically establish impact and value.

Setting Priority

Every month, our development team holds a product feedback meeting. We discuss the highest priorities for our customers, team members and prospects and look at how feature requests align with our own strategy. As the team goes through, they will update the status of each feature request in our system so you can immediately know the outcome.

Creating the Roadmap

If we decide to build a feature or make an improvement, the status will be changed to “Planned” or “Building”. It will be added to our product roadmap which you can view at any time.

Anyone who has submitted or voted on a specific request will be notified when the status so the request if updated. We will always provide an explanation as to the nature of the status update.

Our product feedback portal always has the most up-to-date information about our products and what we are building next.

If you reach out directly to our Support or Customer Success teams, they’ll be able to look up ideas for you, but they won’t have any additional information or provide an estimate for when your request will be reviewed.

How are Votes weighted?

Votes toward feature requests are weighted in two ways.

1. The first, is by the number of votes on a feature request
2. The second, is by the relative voting power of the people requesting.

Number of Votes

If we receive a feature request which has a high number of votes, it will be prioritised higher in our product roadmaps. For example, if 100 of you get together and voted for an insanely cool widget, then that widget we will build.

Voting Power

As a SciChart customer, trial user or prospect you will be given a Voting Power value. This value changes depending on the product(s) that you have purchased with SciChart. Simply put, customers with higher product tiers have a higher voting power.

If we receive a feature request with fewer votes, but each vote had a higher power, then it is likely we will build this item also.

Voting power is calculated as follows:

For example:

• A customer who has 5 licenses of SciChart WPF SDK Professional with 2-years support remaining will have a total voting power = 3+2 = 5 per developer, and 25 if all developers vote on the same features.
• A customer with a single SciChart 2D Professional and < 90 days support remaining has a voting power = 2.
• A customer with two licenses of SciChart iOS/Android 2D Professional and > 90 days support remaining has a voting power = 2+1 = 3 per developer, and 6 if both developers vote on the same features.

Each of your votes for feature requests count, no matter the voting power, but it gives us another angle to view the relative weight or value of requests to our user-base and help us to prioritise the roadmap.

FAQs

How long will it be before the product team reviews my idea?

Items will be reviewed by the product specialist on a weekly basis; we take the top requests and update the status where appropriate. Road-mapping meetings occur monthly. Make sure your ideas are clear and concise so others can vote on it & prioritise. Also be sure to prioritise your own requests too! That way, we will know if a particular request is important to you.

Can I fast-track a feature request?

We will build the feature requests that align with our roadmap and also are the most popular / most valuable requests from our customer-base, but what happens if you want to fast track a request?

There are some instances where you might need a feature asap. In this case – you can consider hiring our team as short-term consultants. We’ve carried out a number of projects for customers where we have built new features specifically for them and they have been a great success!

Why hasn’t my request been reviewed?

If we haven’t reviewed your item yet and it is a high priority for you:

• Make sure it’s at the top of your priority list
• Make sure your request is clear. Why do you need this? What is it stopping you from doing? What is the impact of that? Please add these details in a comment on your idea.

The post Feedback & Feature Requests Policy appeared first on Fast, Native Chart Controls for WPF, iOS, Android and Xamarin.