By ChartNothing Product Team · Updated · 6 min read
How ChartNothing builds quiet, shareable TradingView-native chart grids, chooses Coinbase-first crypto suggestions, and stores dashboard recipes without warehousing candle history.
The dashboard is the product surface
ChartNothing keeps the web price experience close to the thing users came to inspect: charts. A dashboard recipe contains symbols, timeframe, column count, order, and display settings. Those values can live in the URL for a bookmarkable view and, when signed in, in a saved dashboard record.
TradingView widgets handle web candles and indicators. ChartNothing coordinates the grid and navigation. This avoids pretending that a thin wrapper owns or reconstructs exchange market data while still giving users a cleaner multi-chart workspace than a general trading portal.
Why search is Coinbase-first
Typing a common crypto asset can produce many equivalent venue pairs. Showing Coinbase, Binance, Kraken, and Bitfinex versions of the same USD idea creates noise before the chart is even open. ChartNothing therefore prefers a Coinbase USD market when one is known and keeps explicit exchange input intact when the user deliberately types a venue-qualified TradingView symbol.
The catalogue is curated, so a generated crypto fallback does not turn an unknown stock ticker into a made-up coin. If a symbol is not in the catalogue, the UI still offers a direct TradingView fallback that the user can verify in the embedded chart.
What ChartNothing stores
For the default web dashboard, ChartNothing stores the recipe rather than OHLC candles, market-cap history, or exchange archives. This keeps bookmark and saved-layout behavior deterministic while leaving market-data licensing, corporate actions, bad candles, delistings, and venue outages with the chart provider selected for the page.
A future native price feed is a different product requirement. It would need a licensed provider, bounded shared cache, symbol mapping, freshness policy, and per-subscriber metering. It should not be implied by the current TradingView web chart experience.
Building a readable grid
Use fewer columns when labels and indicators need room, and more columns when the dashboard is a scanning wall on a large display. The fullscreen route removes surrounding product controls, keeps add-chart and global timeframe controls in the header, and lets the chart grid consume the remaining viewport.
A useful watchlist groups related questions rather than collecting symbols without purpose. A crypto macro view might combine major assets, dollar strength, total market measures, and one risk proxy. A sector view might compare leaders on the same interval. Consistent intervals and units make visual comparison much easier.
Frequently asked questions
Does ChartNothing store TradingView candles?
No. The default dashboard stores symbols and layout recipes while TradingView renders web market charts.
Can I choose Kraken or Binance explicitly?
Yes. Coinbase is the de-duplicated default where available, but an exchange-qualified symbol typed by the user is preserved.
Will the same dashboard open on another device?
A shared URL carries symbols, interval, and layout. Signed-in saved dashboards add account persistence; native widget feeds use a separate published feed contract.