I am building a backtesting platform that allows people to select strike prices relative to the ATM price. Currently I am using the price of NIFTY to decide the ATM price. But some of my beta users have suggested that it would be better to use the Future price to decide the atm price.
So I want to know what is the standard Say for deciding the ATM price. Spot or monthly future? Or by using a synthetic weekly future?
I’m still trying to wrap my head around why independent app developers invest so much time into building backtesting features when there are already great, free tools like Sensibull that provide the same features on computing resources that smaller developers can’t compete with.
I truly value these independent developers and love supporting them through subscriptions because they often bring fresh, unique ideas to the mix. But it can be a bit disappointing at times.
I can’t help but wish for innovative and exclusive features, yet it seems like many end up spending years just reworking back-testing tools and fixing bugs instead.
This isn’t just one app—it seems to be a trend among many independent developers with great potential, wasting their valuable energy on what’s already available for free in top-tier apps.
Why aren’t they channeling their energy into fresh, innovative, unique ideas?
Am I missing something here, or are they overlooking this crucial point?
@RupeeRiser This is from @Sensibull page on freshdesk. I don’t know if it is official or not and if their plans have changed.
Sorry, I got a bit confused thinking those strategy-building diagrams and interfaces for creating complex options strategies were actually back-testing modules.
The main point of the original message was that a most of retail traders are option buyers, while independent app developers are putting most of their effort into creating features for executing complex options strategies that only appeal to a small part of the retail market.
No problem.
Backtesting is useful for systematic traders, whether they do buying or selling. I was suprised by you mentioning sensibull. A good backtesting platform will discourage you from taking the trade 90% of the time. This is why a platform like sensibull can never have a backtesting feature because it will mean less revenue for the broker, who is paying money to sensibull for generating trades.
You may be right in your original argument that this is probably not the most popular problem to solve. And there are already 2-3 platforms doing this. The thing is, developers don’t build stuff just to make money. 90% of the time, we build to learn, test or just amuse ourselves. When you have an burning idea in your head, you can’t stop until you have actully built it (and see if fail). It all works out as long as the rest 10% generates enough money to pay the bills.
