Available for new work

Vrajesh Trivedi

Software Developer — Android, Wear OS & Chrome Extensions

I build products that ship — real-time Android systems, browser automation, and local-first platforms, taken from problem to production.

  • 3 Products shipped
  • 2 Platforms: Android & browser
  • End‑to‑end Own the build & the tests

How I work

Not a list of exercises — a path from problem to people.

These projects are not unrelated. They are the same loop, run at three different scales: find something broken, decide what would actually fix it, choose the shape, build the whole thing, prove it works under real conditions, put it in front of people, and fix what breaks.

  1. 01

    Problem

    Find something broken in my own day.

  2. 02

    Product

    Decide the smallest thing that is genuinely useful.

  3. 03

    Architecture

    Choose the shape before writing code.

  4. 04

    Build

    Ship the whole thing, not a slice of it.

  5. 05

    Test

    Prove it works on real devices, under failure.

  6. 06

    Deploy

    Get it in front of people who are not me.

  7. 07

    Real users

    Watch it break, then fix the right thing.

  8. →

    Repeat

    With a better idea of what actually breaks.

The part most portfolios leave out

Shipping is the easy half. On Audio Rewind the interesting work is that a user action has to survive a Bluetooth drop, a screen-off, a service kill and a repeated request — and a test that only checks the happy path would not notice any of it. So the assertion runs all the way through: user action → handler → transport → processing → state → UI → result. A failure names the broken link instead of just saying "it didn't work".

Want the long version? Ask me about any of these.

Selected work

Products, not exercises.

Three things I identified, architected, built, tested and shipped. Each one has a live surface, a real user-facing constraint, and a hard part that had to be solved rather than worked around.

01 Android · Wear OS shipped

Audio Rewind

Wear OS + Android

An audio rewind button on your wrist. Capture a rolling window of recent sound, pull back the last 15–30 seconds, replay it, and read it as text.

A Wear OS watch app and its Android phone companion. You start a session explicitly, the app keeps a short rolling audio buffer in RAM, and a tap on the watch rewinds the last 15 or 30 seconds — replayed and transcribed. Built with real phone↔watch communication and an automated end-to-end test harness that drives physical devices.

Real-time systemsAudio capture & bufferingDevice-to-device communicationAI transcriptionAutomated device testing
  • Kotlin
  • Android
  • Wear OS
  • Android audio APIs
  • Foreground services
  • Wearable APIs
  • +3
Case study
Audio Rewind — Android · Wear OS. available.
02 Chrome Extension live

Bulk Unsaver for Insta

Chrome Extension

Clear out a Saved collection you have been meaning to clear out for two years — without opening four thousand posts one at a time.

A published Manifest V3 extension that unsaves Instagram posts sequentially, resumably, and only after you explicitly start it. Starts from any post, stops whenever you like, uses randomized delays instead of rapid bursts, and works in any interface language. Commercialised with a license key system.

Browser automationDOM reverse engineeringProductisationLicensing & paymentsPublished shipping product
  • JavaScript
  • Chrome Extensions / Manifest V3
  • DOM automation
  • Chrome extension APIs
  • chrome.storage
  • Licensing & payments
  • +1
Case study
Bulk Unsaver for Insta — Chrome Extension. Chrome Web Store available.
03 Full-stack Product in-progress

May The Job Be With You

Platform · Chrome Extension

Stop retyping your life into forty different job portals. Keep your job-search profile once, in your browser, and fill applications in one click.

A job-application productivity platform: a website and a Manifest V3 Chrome extension working as one local-first product. Detect fields on supported job platforms, fill them from a profile that never leaves the device, and track applications from a Side Panel. You still press submit — the point is removing the typing, not making the decisions.

Local-first architectureFull-stack product thinkingForm & DOM automationData modelling & migrationsWebsite + extension as one product
  • JavaScript / TypeScript
  • Chrome Extensions / Manifest V3
  • Vite
  • IndexedDB / Dexie
  • Side Panel API
  • Browser APIs
  • +2
Case study
May The Job Be With You — Full-stack Product. Live site available.

Each case study covers the problem, what I built, the architecture, what was hard, and how it is tested. See what the set proves together

Capabilities

Three products, eight things they prove.

Each project is a different surface, but the work underneath overlaps. This is what the set covers — and which project is the evidence for each claim.

  • Real-time & embedded-feeling systems

    Rolling audio capture, preallocated ring buffers, foreground services, permission and lifecycle handling — the kind of code where an off-by-one is audible and a GC pause is a bug.

  • Device-to-device communication

    Wearable APIs, request identity, timeouts, deduplication and resync. Two devices that must never disagree about the truth, over a link that will drop.

  • AI in the product path

    Transcription as an asynchronous stage in a user journey — fast enough not to block, isolated enough that its failures cost nothing else.

  • Automated testing on real hardware

    Device discovery, install, launch, UI driving, log and state monitoring, transport tracing and fault injection — an end-to-end suite against physical devices, not emulators.

  • Reverse-engineering a platform you do not control

    Driving a client-rendered app through its own interface, structuring the knowledge so the platform can change underneath you without taking the product apart.

  • Shipping a commercial product

    Chrome Web Store packaging and review, licensing and entitlements, listings, updates, and users reporting things that broke on a page you did not write.

  • Local-first architecture

    A browser-local source of truth with no backend, no accounts and no user data at rest — including the durability costs that comes with, and the migrations that fix them.

  • Product judgment

    Knowing what not to build. No passive recording, no automatic submission, no account wall — the constraints are the product, and they are the reason the product is trusted.

Get in touch

Have something that needs building, or a question about any of these?

I am happy to go deep on the engineering — the buffer design, the transport protocol, the detection heuristics, the testing strategy. Or just say hello.

Send an email