Skip to main content↵

Building My First React Native App: A Real-Time Todo App with Convex

As my first real dive into React Native, I wanted to build something that was simple on the surface but let me stretch into concepts I hadn't touched before - real-time data sync, theme handling, and putting together a mobile experience that actually feels good to use. The result is a Todo App powered by React Native, Expo, and Convex. Why This Project Most "first app" tutorials stop at local state and a hardcoded list. I wanted more than that. I wanted to understand what it actually takes to have data update instantly across multiple devices, to support both light and dark mode properly, and to ship something that felt like a small but complete product rather than a demo. What It Does At its core, this is a todo app - but with a few details that make it feel polished: Todos Add, edit, and delete tasks Mark tasks as complete or incomplete A live progress bar that reflects completion status in real time Instant sync across every connected device Settings Task statistics - total, completed, and remaining A dark mode / light mode toggle Notification and auto-sync toggles (UI groundwork for future functionality) A "delete all tasks" option with a confirmation step, so one accidental tap doesn't wipe your list Real-Time Sync Changes propagate instantly through Convex's real-time database Automatic reconnection handling, so the app recovers gracefully if connectivity drops The Tech Stack React Native for the cross-platform mobile UI Expo to speed up development and testing without fighting native build tooling Convex as the real-time backend and database TypeScript throughout What I Learned The biggest unlock on this project was understanding how Convex handles real-time subscriptions. Instead of manually polling or writing socket logic, Convex lets the UI just react to data changes — which completely changed how I thought about state management in a mobile context. Building the theme system also pushed me to think more intentionally about UI consistency, since every component had to look right in both light and dark mode. It's still a simple app on paper a todo list but building it end to end taught me far more than any tutorial could about how real apps are structured, synced, and shipped. This was my first React Native project, and I'm excited to keep building. If you find it useful, a star on the repo is always appreciated.

Building My First React Native App: A Real-Time Todo App with Convex screenshot

Project Specifications

Technologies Used
React NativeTypeScript
CategoryMobile App
TimelineJul 2026

Related Projects

Browse All Projects →
Wallet: Building a Full-Stack Expense Tracker with React Native & Express
Mobile App

Wallet: Building a Full-Stack Expense Tracker with React Native & Express

After my first React Native project, I wanted to push further past a front-end-only app and into something that felt genuinely production-ready. Wallet is the result: a full-stack mobile expense tracker with real authentication, a cloud-hosted database, rate limiting, and a deployment-ready backend behind it. Why This Project A lot of portfolio apps stop at the UI layer pretty screens backed by mock data or local storage. I wanted to build the whole system: an API that handles real users, a database that persists real transactions, and the kind of infrastructure decisions (auth, rate limiting, cloud deployment) that separate a demo from something you could actually ship. Wallet is built to run on both iOS and Android, on simulator or a real device, with a backend that's ready to go live. What It Does Authentication Email-based auth handled through Clerk Six-digit email verification codes for signup Secure signup and login flows, with logout support Wallet Functionality View current balance at a glance Track income and expenses separately Add new transactions Delete transactions, with the balance recalculating automatically Pull-to-refresh, implemented from scratch rather than pulled from a library Mobile Experience Built with React Native and Expo Navigation handled through React Navigation State managed with custom hooks rather than a heavy external library UI tuned to feel native on both Android and iOS Backend & Cloud An Express.js REST API PostgreSQL via Neon for cloud-hosted, serverless-friendly data storage Redis-based rate limiting (via Upstash) to protect the API from abuse Clerk auth middleware and webhooks securing every relevant route An architecture that's ready to deploy, not just run locally The Tech Stack Frontend (Mobile) React Native Expo React Navigation Clerk (Authentication) Axios TypeScript / JavaScript Backend Node.js Express.js PostgreSQL (Neon) Redis (Upstash) Clerk Webhooks & Auth Middleware Rate Limiting What I Learned This project forced me to think like a backend engineer as much as a mobile developer. Wiring up Clerk's auth middleware and webhooks meant understanding how tokens flow between the client, the API, and a third-party auth provider not just calling a login function and trusting it works. Adding Redis-based rate limiting was my first real exposure to protecting an API against abuse rather than just handling the happy path. On the mobile side, implementing pull-to-refresh from scratch instead of reaching for a pre-built component taught me more about React Native's gesture and scroll handling than any tutorial. And keeping the balance in sync every time a transaction was added or deleted meant being deliberate about where state lived and how it updated, rather than letting the UI drift out of sync with the database. Overall, Wallet felt like the first project where I was building a system, not just a screen and that shift in thinking is something I'll carry into everything I build next. Wallet is a full-stack, production-oriented project authentication, database, rate limiting, and deployment-ready architecture, all wired up end to end.

React NativeTypeScriptJavaScriptNode.jsExpress.js
Kavi - AI Shopping Agent
AI Agent

Kavi - AI Shopping Agent

Overview Kavi is a conversational AI shopping assistant built for the Kapruka Agent Challenge, an open competition where 700+ developers submitted over 200 live, working AI agents. Kavi helps users discover products, get gift recommendations, and complete checkout entirely through natural language — in English, Sinhala, or Tamil. The goal of the challenge was simple to state and hard to execute: build a real, live agent on top of Kapruka's Model Context Protocol (MCP) server, not a prototype or mockup. Kavi is the result — a full end-to-end shopping experience powered by conversational AI. The Problem Traditional e-commerce search relies on filters, dropdowns, and category trees that assume the shopper already knows what they're looking for. Gift shopping in particular often starts with a vague idea ("something for my mom's birthday") rather than a specific product. Kavi was designed to close that gap — letting users describe what they want in plain language and have the agent handle search, recommendation, and checkout from there. What It Does Conversational shopping assistant Powered by Google Gemini, Kavi understands natural-language requests, recommends gifts based on context, searches the product catalog, and walks users through checkout — all through chat. Multi-lingual by design Full UI and conversational support in English, Sinhala (සිංහල), and Tamil (தமிழ்). Language context is dynamically mapped into both the Gemini system instructions and the frontend, so the experience is consistent regardless of language. Live, real-time commerce Product search by keyword, category, price range, and availability, rendered through custom cards, detail drawers, and carousels. Cart management updates totals in real time and enforces sensible limits. Checkout can be completed conversationally or through a guided form, capturing sender, recipient, and delivery details. Orders can be tracked by order number after purchase. Personalization that persists User accounts are backed by Supabase Auth (magic link and Google OAuth), with saved delivery details, a persistent list of frequent recipients that auto-syncs during gifting checkouts, and reminders for birthdays and anniversaries that surface tailored gift suggestions before the date arrives. Grounded in real data Every product, category, and location shown to users is pulled live from the Kapruka Model Context Protocol (MCP) server — not cached or mocked data. Tech Stack AI / LLM: Google Gemini Data layer: Kapruka Model Context Protocol (MCP) server Auth & backend: Supabase (magic link + Google OAuth) Frontend: Custom UI with multi-lingual support (English, Sinhala, Tamil) Outcome Kavi was one of 200+ live agents evaluated by judges in the Kapruka Agent Challenge, out of 700+ developers who entered. It didn't place in the Top 20, but it stands as a fully working, deployed product — handling real product search, multi-lingual conversation, checkout, and personalization end to end. What I Learned Building Kavi meant designing a conversational interface that had to work reliably in three languages, wiring a live MCP integration for real-time data rather than static content, and thinking through the full shopping journey — discovery, recommendation, cart, checkout, and post-purchase tracking — rather than a single isolated feature. It was as much a lesson in product thinking as it was in AI engineering.

ReactKapruka MCPSupabase