arqam365

Founder & CEO, Revzion

Work

Systems built under pressure

Product lines built and maintained at Revzion. Each one is described by the constraint that made it hard — that is the part worth reading, and the part most portfolios leave out.

Client names and commercial outcomes are covered by agreement. Happy to walk through specifics under NDA.

01

Evolwe Ring

Connected Health · Wearable

The constraint

A smart ring streams biometric data continuously, from a battery that cannot afford a chatty radio, to a phone that is often asleep, over a link that drops whenever the wearer walks into another room.

  • Kotlin Multiplatform
  • BLE
  • PubNub
  • Node.js
  • Next.js
  • TypeScript

Approach

BLE transport with reconnection and backfill built into the protocol rather than bolted on. Real-time fan-out to companion apps and dashboards, shared domain logic across Android and iOS so a firmware change lands once, and an AI layer over the resulting time-series.

What it demonstrates

Hardware-to-cloud ownership: firmware boundary, mobile runtime, realtime backend and the analytics on top, built as one system.

02

Clinical & Diagnostic Apps

Health Technology

The constraint

Clinical tooling is used in short, interrupted sessions by people who cannot re-enter data because the network dropped, and it carries records that must stay correct under every failure mode.

  • Kotlin
  • Jetpack Compose
  • Offline-first sync
  • RBAC

Approach

Offline-first state with deterministic sync, strict domain modelling of records, and role-based access designed before the first screen — because retrofitting permissions into a shipped clinical product is not a refactor, it is a rewrite.

What it demonstrates

Building for correctness-critical domains where a lost write is a real-world consequence, not a bug report.

03

Commerce & Marketplace Platforms

E-Commerce · Operations

The constraint

Storefronts are the easy half. Catalogue, inventory, fulfilment, payments and the admin surface the operations team actually lives in are where commerce projects stall.

  • Next.js
  • TypeScript
  • Node.js
  • PostgreSQL

Approach

Modular service boundaries so catalogue, orders and payments evolve independently, with an operations dashboard treated as a first-class product rather than an afterthought.

What it demonstrates

Shipping the unglamorous 70% — the back office — which is what determines whether a commerce platform survives its first peak.

04

Real-Time Operations Systems

Logistics · Live Tracking

The constraint

Live tracking and dispatch look simple until you have hundreds of devices reporting at once, on mobile networks, where every stale marker on a map is an operational decision made on bad data.

  • Kotlin
  • WebSockets
  • Pub/Sub
  • TypeScript

Approach

WebSocket and pub/sub transport sized for concurrent device load, with backpressure and reconnection treated as the normal case rather than the exception.

What it demonstrates

Real-time systems that hold their shape under concurrency, not just in a two-device demo.

Building something with similar constraints?

Start a conversation