Rabia K.

I started building production apps years before AI coding assistants existed. My architecture instincts were shaped by doing things the hard way first. Today I use AI tooling to accelerate delivery, but the judgment behind the decisions that matter is still mine. 🔹 What I bring: ▸ 9+ years building production mobile apps with Clean Architecture, SOLID principles, and testable, scalable codebases. ▸ Experience leading frontend technical direction on complex apps — architecture decisions, code review standards, and mentoring. ▸ Full-stack capability: I can own the mobile app and the backend it talks to (Firebase, Node.js, GCP), so you're not coordinating between multiple contractors. 🔹 AI-Augmented Development ▸ I use AI coding tools (Claude Code, Copilot, Cursor) to speed up boilerplate, prototyping, and test generation — but architecture decisions, code review, and final quality checks are always mine. ▸ This means faster delivery without the usual trade-off: you get senior-level oversight on every line, not just AI output rubber-stamped. ▸ Ideal if you need an MVP fast but don't want to inherit unmaintainable code six months later. 🔹 Frontend ▸ Flutter & Dart, native Android (Java/Kotlin) ▸ State management: Bloc/Cubit, Provider, Riverpod ▸ Offline-first apps: Hive, Drift, Firebase local storage ▸ REST & GraphQL integration, WebSockets, third-party SDKs ▸ CI/CD to App Store & Play Store via Codemagic ▸ In-app purchases, push notifications, deep links, social login, maps/places, camera/QR, Bluetooth, chat, biometrics 🔹 Backend ▸ Firebase: Auth, Firestore, Realtime DB, Hosting, Push ▸ GCP: Cloud Storage, Cloud Functions, Cloud Run, Cloud Scheduler ▸ Node.js/TypeScript: Express, node-cron, Jest ▸ MongoDB/Mongoose, PostgreSQL/Prisma ▸ Auth & security: JWT, OAuth2, RBAC, Firebase Security Rules ▸ Payments (Stripe, PayPal), Docker, Sentry, Kafka, webhooks 🔹 Engineering Practices ▸ Clean Architecture & MVVM depending on project size/timeline ▸ Test-driven development, CI/CD pipelines ▸ Agile workflows: sprint planning, code review, Git-based collaboration If you want code that's still easy to work with a year from now — not just code that works today — let's talk.