Kotlin Multiplatform on Dhruv Patel - Lead Android Engineer

Part 5 - At Some Point I Stopped Building a Chat App

dhruv.time@gmail.com (Dhruv Patel) — Mon, 05 Oct 2026 14:00:00 +0530

At Some Point I Stopped Building a Chat App

Part 5 - The project became a platform because every feature needed a place to live.

There was a point where I stopped looking at AI Playground as:

chat + models

and started seeing:

runtime orchestration
+
document ingestion
+
retrieval
+
vision
+
memory policy
+
image generation
+
diagnostics
+
model delivery
+
platform integration

At that point, adding another feature without architecture would have been reckless.

Part 2 - The Day a Chat Box Became a Document Engine

dhruv.time@gmail.com (Dhruv Patel) — Mon, 05 Oct 2026 11:00:00 +0530

The Day a Chat Box Became a Document Engine

Part 2 - I thought “attach a PDF” would be a UI feature. It became an ingestion pipeline.

Once local chat was reliable enough, I wanted the next capability that makes a local assistant genuinely useful:

Let me ask questions about my own files without uploading them.

That sounds like:

paperclip icon
+
file picker

It is not.

A PDF is a container. A Word document is structured data. An Excel workbook is a workbook model. A scanned document may have no text layer at all. An image may contain words, diagrams, tables and visual context simultaneously.

Part 1 - I Wanted the Model to Stay on the Phone

dhruv.time@gmail.com (Dhruv Patel) — Mon, 05 Oct 2026 10:00:00 +0530

Beyond the Model: Building a Private AI Playground for Android & iOS

Part 1 - I Wanted the Model to Stay on the Phone

The engineering journey of integrating established on-device AI runtimes into one multimodal mobile product - and everything it takes to make the pieces behave like a coherent system

There was one constraint behind AI Playground that shaped almost every architectural decision that came after it:

I did not want the core AI workflow to depend on a server.