Nishchay Bhatt

Work / Selected systems

The interface is only part of the story.

Three records of working across boundaries: native platforms, unreliable networks, and package execution. Each explains the constraint, the decisions, and what is still unfinished.

01 /Production
Mobile / Native / Real-time

HiRobin — AI calling assistant

Owning a React Native product across mobile architecture, Android telephony, call forwarding, payments, real-time chat, and VoIP foundations.

A calling assistant crosses mobile UI, Android platform behavior, telecom workflows, payments, and live server events. The client has to make those systems understandable to the user.

Outcome

Lead mobile contribution to a product with 1.1M installs and approximately 296K monthly active users. September 2026 snapshot.

  • React Native
  • TypeScript
  • Android native modules
  • WebSockets
  • Payments
  • Telephony
Read the case study
HiRobin / Product boundaries
InterfaceReact Native applicationOnboarding · Conversations · Subscriptions
PlatformNative AndroidDialer & telephony
Permissions & lifecycle
ServicesLive product stateEvents & chat
Payments & calling
One user journey. Multiple state owners.
Sanitized responsibility map. Shows integration surfaces, not proprietary architecture.
02 /In progress
Web / Offline / Geospatial

Operations software for unreliable networks

A React and TypeScript field-operations console designed around map-heavy workflows, offline writes, reconnect synchronization, and constrained devices.

Operational software cannot assume a stable connection or a clean linear workflow. The interface has to preserve user intent and make synchronization state understandable.

Current state

An evolving architecture record. Implementation and production validation are still in progress.

  • React
  • TypeScript
  • Leaflet
  • Zustand
  • TanStack Query
  • IndexedDB
  • WebSockets
View architecture and progress
Operations / Proposed write lifecycleIn progress
User updates a taskNetwork unavailable
  1. Save the intent locallyPersist operation in IndexedDB
    Queued
  2. Reconnect & reconcileCompare the server revision
    Syncing
  3. Confirm or surface a conflictKeep the operator in control
    Review
Architecture study: queued work stays visible until the server confirms it.
03 /Open source
Developer tools / Package safety

Safer package execution and installation

A local-first audit pipeline that inspects npm packages before execution or installation and makes the approval decision explicit.

Package runners combine retrieval and execution into one convenient step. Latch changes the order: resolve, verify, inspect, evaluate policy, then run only after approval.

Outcome

Three published packages. One shared inspection and policy engine.

  • TypeScript
  • Registry resolution
  • Integrity verification
  • Static analysis
  • Policy engine
  • CLI / CI
See the audit model
Latch / Inspect · Decide · RunLocal-first

A trust boundary, before execution.

  1. 01ResolveExact version
  2. 02VerifyArtifact integrity
  3. 03InspectStatic risk signals
  4. 04DecidePolicy & approval
Execute only when allowed

latch-core latchx / latchpm

Static risk signals inform a decision. They are not a malware verdict or a sandbox.
Have a difficult product problem?

Let’s make it
work in the real world.

I’m interested in roles where I can own meaningful frontend and mobile systems, and build with people who care about the details.

Email NishchayView LinkedIn

Open to SDE-2 / Senior Frontend & React Native roles

Bengaluru, India
Bengaluru, India-wide & suitable remote opportunities