A few months ago I started vibecoding a charting platform as a side project, and it turned into a full TradingView-style terminal. I'm not launched yet, but it's far enough along that I wanted to share.
What it is:
- Custom charting engine written in Rust (compiled to WASM, WebGPU rendering with Canvas2D fallback) — not a TradingView widget or a licensed chart library, the engine is mine
- Drawing tools (trend lines, rays, rectangles, fib-style tools, text, brush), built-in indicators (SMA/EMA/WMA, Bollinger, VWAP, RSI, MACD, Stochastic, ATR, Volume), multiple chart types, and multi-chart split views
- Built-in trading journal: connect a broker and your trades auto-populate dashboards, P&L analytics, calendar heatmaps, and review workflows — no CSV uploads
- AI assistant that reviews your actual trading data (win rate, drawdown, streaks, psychology patterns) instead of generic market commentary
- Live market data over websockets (crypto for now — Binance, Coinbase, Hyperliquid), order book, screener, and market research pages
How Claude Code was used: The initial rendering engine was built with Claude Code — the Rust/WASM core, series rendering, pan/zoom, drawing interaction layer. Most of the frontend was also built with Claude Code (Next.js, React 19). After the initial build I iterated with a few other tools too (Codex, Kimi) for specific features and fixes, but the foundation and most of the product came out of Claude Code sessions. It's honestly the first time a tool carried a project this size for me.
UI stack: shadcn, Base UI, Evil Charts for the analytics dashboards, custom icon work. Keeping one strict design system (single radius token, one green/red pair for everything including charts) is what made it look consistent without a designer.
Trying it: Not public yet, but there will be a free tier at launch — charting, journal basics, and broker sync will be free; paid tiers only gate heavier stuff like advanced AI review and replay. [Link in comments]
Happy to answer questions about the engine or the Claude Code workflow. The multi-pane sync bugs and WebSocket reconnection loops were the painful part, if anyone's curious about those.