Candlestick Chart Implementation in a Mobile Exchange App

TRUETECH is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.

Development and support of all types of mobile applications:

Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Showing 1 of 1All 1734 services
Candlestick Chart Implementation in a Mobile Exchange App
Complex
~5 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    860
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    746
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1163
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    1035
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    970
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    564

Candlestick Chart Implementation in a Mobile Exchange App

We often encounter situations where a client needs an exchange chart with 60fps performance and smooth zooming over 10,000+ candles. Off-the-shelf libraries either lack candlestick support or require expensive licenses. Our team developed a native solution on Flutter using CustomPainter that bypasses these limitations and saves on licenses. With over 7 years of experience in mobile development and 50+ implemented projects involving custom charts, we guarantee high quality.

Candlestick chart is technically the most complex chart type for a mobile app. Not because of OHLC math, but due to the set of requirements mandatory for exchange UX: smooth zoom/pan over 10,000+ candles, crosshair with coordinates on touch, real-time updates without full redraw, timeframe switching without flickering, correct orientation handling. All these requirements together cause most ready-made libraries to break. A native Canvas implementation delivers 3x smoother scrolling compared to WebView on older devices.

Why Standard Libraries Don't Fit for Candlestick

fl_chart — no candlestick out of the box. You can hack it with custom BarChartRod, but that's a hack without zoom and acceptable performance.

syncfusion_flutter_charts — has SfCartesianChart with CandleSeries, supports zoom/pan, data updates. It's a workable option for most tasks. But the commercial license ($995/year per developer) makes it impractical for startups. For a team of two developers, the license would cost $1,990 per year.

TradingView Lightweight Charts in WebView — the most common approach in production apps of major exchanges. The library is built for production trading UI, optimized for large data volumes, supports all needed features. Overhead from WebView exists but is negligible on modern devices. More: TradingView Lightweight Charts.

Approach Timeline Performance License Suitable For
WebView + TradingView 1-2 weeks 30fps on old devices Free Quick launch
Native CustomPainter 3-5 weeks 60fps on all devices No license Core feature
Syncfusion Flutter Charts 1-2 weeks 45fps $995/year Prototypes

Which Approach to Choose: WebView or Native?

If the chart is a secondary element and time to launch is critical, choose WebView with TradingView. If the chart is the central screen of the app, native implementation delivers 3x smoother scrolling on older devices. We help you choose during consultation — we'll analyze your requirements and propose the optimal solution.

Criteria WebView + TradingView Native CustomPainter
Time to MVP 1-2 weeks 3-5 weeks
Performance 30fps (old devices) 60fps (all)
Customization flexibility Limited Full
Network dependency None None

How to Implement Real-Time Updates Without Lag?

WebSocket connection to the exchange provides tick data. On receiving a new tick, we update only the last candle without rebuilding the entire list:

void onTickReceived(Tick tick) {
  if (_candles.isEmpty) return;
  final last = _candles.last;
  _candles[_candles.length - 1] = last.copyWith(
    high: max(last.high, tick.price),
    low: min(last.low, tick.price),
    close: tick.price,
    volume: last.volume + tick.volume,
  );
  if (tick.timestamp >= last.timestamp + timeframe.milliseconds) {
    _candles.add(Candle.fromTick(tick));
    if (_candles.length > maxCandlesInMemory) _candles.removeAt(0);
  }
  _chartController.notifyListeners();
}

ValueNotifier + ValueListenableBuilder only around CustomPaint — only the canvas repaints, not the AppBar or side panels.

How to Ensure Smooth Zoom on 10,000 Candles?

The main challenge is not redrawing the entire chart on every zoom. We use virtualization: only visible candles are rendered, and on zoom we recalculate the visible range. Additionally, we cache prices and adjust candles per pixel based on scale.

getVisibleRange(int totalCandles, double canvasWidth) {
  final visibleCandlesCount = (canvasWidth / (candleWidth * scale)).floor();
  final start = ((totalCandles - visibleCandlesCount) * offset / maxOffset).clamp(0, totalCandles - visibleCandlesCount);
  return Range(start, start + visibleCandlesCount);
}

This approach guarantees 60fps even on devices with Android 10 and iOS 12.

Native Implementation on Flutter via CustomPainter

For apps where the chart is the main screen, native implementation delivers 60fps on any device. Key components:

Data Structure

class Candle {
  final int timestamp;
  final double open;
  final double high;
  final double low;
  final double close;
  final double volume;
  bool get isBullish => close >= open;
}

Render Pipeline

CustomPainter with shouldRepaint — called on every data change. To avoid repainting the entire chart on a new candle:

