About Zeeshan Bhatti

Background

I'm Zeeshan Bhatti, the founder and sole developer behind Zee Tech Innovations. I build native Android applications — everything from casual games to full business-management systems — using Kotlin, Java, and the standard Android Studio toolchain. Alongside app development, I'm currently studying Database Administration & Management, which is where most of my backend and database work comes from.

I started with small Android projects to learn the platform properly: publishing a puzzle game to the Google Play Store, then moving into larger builds like a native music player app with a foreground playback service, equalizer, and sleep timer. In parallel, I've built full-stack systems on the database side — an expense tracker, an insurance management platform, and coursework projects — using Node.js/Express with Oracle Database and MySQL.

What I actually work on

• Android app development — Kotlin and Java, Android Studio, targeting current API levels (currently building against API 36).
• App monetization — AdMob integration done correctly, including the mistakes to avoid (like accidentally shipping a test ad unit ID to production).
• Backend & database systems — Node.js/Express APIs, Oracle DB (stored procedures, views, triggers), and MySQL.
• Play Store publishing — store listings, content ratings, and the review process itself.

Education

I'm currently enrolled in a Database Administration & Management program, which covers relational database design, SQL, stored procedures and functions, triggers, and role-based access systems. Several of the full-stack projects on this site — including the insurance management system and expense tracker builds — started as coursework and were extended into complete applications with real authentication and multiple user roles (admin, customer, agent).

Tools & technologies

How I work

I work on one project at a time and see it through to a working, published result rather than juggling half-finished builds. For client work, that means a clear scope up front, regular updates while the app is in progress, and a store-ready build at the end — not just source code. For my own apps, it means testing on real devices across Android versions before anything goes live, rather than assuming an emulator build is good enough.

Where to find the work

Published apps are listed on the apps page, technical write-ups are on the blog, and service details are on the services page. If you'd like to work together, the contact page has the fastest way to reach me.