Use cases

Realtime for products where a delay changes the experience.

DomVia Realtime fits live product flows: banking alerts, logistics control rooms, private messaging, operations dashboards, AI progress, device state, and field coordination.

Mobile notifications

Realtime is best while the app is open. Lock-screen mobile push still needs APNs or FCM, usually triggered by the same server event.

Banking and fintech

Live transaction, risk, and account alerts.

Use realtime for in-app account movement: balance changes, card activity, fraud review prompts, approval state, queue movement, and operations alerts. Lock-screen push still needs APNs or FCM when the app is closed.

Common signals

transaction.postedbalance.updatedrisk.reviewapproval.changed

Product outcome

In-app banking alerts

Fraud review prompts

Live approval state

Realtime flowBanking and fintech

Source

Card activity

Verify

Risk + ledger

Deliver

Customer app

A card, transfer, or approval event starts inside the bank system.

Trusted server code validates the account, risk state, and notification rule.

DomVia Realtime updates the open mobile app, dashboard, or operator queue instantly.

For closed apps, the same event can trigger APNs or FCM for lock-screen delivery.

Logistics control room

Live dispatch, trip, and delivery coordination.

Control rooms need moving state: pickup, route progress, driver nearby, delay, failed delivery, support needed, and completed handoff.

Common signals

trip.starteddriver.nearbydelivery.failedroute.updated

Product outcome

Live maps

Dispatch queues

Exception handling

Realtime flowLogistics control room

Source

Driver app

Verify

Dispatch rules

Deliver

Control room

A driver, courier, inspector, or field worker sends a status or location update.

Your server confirms the assignment, trip state, and viewer permissions.

Realtime events update the control room, customer screen, and internal queue.

Exceptions become visible immediately so dispatch can reroute or escalate.

Chat and presence

Private rooms, typing, read state, and online members.

Use private and presence channels for customer support, marketplaces, property platforms, operator chats, team rooms, and user-to-user messaging.

Common signals

message.newtyping.startedmessage.readmember.joined

Product outcome

Private chat

Typing indicators

Presence state

Realtime flowChat and presence

Source

Member A

Verify

Private room

Deliver

Member B

A user opens a room, sends a message, or starts typing.

Trusted server code verifies room membership before private access is granted.

Realtime events deliver message state, typing state, read state, and presence.

Optional strong privacy mode can encrypt sensitive payloads before delivery.

Operations dashboards

Dashboards that update without refresh.

Keep admin panels, billing queues, support inboxes, incident screens, usage counters, and security activity visible as they happen.

Common signals

ticket.createdusage.limit_nearincident.openedpayment.reviewed

Product outcome

Support queues

Usage counters

Incident panels

Realtime flowOperations dashboards

Source

Product events

Verify

Operations rules

Deliver

Live dashboard

A product event, billing event, status event, or support event happens.

Your server normalizes it into a safe event name and payload.

Realtime updates subscribed dashboards and internal consoles instantly.

Operators see state changes without manual refresh or polling loops.

AI products

Streaming AI, jobs, and assistant progress.

Show model output, background job progress, moderation status, file processing, agent decisions, and task completion as they move through your system.

Common signals

job.startedtoken.streamreview.requiredjob.completed

Product outcome

Streaming output

Job progress

Agent activity

Realtime flowAI products

Source

AI job

Verify

Worker state

Deliver

User screen

A user starts an AI task, file process, assistant run, or background job.

Your worker emits progress checkpoints instead of making the user wait blind.

Realtime streams task state, partial output, warnings, and completion.

The UI can show progress bars, live text, review queues, and next actions.

IoT and field operations

Device signals, crews, sensors, and live supervision.

Use realtime for field teams, device state, active sessions, alerts, sensor movement, machine events, and coordinated operational response.

Common signals

device.onlinesensor.warningcrew.arrivedthreshold.crossed

Product outcome

Live supervision

Device alerts

Field coordination

Realtime flowIoT and field operations

Source

Device signal

Verify

Rules engine

Deliver

Ops viewer

A sensor, machine, kiosk, field device, or team member emits a state update.

Trusted server code filters noise, checks thresholds, and chooses who can view it.

Realtime pushes safe state into monitoring screens and responsible team views.

Escalations can trigger alerts, tickets, or push notifications when needed.

Current world

Where realtime is used today.

Mobile banking alerts

Fraud review prompts

Live logistics control rooms

Driver and courier tracking

Private messaging

Typing and read receipts

Presence and active viewers

Live support queues

Incident dashboards

Billing and approval workflows

Streaming AI responses

Background job progress

IoT device state

Gaming lobbies

Collaboration cursors

Marketplace activity feeds

Healthcare operations

Field team coordination

Live auctions

Command centers

Reality check

Realtime and push work together.

Realtime updates active sessions: open mobile apps, browser tabs, dashboards, control rooms, and operator consoles.

Push notifications wake users outside the app: lock screen, notification tray, background app state, and urgent offline alerts.

For calls, chat, banking alerts, and logistics, the usual production flow is server event first, realtime delivery for active clients, then APNs or FCM when the user is offline.

Discuss a use case