Android developer focused on real-world problems, clean architecture, and how people actually use technology.
I didn't get into development just to write code.
I got into it because I like understanding how things work — and more importantly, how they break.
Most apps today feel disconnected from real people. They look good, but they don't think.
That's what I try to change when I build.
I work mainly with Android (Kotlin), focusing on clean architecture, performance, and scalability. But beyond tech, I spend a lot of time thinking about user behavior, systems, and how small decisions shape big outcomes.
Right now, I'm building apps, exploring backend systems, and experimenting with AI-based solutions.
Not perfect. Still learning. Always building.
Kotlin, Node.js, Python
Bachelor in Computer Science
Built 5+ real-world systems
Each project is a story — a real problem, a solution, and something learned.
Health Connect API
“Most fitness apps depend on external ecosystems. I wanted to understand how data actually flows.”
What I learned
Real-world systems are messy. APIs don't behave like documentation.
Full Stack — Android + Node.js
“I didn't want just a UI app — I wanted control over the entire system.”
What I learned
Frontend is easy. Designing data flow is where things get interesting.
Real-time AI System
“This started as curiosity — how machines read the real world.”
What I learned
Performance matters more than accuracy in real-time systems.
Android — Production App
“Built for real teams managing attendance at scale — reliability was non-negotiable.”
What I learned
Simple problems have complex edge cases when real people are involved.
Structured and honest — not buzzwords. What I actually know and use.
Beyond tools: architecture design, problem decomposition, feature scalability planning, and trade-off analysis.
Things I've been thinking about — on building, systems, and craft.
Most apps fail not because of bad code, but because nobody thinks about how people actually use them.
Clean architecture is not about layers. It's about clarity.
Building fast is easy. Building right is not.
Real-world APIs don't behave like documentation. That's where the real learning happens.
Building a full-stack movie app (Android + Node.js + MongoDB)
Learning more about backend scalability and API design patterns
Experimenting with AI + real-time processing systems
Improving how I think about and design user flows
Inspired by Derek Sivers' /now page movement.
ankit.singh4x@gmail.com