10M Downloads · 5.0 Rating

Projects · InPost Success Story

10 million downloads, a 5.0-star delivery app.

How we rebuilt the InPost delivery app into a 5.0-rated product with 10 million downloads — parcel tracking users open daily.

InPost · Case Study

We turned parcel tracking into a daily habit — fast, reliable and genuinely loved.

  • 10MDownloads on both stores
  • 5.0App Store rating held
  • -38%Support tickets after rebuild
  • 99.9%Tracking API uptime

02

Why it worked

Parcel-first thinking.

  • 01

    Tracking in two taps

    Parcel status on open — no logins standing between users and answers.

  • 02

    Offline-proof journeys

    Locker codes cached — courtyards with no signal still collect.

  • 03

    Release trains

    Biweekly updates with staged rollouts — ratings never dipped.

03

App rebuild

Native, both stores.

Swift and Kotlin rebuilds that made tracking instant.

Push-triggered refresh with optimistic states — the app feels alive even on 3G.

  • Native iOS & Android
  • Push-triggered refresh
  • Offline locker codes
  • Widget support
  • Deep-link routing
  • Swift
  • Kotlin
  • Push
  • Widgets
  • REST

04

Tracking platform

Truth at scale.

Event pipelines carrying millions of parcel scans daily.

Idempotent ingestion with carrier adapters — every scan lands exactly once.

  • Event ingestion
  • Carrier adapters
  • Idempotency keys
  • Status normalisation
  • Uptime SLOs
  • Node.js
  • Kafka
  • PostgreSQL
  • Redis
  • Grafana

05

Ratings & growth

Loved on purpose.

Review prompts at delight moments plus ASO that compounds.

Happy-path prompts with unhappy-path support routing — ratings climbed and held at 5.0.

  • Delight-moment prompts
  • Support routing
  • ASO program
  • Screenshot storytelling
  • Release notes users read
  • ASO
  • Prompts
  • Support
  • Screenshots
  • Notes

06

How we deliver

Four phases, demoed every sprint.

  1. 01

    Discover

    Scope, estimate and risks on paper before build.

    2–4 weeks
  2. 02

    Design

    Flows and UI tested with real users.

    Design sprints
  3. 03

    Build

    Weekly increments, QA baked in, demoed live.

    Every sprint
  4. 04

    Scale

    Launch, monitor and improve on a roadmap.

    SLA care

07

Client voices

Partners we delivered with.

Users open us daily now — parcel tracking became a habit, not a chore.

Product OwnerLogistics · Rebuild

Support tickets down 38% while downloads tripled. Quality scales.

Support LeadOperations · Platform

5.0 held through three festive peaks. That is engineering plus discipline.

CTOTechnology · Scale

08

Technologies we use

Boring where it should be, modern where it pays.

  • Swift
  • Kotlin
  • Node.js
  • Kafka
  • PostgreSQL
  • Redis
  • Push
  • Widgets
  • ASO
  • Grafana
  • SLOs
  • REST

09

FAQ

Straight answers, before the first call.

What did the rebuild change?
Native apps replacing a hybrid shell — instant tracking, offline codes and push that arrives.
How was 5.0 achieved?
Delight-moment prompts plus support routing — unhappy users reach help, happy ones review.
Does it work offline?
Locker codes and recent parcels cached — collection works without signal.
Who maintains it now?
Release trains with staged rollouts — runbooks handed to the in-house team.
Does TEKSNAPP work with teams in Hyderabad and Warangal?
Yes — discovery onsite across both cities, demos every sprint.

10

Delivery app case study — Hyderabad & Warangal

Onsite across Telangana.

Lessons for Telangana logistics, from 10 million users.

From Hyderabad courier startups to Warangal transporters going digital — the InPost playbook applies: offline-first tracking, delight-timed reviews and release trains, implemented by teams nearby.

  • Madhapur
  • HITEC City
  • Gachibowli
  • Kondapur
  • Jubilee Hills
  • Begumpet
  • Kukatpally
  • Secunderabad
  • Hanamkonda
  • Kazipet

11

Keep exploring

Where to go next.