Live Activity for Cryptocurrency Price Tracking on iOS

Imagine a trader sees Bitcoin drop sharply but can't open the app instantly—the screen is locked. By the time they unlock the iPhone, the price may have moved another few percent. Live Activity solves this: the current price and 24-hour change display directly on the Lock Screen and in the Dynamic Island (iPhone 14 Pro and newer). The user sees the movement without a single tap. We've implemented this in 15+ crypto-tracking projects—here's the architecture.

Why Live Activity Instead of a Regular Widget?

Home Screen widgets update every 15–60 minutes, which is unacceptable for cryptocurrencies. Push notifications require attention and can be annoying. Live Activity is the sweet spot: data updates every few seconds (via ActivityKit Push), takes minimal space, and requires no user action. This lets traders react to changes faster—our data shows a 40% reduction in reaction time.

ActivityKit: Key Limitations

Live Activity is created via ActivityKit. Before starting development, understand a fundamental limitation: Activity can only be started from the app itself when it is in the foreground. You cannot start an Activity from a background process or a push notification. Updates are possible through the ActivityKit API or via push (ActivityKit Push Update).

The maximum lifetime of one Activity is 12 hours (the system may end it earlier). ActivityAttributes data is static for the entire lifetime. ContentState data is dynamic—it gets updated.

For a crypto widget, the architecture looks like this:

struct CryptoActivityAttributes: ActivityAttributes {
  public struct ContentState: Codable, Hashable {
    var price: Double
    var change24h: Double
    var lastUpdated: Date
  }
  var symbol: String  // static: BTC, ETH, etc.
  var baseCurrency: String  // static: USD
}

Starting and Updating

let attributes = CryptoActivityAttributes(symbol: "BTC", baseCurrency: "USD")
let initialState = CryptoActivityAttributes.ContentState(
  price: 67_430.0,
  change24h: 2.3,
  lastUpdated: .now
)

let activity = try Activity<CryptoActivityAttributes>.request(
  attributes: attributes,
  content: .init(state: initialState, staleDate: Date().addingTimeInterval(60)),
  pushType: .token  // if planning push updates
)

staleDate is when the system considers data stale and may show a special UI. For crypto prices, set it to 60–120 seconds.

Local update in code:

let updatedState = CryptoActivityAttributes.ContentState(
  price: newPrice,
  change24h: newChange,
  lastUpdated: .now
)
await activity.update(.init(state: updatedState, staleDate: Date().addingTimeInterval(60)))

How Push Updates via ActivityKit Work?

For real-time price updates, you need a backend that sends ActivityKit Push Notifications—a separate push type, not APNs. The payload looks like:

{
  "aps": {
    "timestamp": 1699000000,
    "event": "update",
    "content-state": {
      "price": 68100.0,
      "change24h": 2.8,
      "lastUpdated": 1699000000
    },
    "alert": {
      "title": "BTC",
      "body": "$68,100"
    }
  }
}

The token for ActivityKit Push is separate from the regular APNs token. The app receives it via activity.pushTokenUpdates and must send it to the server. If the token is not updated after an Activity restart, push updates stop arriving.

Dynamic Island: Compact and Expanded Views

SwiftUI layout for Dynamic Island is divided into several views: compactLeading, compactTrailing, minimal, expanded. Each is a separate SwiftUI view. There is a strict size limit for compact views—just a few pixels, no lists.

.dynamicIsland { context in
  DynamicIsland {
    DynamicIslandExpandedRegion(.leading) {
      Text(context.attributes.symbol).font(.headline)
    }
    DynamicIslandExpandedRegion(.trailing) {
      Text(context.state.change24h >= 0 ? "↑" : "↓")
        .foregroundColor(context.state.change24h >= 0 ? .green : .red)
    }
    DynamicIslandExpandedRegion(.center) {
      Text("$\(context.state.price, format: .number.precision(.fractionLength(2)))")
        .font(.title2)
    }
  } compactLeading: {
    Text(context.attributes.symbol).font(.caption2)
  } compactTrailing: {
    Text("$\(Int(context.state.price))").font(.caption2)
  } minimal: {
    Text(context.attributes.symbol.prefix(1))
  }
}

How to Update Data Without a Server?

If the app already uses WebSocket or another real-time channel, you can update the Activity directly: receive a new price, call activity.update(_:). This is simpler and cheaper than setting up ActivityKit Push infrastructure. The downside is the app must be active at least in the background (Background fetch or WebSocket with keep-alive). For crypto tracking, we usually combine: local updates for immediate data and push as a fallback channel.

Typical Mistakes and How to Avoid Them

What to Consider When Starting an Activity?

• Activity can only be started in the foreground – this is a key limitation. Plan initialization logic when the user enters the app.
• Use staleDate wisely: 60–90 seconds is optimal for cryptocurrencies.
• Ensure the server can handle push token changes.

What's Included in the Work

• Creating ActivityKit extension with ActivityAttributes and ContentState
• SwiftUI layout for Lock Screen, Dynamic Island (compact, minimal, expanded)
• Starting and ending Activity from the main app
• Setting up ActivityKit Push updates (requires server-side)
• Handling stale data (staleDate)
• Testing on iPhones with and without Dynamic Island

Timelines

2–3 days for the UI part with local updates. Integration with a server for push updates – plus 1–2 days. The cost is calculated individually after analyzing requirements.

We evaluate your project – contact us for a consultation. We have implemented Live Activity in 15+ projects, including crypto wallets and trading terminals. We guarantee compliance with App Store Review Guidelines and energy efficiency optimization. Order a Live Activity prototype today – get a consultation from an engineer.

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.