About Projects Experience Thinking Connect
Android Engineer / Product Builder

Ameya Kulkarni.

I engineer systems that ship fast, stay minimal, and respect the user's attention.

Ameya Kulkarni Mumbai, India
Building chattodo.co, solo product engineering at a stealth startup.
Scroll ↓

The Operating
System.

I build software the way I think about products - with structural conviction MVI architectures, event-driven sync, delta-time game loops: precision over convenience. , ruthless scope reduction, and a deep bias for shipping.

At Preseed, I learned that product isn't about adding features - it's about removing decisions "Every extra feature is a decision point. Fewer decisions, less noise." - chattodo.co . I work in Kotlin and Jetpack Compose, building everything from cloud-synced real-time apps to fully offline Bluetooth communication systems. I care about the architecture beneath the interface.

Kotlin Jetpack Compose Android SDK MVI / MVVM Coroutines & Flow Firebase (Realtime Systems) Bluetooth RFCOMM (P2P) Room DB AWS S3 Event-Driven Architecture Real-time Sync Custom Canvas & Rendering
4+
Systems built end-to-end
100K+
Architecture Scaled To
Single
Source of Truth (Architecture)
// SYS.NOTE

Location: India
Degree: B.E. Electronics & CS
Institute: SIES GST, Nerul
Focus: Native Android

Compiled
Systems.

Zero-to-one executions. Thesis / Execution / Impact.

Runtime
Logs.

Stealth Startup | Jul 2025 – Present
Android Developer Intern

Building a collaborative chat interface with Jetpack Compose. Dynamic messaging with replies, real-time sync, and task derivation.

The Learning: Context switching kills momentum. Converting messages into actionable Todo states reduces cognitive load. Collaborative sync taught me the hardest edge cases in distributed state management.
Preseed @ Chattodo | Jul 2024 – Aug 2024
Android Developer Intern

Complete architectural redesign for real-time messaging. Scaled database performance to handle 100,000+ active users.

The Ambiguity: Scaling event-driven architecture isn't about faster queries - it's about predicting bottlenecks before they saturate. Redesigning this solo taught structural prudence over "add-more-servers" mentality.
// RUNTIME.LOG

Focus: Learnings > Outputs.
Format: What changed my thinking.

Thinking
Fragments.

01 / On Anti-Bloat

Every extra feature is a decision point forced upon the user. Fewer decisions equal less noise. Systems should be designed for clarity, not metrics padding.

02 / Events Over Requests

Request-response is a conversation. Event-driven is an ecosystem. When your system reacts instead of being asked, latency becomes an architectural choice, not a limitation.

03 / Invisible Protocols

The best networking architectures are invisible. If a user notices a loading spinner during a chat, the protocol has already failed.

04 / Solo is not Small

One person operating with conviction can ship a product that feels like a team of ten.

// INTERNAL.LOG

Operating principles,
not performance reviews.