No internet connection
  1. Home

Comments for https://ctrader.com/products/4335

By system
    2026-05-22 18:52:19.564Z

    Comments for: https://ctrader.com/products/4335

    Add Comment
    • 6 comments
    1. A
      algo_expert
        2026-05-22 18:52:19.622Z

        Hello Firat,
        After resolving the setup issues and configuring the correct broker symbol names together with a valid FRED API key, the indicator started working properly - and the overall concept became much clearer.
        The macro/intermarket logic behind Market State Pro is genuinely impressive. The combination of USD pressure, yield curve analysis, liquidity conditions, volatility, and cross-asset flow mapping creates a very strong institutional-style market context dashboard.
        The HUD is also surprisingly clean considering how much information is processed internally.
        The main challenge from the QA side is onboarding and broker compatibility. Since the indicator depends on exact broker symbol names, many users may struggle during the initial setup phase.
        Adding features such as:
        automatic symbol detection
        broker alias mapping
        setup validation
        clearer onboarding instructions
        would significantly improve usability.
        Overall, this is one of the more interesting macro-context tools currently available on cTrader.

        Reply
        1. Ffirat_aslan
            2026-05-23 11:57:25.885Z

            Hello algo_expert,

            Thank you very much for your detailed feedback.

            I’m very glad to hear that you liked the product and found the macro/intermarket logic useful. Your comments about the HUD design and the institutional-style market context are truly appreciated.

            In the first version, my main focus was to make the core calculation logic, HUD structure, and market context model work in a stable way. Because of that, some parts of the initial setup process still need to be simplified and improved.

            I also considered automatic symbol detection. However, since broker symbol names can vary a lot, I initially preferred manual symbol parameters because they are more stable and controllable. That said, I will continue testing this area. If I can make automatic detection work reliably across different broker environments, I will definitely consider adding automatic symbol detection or broker alias mapping in a future update.

            I also plan to make the onboarding process clearer and simpler, especially around symbol mapping, setup validation, and first-time configuration.

            Regarding the FRED API key, adding a hardcoded API key is not a healthy approach in cTrader, and each API key also has its own usage limits. For that reason, it is better for users to use their own API keys. However, I am also planning to make the product work in a basic mode without requiring an API key, using the available internal/current data. This way, Market State Pro can start working correctly on the first launch, and when a FRED API key is added, it can switch to more advanced macro-data-based calculations.

            Thank you again for testing the product and sharing such constructive feedback. Your suggestions are very useful for the next updates.

            Best regards,
            Firat

            Reply
            1. Aalgo_expert
                2026-05-23 13:51:49.674Z

                Thank you for the detailed response and for explaining the design decisions. Your reasoning about broker symbol differences and FRED API handling makes complete sense from a technical perspective.

                I especially like the idea of introducing a basic mode that works immediately without requiring an API key. From a user experience perspective, I think this could significantly improve the first impression of the product.

                One additional suggestion from testing:

                Even if full automatic symbol detection is difficult across brokers, a lightweight alias system could help. For example, mapping common variations such as:

                US500 ↔ US 500
                NAS100 ↔ US TECH 100
                XAUUSD ↔ GOLD
                XBRUSD ↔ UKOIL

                Another useful addition could be a startup validation panel that checks:

                Missing API key
                Missing or invalid symbols
                Unavailable market data
                Configuration status

                This would help users immediately understand why something is not working instead of seeing an empty HUD and trying to troubleshoot manually.

                Overall, I think the core idea and macro/intermarket logic are very interesting, and the roadmap you described sounds like a good direction.

                Thank you again for being open to feedback.

                Reply
                1. Ffirat_aslan
                    2026-05-23 15:20:57.610Z

                    Hello algo_expert,

                    One more question, if you have experience with different cTrader brokers.

                    To make the symbol alias system more practical, I am trying to understand which brokers are most commonly used by cTrader users and how their symbol naming differs.

                    Do you have any rough estimate or practical experience regarding the distribution of cTrader brokers among users?

                    For example:

                    A Broker: ~40%
                    B Broker: ~20%
                    C Broker: ~10%
                    Other brokers: remaining share

                    The reason I am asking is that I could directly include predefined symbol mappings for the most commonly used brokers, while keeping manual symbol parameters available for less common or unsupported brokers.

                    For example, if a few major brokers cover most of the cTrader user base, I can prioritize their symbol formats first and add mappings such as:

                    US500 / US 500 / SPX500
                    NAS100 / US TECH 100 / USTEC
                    XAUUSD / GOLD
                    and other commonly used broker-specific variations.

                    This would make the setup process much easier for most users while still keeping manual configuration available as a fallback.

                    Any practical insight about the most common cTrader brokers and their symbol naming conventions would be very helpful.

                    Reply
                    1. Aalgo_expert
                        2026-05-24 09:35:39.385Z

                        Hello Firat,

                        I don't have official market-share statistics, so I can only share practical observations from testing many cTrader products and broker environments.

                        From QA experience, I would avoid building the logic around exact broker percentages because users are spread across many brokers. Instead, I would focus on covering the most common symbol naming patterns.

                        From what I frequently encounter:

                        Tier 1 (very common in practical cTrader testing):

                        • Spotware Demo
                        • IC Markets
                        • Pepperstone
                        • Fusion Markets
                        • FTMO / prop environments
                        • broker white-label environments

                        Common symbol variations I often see:

                        Indices:

                        US500
                        US 500
                        SPX500
                        SP500

                        NAS100
                        US TECH 100
                        USTEC
                        NAS100.cash

                        Gold:

                        XAUUSD
                        GOLD
                        XAUUSD.cash

                        Oil:

                        XBRUSD
                        UKOIL
                        BRENT

                        Currencies:

                        EURUSD
                        EURUSD.cash
                        EURUSDm
                        EURUSD.pro

                        One thing I noticed: broker suffixes and prefixes often create more problems than the symbol itself.

                        Examples:

                        EURUSD.m
                        EURUSDpro
                        mEURUSD
                        US500.cash
                        XAUUSD_i

                        Because of that, I would suggest avoiding broker-specific mapping tables first.

                        A more scalable approach might be:

                        1. Build a core alias dictionary:

                        US500 ↔ US 500 ↔ SPX500
                        NAS100 ↔ US TECH 100 ↔ USTEC
                        XAUUSD ↔ GOLD

                        1. Add automatic suffix/prefix detection:

                        .cash
                        .m
                        .pro
                        _i
                        mini

                        1. Keep manual override as fallback.

                        This approach may scale better than maintaining a growing list of broker names and predefined broker-specific profiles.

                        From a QA perspective, I think symbol-pattern recognition may be more future-proof than broker recognition.

                        Hope this helps.

                        Reply
                        1. Ffirat_aslan
                            2026-05-24 11:41:44.985Z

                            Hi,

                            First of all, thank you for the detailed information you shared. It was very useful.

                            Based on this feedback, I have prepared a newly updated version. I will publish it after a short testing phase.

                            In this update, I added a Basic Mode, expanded the symbol scanning pool, and also added manual input fields for the symbols that are most commonly misdetected. This way, automatic detection can still cover the common cases, while users can manually correct broker-specific symbol names when needed.

                            Thanks again for the helpful guidance.

                            Reply