@Arockiya_Raja
can you please add a new category for Feature Requests, this way user can request new features and community can vote/like/heart the features. based on feasibility and timeline Zerodha can evaluate inclusion of these features. (VSCode takes similar approach for new user requested features using Github issues)
6 Likes
@Arockiya_Raja, @nithin any thought on this approach?
Thanks for the suggestion. A public voting board can indicate general interest, but the vote count may not always reflect the actual need or sustained usage. Some features may receive wider support based on their immediate appeal, while the complete context and varying user requirements may not be captured through voting alone. We therefore collect feedback across multiple channels and assess each request based on its use case, expected usage, user impact, feasibility, and overall product priorities.
Fair point, but the goal is not to let votes decide the roadmap. The goal is to create a centralized place for feature requests, reduce duplicate discussions, and allow users to signal interest in existing ideas. Voting can be treated as just one of many inputs alongside feasibility, usage data, and product priorities.
This was my selfish way to get a focused way to view what everyone is thinking about. I still will keep requesting them even in absence of a dedicated category 
Some of them eventually will find home.
2 Likes
many good things can come from this , and it will indeed improve community feedback / user participation.
there are a few drawbacks though -
- some users are not wise enough to request for the right things. For example,
-
they may ask for a section to show “hot trending” stocks , that have given amazing returns in the recent past, or a scanner for micro cap stocks. Now this may cause unknowing users to invest in a stock that has already rallied too much and is near all time high , or come across some penny stock that has no intrinsic value.
-
Or users may ask for a convenient “instant buy” button that immediately uses all available funds to buy the stock at market price. This can cause fat-finger freak trades.
So if some user’s suggestions is aggressively upvoted by the community , zerodha may get pressurized to implement it even if they feel the feature would do more harm than good.
- Theft of ideas : if some feature idea or innovation is truly valuable, since it is a public forum , competitor brokerage firms & app developers can steal it. So this would reduce the “edge” zerodha gets by being a first mover and implementing a novelty idea before others. As a result, the incentive would diminish to justify the resources involved in development of the feature.
So, it would be in people’s interests to privately communicate any original idea directly to zerodha team.
Strong disagree on both points.
This is extremely unlikely unless the folks behind Zerodha change.
(simply based on the behaviour so far)
Even assuming there are such ideas (IMHO, there aren’t; execution is what matters.)
The incentive would be to implement it to achieve parity (without regressing on Zerodha’s USP).
PS: As with other comments in this thread, this is also just an opinion.
Also FWIW, a public “backlog” / “roadmap” of features
has been repeated discussed and concluded as not worth the effort, multiple times on this forum already.
Not sure if any of the underlying conditions have changed which may result in a different conclusion now.
1 Like
as if the supposed competitors are lagging behind zerodha in terms of features right ? ideas are dime a dozen, execution is what matters thinking in adversarial scenarios is a sure shot way to become a laggard in this space, zerodha’s edge is in the community of serious traders who’ve stuck by it for a long time,
traders have been requesting a drag-n-drop sl and tp on chart for a long time now which zerodha can easily implement btw by visualizing its GTT’s OCO order on the chart and since placing regular orders give you a percentage tp and sl in GTT thats doable for them at no extra cost but for some reason(s) they aren’t,
so a community vote/like would definitely signal zerodha dev team to focus on the intent of serious traders
And what is zerodha’s USP ?
I like to think of their USP as avoiding this common pitfall for most retail investors/traders.
Zerodha’s stated USP is “trust”. (refer any annual-report/announcement/… in the past decade)
Zerodha’s revealed USP is “sustainability”. (refer Rainmatter)
Not increased customer-base. Not feature-set. Not trade volumes.
These are recurring themes
that one can find in discussions and announcements on this topic over the years,
a somewhat recent one being -
By who? A better word would be not entertained by Zerodha - in which case, persistence from user base might still work. Characterization of the result of previous discussion as a done deal is a bit misleading.
Sure.
The requester giving up in the discussion-thread
is also an implicit form of conclusion on their part
that it is not worth the effort for them.
(Note: personal opinion) User persistence is already part of the equation
(previous discussions were not the first),
and previous responses have made it clear that
user preference is not a signficant/deciding factor.
(especially revealed user-preferences being used to override stated user preferences)
So am not expecting conclusion/outcome to change
without any other relevant factors changing.
Well, since this is a new thread, the previous discussion is done, right? 
Most folks on this forum who post new threads without linking quoting previous releavnt threads are likely to have NOT read the previous discussions. Having started a “new” topic-thread with the same old mis-assumptions about Zerodha, will end-up making an unconvincing argument to justify their request. 
A new discussion that is identical to the previous discussion without any new factors is likely to end-up with the same outcome. When i see a well-intentioned and well made post, i choose to chime-in with the hope that they can catch-up with the “story so far” and make a better argument, instead of just one more instance of the same old argument that has failed to achieve desired outcome in the past.
@ketub still interested?
Based on the previous comments above,
managed to find any previous topic-threads on this topic yet?
(“backlog” “roadmap”)
You painted a hopeless picture. But a hammer hitting a strong rock will break it if done many times over and over - even with the same exact type of strike each time with absolutely no difference. Brute force persistence with no wisdom still works.
2 Likes
@cvs, I did try looking for a feature-request category/tag before posting, but my search was limited to that specific term. After your replies, I broadened the search to related topics such as roadmap/backlog discussions and went through some of the previous threads.
I understand that similar requests have been discussed before and that the outcome hasn’t changed. My suggestion is less about influencing the roadmap and more about improving discoverability.
I still believe a dedicated feature-request tag/category would help consolidate discussions, reduce duplicate requests, and make it easier for users to find existing requests before creating new topics. Whether a request is eventually accepted or not is, of course, a separate matter.
2 Likes
Not really. That’s your interpretation 
However, continuing with that interpretation, false-hope is worse than no-hope, right?
One of the problems with using analogies is
now the added aspect of discussing whether an analogy accurately reflects the actual point being discussed. 
1 + 4 = 5 no matter what how many times one does it.
…until one introduces additional factors.
For example, Instead of base10 do it in base5 and now 1 + 4 = 10.
Right. Sounds good.
However, this is more about improving the experience on Tradingqna.com.
A key aspect to keep in mind would be to ensure that the category-name, description, pinned-message of such a category, all of them make it very clear that Zerodha is NOT looking for feature requests. i.e the category is simply to help avoid duplicate requests, and noise on this forum.
Also, I wonder how well such a category would be adopted ?
Hopefully, the fact that this topic-thread
- was not created in the existing Site Feedback category.
- and none of us have bothered to move it either
is NOT an indication of how well such a “Feature-Request” category will be used in future. 
Need to start somewhere i suppose.
Maybe today is it?
All other things being the same, do you believe the chances of Zerodha team changing their mind and introducing a roadmap is literally zero - with only user persistence? Do you think those chances are equal to 4+1 being anything other than 5(same base and all other things being equal)? I just believe user persistence is x in 4+x+1=5(Of course you could add a bunch of other variables). Variable “x” may be close to or at 0 now, but with enough effort in pushing it closer to 1, it may change the validity of the equation. Only those who persevere till end have the luxury of knowing, whether the hope will turn out to be false hope or true. But if you never try, it’ll always be false.
Yes, i genuinely do believe that.
And i wish for that too.
I also believe that the decision will eventually change
Because other factors change,
not due to persistence of a vocal minority (of all the users) who interact on this forum.
(FWIW, i think the most likely factor to trigger such a change in the decision/outcome
would be one of the several ways the definition of “Zerodha team” can change in future.)
Of course.
A feature request category is more suited for a broker that actively invites such participation and systematically takes up such for development. I don’t think Z functions like that. Infact most brokers don’t.
In my experience only Dhan does it, it’s part of their culture, and maybe they even overdo it… Look at their Feature Request category. It’s so active, with so many requests taken up for development.
1 Like