class CandlestickPainter extends CustomPainter {
  final List<Candle> candles;
  final CandleChartController controller;
  @override
  void paint(Canvas canvas, Size size) {
    final visibleRange = controller.getVisibleRange(candles.length, size.width);
    final visibleCandles = candles.sublist(visibleRange.start, visibleRange.end);
    final priceRange = _calculatePriceRange(visibleCandles);
    final candleWidth = size.width / visibleCandles.length * controller.scale;
    for (var i = 0; i < visibleCandles.length; i++) {
      _drawCandle(canvas, visibleCandles[i], i, candleWidth, size.height, priceRange);
    }
    if (controller.crosshairVisible) {
      _drawCrosshair(canvas, controller.crosshairPosition, size);
    }
  }
  // ... _drawCandle implementation
  @override
  bool shouldRepaint(CandlestickPainter old) => old.candles != candles || old.controller != controller;
}

Gesture Handling: Pan and Pinch-Zoom

GestureDetector with onScaleStart/Update for pinch-zoom, onPanUpdate for scrolling along the time axis. Clamp scale — important: without it, users could zoom to a single candle filling the entire screen.

GestureDetector(
  onScaleUpdate: (details) {
    setState(() {
      controller.scale = (controller.scale * details.scale).clamp(0.5, 10.0);
      controller.offset += details.focalPointDelta.dx;
    });
  },
  child: CustomPaint(painter: CandlestickPainter(candles, controller)),
)

Crosshair on Long Press

GestureDetector(
  onLongPressStart: (details) {
    controller.crosshairVisible = true;
    controller.crosshairPosition = details.localPosition;
    final candleIndex = controller.positionToIndex(details.localPosition.dx, candles.length);
    if (candleIndex < candles.length) _showCandleInfo(candles[candleIndex]);
  },
  onLongPressMoveUpdate: (details) {
    controller.crosshairPosition = details.localPosition;
  },
  onLongPressEnd: (_) => controller.crosshairVisible = false,
)

Timeframe Switching

Buttons 1m / 5m / 15m / 1h / 4h / 1D / 1W. On switch, we request a new set of candles and apply a crossfade animation to eliminate flickering. Use AnimatedSwitcher with timeframe as key.

Technical Indicators (Optional)

MA, EMA, Bollinger Bands, RSI — each drawn as an additional layer in CustomPainter. RSI and MACD are placed on a separate lower CustomPaint with fixed height and shared time axis with the main chart.

Work Process for Candlestick Chart

  1. Analysis — define performance requirements, list of indicators, timeframes.
  2. Design — choose approach (WebView or native), design render architecture.
  3. Implementation — write code, connect WebSocket, implement gestures.
  4. Testing — test on 10+ real devices, including older models.
  5. Deployment — publish to App Store / Google Play, provide source code.

What's Included

  • Implementation of candlestick CustomPainter or TradingView WebView integration
  • Pan/zoom gestures with proper limits
  • Crosshair with info panel
  • Real-time updates via WebSocket
  • Timeframe switching
  • Technical indicators (MA, EMA, Bollinger Bands — upon agreement)
  • Volume bars on lower panel

Timeline

WebView + TradingView Lightweight Charts: 1–2 weeks (including WebSocket integration). Native CustomPainter with full exchange chart functionality: 3–5 weeks. Cost is calculated individually. Get a consultation — contact us to evaluate your project.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Criteria Firebase Analytics Amplitude Mixpanel
Free limit Unlimited (Spark plan) Up to 10M events/month Up to 1K MTU/month (Special)
Data latency Up to 24 hours (standard) Minutes (real-time) Minutes (real-time)
Funnels and cohorts Basic funnels, limited count Deep funnels, Journeys, cohorts Funnels, Retention, Insights
BigQuery export Yes (free, raw data) Yes (subscription) Yes (Enterprise)
Session Replay No Yes (iOS/Android SDK) No
Ad integration Google Ads (native) Via Universal Links Via partners

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Criteria Firebase Crashlytics Sentry Instabug
Free limit Unlimited (Spark) 5k events/month 250 MAU
Grouping By stack trace + parameters By fingerprint By stack trace + metadata
Symbolication Automatic (via file) Automatic (via CLI) Automatic
Velocity alerts Yes (by % change) Yes (by count) Yes (by threshold)
Extra context Logs, Keys, Custom Keys Breadcrumbs, User, Tags User steps, network requests
Price Free (in Firebase) Paid plans available Paid plans available

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

  • Development and approval of a tracking plan with product and marketing teams.
  • SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
  • Setup of funnels, cohorts, dashboards, and alerts.
  • Automation of symbolication and .dSYM upload via Fastlane.
  • Documentation of events and parameters.
  • Team training on the analytics platform.
  • Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.