Open source / Published tools

Make the hidden state explicit.

Small, focused tools built around problems I encountered while shipping mobile products and developer workflows. Source-visible, published, and candid about their limits.

rn-bootloader

Published · v0.1.1

Give startup work an explicit order.

Phase-based React Native startup with blocking and non-blocking tasks, retry, timeout, and readiness controls.

react-native-appcycle

Published · v0.2.1

Make application lifecycle visible.

Foreground/background awareness, React-powered overlays, and native Android entry points in one lifecycle API.

latch-core

Published · v0.1.3

Inspect before deciding.

The shared engine for registry resolution, integrity verification, static risk signals, caching, and policy.

@meredian-labs/latchx

Published · v0.1.3

Audit before execution.

A package runner that makes the inspection and approval decision explicit before delegating execution.

@meredian-labs/latchpm

Published · v0.1.2

Audit before installation.

An npm installation wrapper that puts local inspection and policy evaluation ahead of installation.

Versions reviewed in the portfolio source documents on 22 September 2026. Follow the package links for the latest releases.

Two moments that shape a mobile experience.

A useful first render. A predictable return from the background. Startup sequencing and application lifecycle are easy to distribute across effects and callbacks, until a user encounters the resulting uncertainty.

rn-bootloader organizes work into explicit pre-UI and post-UI phases. react-native-appcycle exposes foreground/background behavior and Android entry points through a React Native API.

Under the native boundary

react-native-appcycle includes new-architecture code generation and Kotlin/Objective-C surfaces. Foreground runtime behavior, Quick Settings, accessibility triggers, and optional assistant invocation have platform-specific setup requirements. The repository documents integration and compatibility.

A clear limit is part of the API.

Latch reports local static risk signals and evaluates policy before delegation. It does not prove a package safe, sandbox its execution, or replace every package-manager behavior.

One product, multiple engineering surfaces.

A frontend center. A wider field of view.

Application

Complex client state. End-to-end product delivery.

React Native product ownership

Native Android

The platform behavior beneath the interface.

Telephony & lifecycle integrations

Services

Features that cross the client boundary.

Payments & real-time events

Web

Operational interfaces built for real conditions.

Offline-first architecture

Public packages + private professional contributions

Some of the most meaningful work is private.

My professional work includes product applications, native Android integrations, supporting services, dashboards, and websites. These case studies describe the engineering surfaces without exposing internal repositories or proprietary product details.

View my GitHub profile
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.

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

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