CodeLamda Technologies
HomeServicesWorkAboutCareerContact
Book a call
CodeLamda Technologies

Transforming ideas into scalable digital products. We help startups and businesses build MVPs, AI solutions, and modern applications with speed, quality, and innovation.

Quick Links

  • Home
  • Services
  • Portfolio
  • Blog
  • About
  • Contact

Our Services

  • MVP Development
  • AI Development
  • Web Development
  • Vibe Code Audit
  • CleverTap Integration

Locations

  • USA Software Development
  • UK Software Development
  • UAE / Dubai Software Development
  • Australia Software Development
  • All locations

Contact Us

7th Floor, APMC, Krushi Bazaar,
704 Sahara Darwaja, Begampura,
Surat, Gujarat 395003

contact@codelamda.com
+91 99099 80048

© 2026 Codelamda Technologies Pvt. Ltd. All rights reserved.

Privacy Policy•Terms of Service
  1. Home
  2. /
  3. Portfolio
  4. /
  5. Tapri.AI
Consumer Social / Gig Economy · Case study

India's #1 Community App for Gig Workers

Tapri.AI is a social community app exclusively for India's delivery riders and gig workers — Swiggy, Zomato, Zepto, Blinkit. Location-tagged feed, local rider groups, real-time traffic + police-check alerts, and rider-made reels. Built Hindi-first so riders actually use it on the road.

Ongoing20+ members2024India (Mumbai, Bengaluru, Delhi and expanding)
Visit website
Tapri.AI hero image
Used
Impact
Ongoing
Duration
20+ members
Team
2024
Launched
The challenge

What we set out to solve

Gig riders earn in silos — WhatsApp groups fragment, platform apps don't share rider intel, and critical road info (checkpoints, demand surges, outages) reaches riders too late.

The solution

How we built it

A mobile-first community layer: location-tagged posts, reels, and rider groups; push alerts for local demand + traffic; direct messaging; platform-agnostic earning strategy sharing.

Technical architecture

Location-aware social backend with real-time feeds and media pipeline

Tapri.AI is a Hindi-first social network for delivery riders, combining a location-tagged feed, rider groups, reels, direct messaging and push alerts for traffic and demand. A React Native app talks to a modular Node.js backend on AWS, with PostgreSQL as the system of record, Redis for feed fan-out and presence, and Firebase for push notifications; a Next.js site handles the public web and blog.

Isometric diagram of rider phones connecting through an API gateway to a cluster of Node.js services, a PostgreSQL database and Redis cache, a media processing pipeline with object storage, and a push notification block.
Isometric diagram of rider phones connecting through an API gateway to a cluster of Node.js services, a PostgreSQL database and Redis cache, a media processing pipeline with object storage, and a push notification block.

Clients

Riders use a React Native app built Hindi-first for one-handed use on the road; the public web and blog run on Next.js.

  • React Native rider app
  • Next.js marketing & blog site
  • Hindi + English localisation

API & real-time edge

An API gateway terminates auth and rate limits, while a WebSocket layer streams feed updates, chat and live alerts.

  • REST API gateway
  • WebSocket gateway for chat & feed
  • JWT auth middleware
  • Rate limiting

Core services

Node.js services are split by domain so feed ranking, messaging and alerts can scale independently.

  • Feed & posts service
  • Groups & community service
  • Direct messaging service
  • Alerts & demand signals
  • Job-portal & referral service

Data

PostgreSQL stores users, posts, groups and geotags; Redis backs timelines, presence, counters and pub/sub for real-time delivery.

  • PostgreSQL with geospatial indexes
  • Redis timelines & pub/sub
  • Object storage for media
  • Search & hashtag index

Media & notifications

Reels and photos are uploaded directly to object storage, transcoded asynchronously, and served via CDN; Firebase delivers push alerts.

  • Direct-to-storage uploads
  • Video transcoding workers
  • CDN media delivery
  • Firebase Cloud Messaging
  • Content moderation queue

Infrastructure & delivery

Runs on AWS with containerised services, background workers and CI/CD, sized for spiky evening delivery peaks.

  • AWS containers & autoscaling
  • Background job workers
  • CI/CD with staged rollouts
  • Logging & crash reporting
Request lifecycle
  1. 01

    A rider opens the app; the gateway validates the JWT and the feed service returns a timeline from Redis keyed to the rider's city.

  2. 02

    The rider records a reel; the app uploads it straight to object storage using a presigned URL and posts the metadata to the API.

  3. 03

    A transcoding worker generates mobile-friendly renditions and thumbnails, then marks the post ready for the feed.

  4. 04

    The feed service fans the post out to followers and nearby riders via Redis, and WebSocket clients receive it live.

  5. 05

    A rider posts a police-check or traffic alert tagged to a location; the alerts service notifies riders in that radius via Firebase push.

  6. 06

    Riders discuss it in a local group or by direct message, with messages persisted in PostgreSQL and delivered over WebSockets.

Key decisions

Redis-backed timelines over query-time feeds

Riders refresh constantly between orders on weak networks, so precomputed per-city timelines in Redis give instant loads while PostgreSQL remains the durable record.

Direct-to-storage media uploads

Routing reels through API servers would saturate them; presigned uploads to object storage with async transcoding keep the API thin and uploads resilient.

Firebase for push, custom backend for everything else

Firebase Cloud Messaging solved device tokens and delivery across Android fleets cheaply, while core social data stayed in PostgreSQL for ownership and complex queries.

Geospatial tagging as a first-class concept

Hyper-local road intel is the product's edge, so every post and alert carries coordinates indexed in PostgreSQL, enabling radius queries for feeds and notifications.

Security & compliance
  • Phone-based sign-in with JWT access tokens and refresh rotation; no credit card or payment data collected.
  • Location data stored at post level only and coarsened for public display to protect rider privacy.
  • Media uploads use short-lived presigned URLs with size and type validation before transcoding.
  • Content reporting and a moderation queue to remove abusive posts and protect a vulnerable workforce.
  • Rate limiting and abuse detection at the gateway against spam and scraping of rider intel.
Tech stack

Built with the right tools

React Native
React Native
Node.js
Node.js
PostgreSQL
PostgreSQL
Redis
Redis
AWS
AWS
Firebase
Firebase
Next.js
Next.js
“CodeLamda shipped Tapri as a production-grade social app — reels, real-time feed, push alerts, in twelve weeks. Hindi-first UX for riders who earn on the road, exactly how we briefed it.”
GR
Gaurav Rajawat
Founder, Tapri.AI
More case studies

Keep exploring our work

View all
BritBox case study
OTTOngoing

BritBox

BritBox – Mobile Streaming Engineering Case Study

Maritime Optima case study
SaaSOngoing

Maritime Optima

Maritime Optima – Ship & Trade Intelligence Platform

BillBxa AI case study
FinTechOngoing

BillBxa AI

BillBxa – AI Bill Payment Automation

Your turn

Have a project like this?

We ship MVPs, AI agents, and production systems in 8 weeks. Bring the rough spec — we'll scope the build inside a week with a fixed timeline and quote.

50+
MVPs shipped
8 wks
Avg. delivery
$20M+
Raised by clients
30 days
Post-launch support
30-minute callBook a discovery callPrefer emailSend us a briefBack to the full portfolio