Pocket Option Pattern-Discovery & Trading App Development

About the project

Pocket Option Automated Pattern Discovery, Backtesting & Trading Software Build a complete Pocket Option pattern-discovery, backtesting, simulation, demo and automated trading application from scratch. 1. REAL DATA Use only legitimate, verifiable Pocket Option market/account data. No fake candles, balances, payouts, trades, results or hard-coded winning strategies. If data is unavailable, show NOT AVAILABLE / NOT TESTABLE / INSUFFICIENT DATA. Support all legitimately accessible markets, OTC markets, timeframes and expiry/timer durations. Validate timestamps, OHLC, duplicates, gaps, missing candles, timeframe, market and data integrity. Never invent missing data. 2. CANDLE PATTERN ENGINE User selects candle count: 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | … | MAX Generate EVERY possible Green/Red combination dynamically using 2^N. Examples: 2=4, 3=8, 4=16, 5=32, 6=64, 7=128, 8=256, 9=512, 10=1,024. Example pattern: GREEN → RED → GREEN → RED → GREEN → GREEN Detect the exact pattern in real time. 3. EXACT ENTRY When the final candle of the selected pattern closes, Step 1 enters immediately. Do NOT wait for another candle or another occurrence of the pattern. Backtesting must use exactly the same rule and must have no look-ahead bias. 4. STEP SELECTOR — HARD TRADE LIMIT UI: 1 STEP | 2 STEP | 3 STEP | 4 STEP This is the HARD MAXIMUM number of trades allowed in one sequence. 1 STEP: maximum 1 trade. BUY → WIN/LOSS → END. 2 STEP: maximum 2 trades. BUY → LOSS → immediately SELL → END. 3 STEP: maximum 3 trades. BUY → LOSS → SELL → LOSS → BUY → END. 4 STEP: maximum 4 trades. BUY → LOSS → SELL → LOSS → BUY → LOSS → SELL → END. If 2 STEP is selected, Step 3 MUST NEVER execute. If 3 STEP is selected, Step 4 MUST NEVER execute. There must NEVER be a Step 5. The selected step limit must be enforced in backtesting, simulation, demo, live execution, risk calculations, sequence management, statistics and the dashboard. 5. LOSS → NEXT STEP IMMEDIATELY The pattern triggers Step 1 only. If a trade loses, the next selected step must enter immediately after the loss is confirmed. Do NOT wait for: * Another pattern * Another signal * A new candle pattern Example: Pattern: G → R → G → R → G → G Steps: 2 STEP Directions: BUY → SELL Final candle closes → BUY enters. BUY loses → immediately enter SELL. SELL wins/losses → sequence ends. After a WIN, immediately reset and wait for the next occurrence of the pattern. After the final selected step, the sequence ends. Only legitimate conditions may prevent the next trade, such as insufficient balance, payout below minimum, market unavailable, connection failure or risk limit. Record the exact reason. 6. BUY/SELL SEQUENCES Generate all combinations dynamically. 1 STEP = 2 combinations. 2 STEP = 4 combinations. 3 STEP = 8 combinations. 4 STEP = 16 combinations. Examples: BUY → BUY BUY → SELL SELL → BUY SELL → SELL For 3/4 steps generate every possible sequence automatically. 7. RISK / TRADE SIZE Allow: * % current balance * % starting balance * Fixed amount * Configurable loss multiplier * Maximum trade size * Maximum exposure * Maximum sequence loss * Maximum consecutive losses Example: R20,000 balance, 1% risk = R200 initial trade. 2× multiplier: Step 1 = R200 Step 2 = R400 Step 3 = R800 Step 4 = R1,600 Multiplier must be configurable or disabled. 8. PAYOUT User selects minimum payout, e.g. 92%. Check actual current payout immediately before EVERY trade, including every subsequent step. If below minimum → DO NOT ENTER and record why. Use genuine historical payout data for backtesting where available. Never fabricate it. 9. BACKTEST ENGINE Test: Market × OTC × timeframe × timer × candle count × every candle pattern × step count × every BUY/SELL sequence × lookback × payout × risk configuration Example: Pattern: G → R → G → R → G → G Timeframe: 30s Timer: 5s Steps: 2 Direction: BUY → SELL Payout: ≥92% Balance: R20,000 Risk: 1% The backtester must reproduce the exact live logic. Support lookbacks: 1h, 3h, 6h, 12h, 24h, 3d, 7d, 30d, full history and custom dates. 10. STATISTICS For every configuration show: * Market/OTC * Candle count * Exact pattern * Timeframe * Timer * Step count * Direction sequence * Lookback * Occurrences * Total trades * Wins/losses * Win rate * Payout * Net result * Drawdown * Losing/winning streaks * Trade frequency * Expectancy * Sample size Sample size must be clearly visible. Allow minimum occurrence requirements. Where enough data exists, support in-sample, out-of-sample and walk-forward testing. Do not permanently label anything as the “best strategy”; continuously recalculate based on selected data. 11. LIVE ENGINE Flow: 1. Connect to selected account. 2. Confirm Demo/Live. 3. Read real balance. 4. Receive real-time data. 5. Build selected candles. 6. Detect pattern. 7. Check historical configuration. 8. Check timeframe/timer. 9. Check payout. 10. Check current step. 11. Calculate direction and amount. 12. Run risk checks. 13. Enter Step 1 at final candle close. 14. Wait for actual result. 15. WIN → reset. 16. LOSS → immediately activate next step. 17. Recheck payout/risk. 18. Enter next step immediately if permitted. 19. Continue ONLY up to selected step count. 20. End sequence and wait for next pattern. 21. Log everything. 12. DEMO / LIVE Modes: BACKTEST | SIMULATION | DEMO | LIVE Demo/Live must use actual account information. Display account type, balance, currency and connection status. LIVE requires explicit confirmation and must be clearly indicated. 13. RISK STOPS User-configurable: * Daily TP * Daily SL * Session TP/SL * Maximum trades * Maximum consecutive losses * Maximum sequence loss * Maximum exposure * Maximum trade size * Cooldown * Emergency stop When a limit is reached, stop opening new trades. 14. STATE + JOURNAL Persist sequence state so restart cannot duplicate or incorrectly reset trades. Store: account, balance, sequence number, pattern, step count, direction sequence, current step, trade amount, entry, expiry, result and risk settings. Log every trade: timestamp, market, OTC, pattern, candle count, timeframe, timer, direction, sequence, step, payout, entry/exit, amount, WIN/LOSS, balance before/after, execution status, timing between trades and any error/block reason. 15. DASHBOARD Show: ACCOUNT: Demo/Live, balance, starting balance, current balance, daily/session P/L. PATTERN: candle count, pattern selector, selected pattern, occurrences and statistics. STEPS: 1/2/3/4 STEP and current position, e.g. STEP 2 / 4. DIRECTION: selected BUY/SELL sequence. TRADE: direction, amount, timer, payout, entry, expiry and result. RISK: risk %, multiplier, TP/SL, exposure and loss limits. MARKETS: market, price, candle, timeframe, payout, detected pattern, statistics, direction and trade status. 16. ERROR HANDLING Safely handle connection loss, unavailable markets, payout changes, delayed/missing data, duplicate signals, failed orders, unknown results, timeouts, WebSocket/API errors, reconnection and restarts. Never assume an order succeeded if its status is unknown. NON-NEGOTIABLE EXECUTION RULES 1. Selected step count = hard maximum trades per sequence. 2. 1 STEP = max 1 trade. 3. 2 STEP = max 2 trades. 4. 3 STEP = max 3 trades. 5. 4 STEP = max 4 trades. 6. Pattern triggers Step 1. 7. Step 1 enters at final pattern-candle close. 8. Loss → next selected step immediately after loss confirmation. 9. No new pattern is required between steps. 10. WIN → reset. 11. Final selected step → sequence ends. 12. New sequence requires a new pattern. 13. Check payout before every trade. 14. Check risk before every trade. 15. No fake data/results. 16. No look-ahead bias. 17. Backtest and live logic must be identical. 18. Never exceed selected step count. 19. Record every trade and decision. 20. Record every skipped trade and its reason. FINAL OBJECTIVE Create a professional application that lets me: Select candle count → generate every pattern → select pattern → select 1/2/3/4 STEP → select BUY/SELL sequence → choose market/timeframe/timer → backtest → analyze transparent statistics → run Simulation → Demo → Live. The exact configuration and sequence logic used in backtesting must be the exact logic used during live execution.

Skills required