Case studies

Proof,
not promises.

Two platforms we designed and engineered end to end, shown the way they really run, and Cockpit, a workspace designed for clients to follow delivery. Try that one yourself.

Tornado and Bingo: real screens from the running apps · Cockpit: interactive demo with sample data

Tornado

Every reel is a storefront.

Category
Social commerce
Platforms
iOS · Android · Web (Flutter)
Products
Shopper · Creator Studio · Brands
Services
Product design · App engineering · Platform architecture
Tornado shopper app home: stories, live rooms and a creator post

The challenge

Social commerce usually splits shoppers, creators and brands across disconnected tools. Inventory, commissions and content drift out of sync, and heavily filtered content erodes trust in what actually arrives.

The approach

One Flutter codebase powering three purpose-built apps that share a single live state. A product a brand edits, a creator pins mid-live and a shopper adds to cart is always the same product, in real time.

The result

A complete, tested product across all three apps: shoppable video, live selling, memberships, affiliate sampling and analytics, in a dark frosted-glass design system.

Three apps, one live state

For shoppers

Tornado

  • Home feed with stories, lives, posts and inline shots
  • Shots: vertical video with add-to-cart in the video
  • Live shopping with chat, hearts and a shelf that updates live
  • Messages, friends, sharing and creator memberships
  • Hide or block anyone, and notifications for every order step
For creators

Creator Studio

  • Wallet, tier and 7-day KPIs at a glance
  • Analytics: earnings, funnel, conversion, AOV, top products, cities
  • Create shots and posts, or go live with a product control room
  • Membership tiers with the exact payout per member
  • Affiliate marketplace to request brands' products
For brands

Tornado for Brands

  • Settlements, escrow, sales and creator share on one home screen
  • Orders and returns: accept, pack, ship, approve or contest
  • Product catalogue with price, stock, sizes and media
  • Creator requests with smart sample / discount recommendations
  • Sample dispatch tracking with courier, AWB and due dates
Trust by design

The no-filter policy

Shots, posts and lives publish exactly as captured: no colour filters, beauty effects or AR. Creators confirm it before every publish, and shoppers see an “Unfiltered” badge, so products look the way they'll arrive.

A shot with the Unfiltered badge and a shoppable product card
Money, to the paisa

Membership economics

Every payment is split by a dedicated engine on integer money, so it always balances. A ₹99 membership pays the creator ₹71.85.

GST (inclusive)18% carved out
Payment gateway2% of the charge
Tornado, year 112% of post-GST
Tornado, after 12 months8%, rewarding retention
CreatorThe rest, settled instantly
Membership tiers showing the split and the ₹71.85 the creator receives per member
Built with
  • Flutter
  • Dart
  • Riverpod
  • Escrow engine
  • Commission & subscription engines
  • Integer-paise money
  • Domain + sync tests

Bingo

Your ride, the moment you need it.

Category
Ride hailing
Platforms
iOS · Android · Web (Flutter)
Products
Rider app · Captain app · Operations console
Services
White-label product · Launch · Care
Bingo rider app home with a single Book a ride action
bingo console

The challenge

Launching a ride-hailing business from scratch means two apps, an operations dashboard and a server, each with its own edge cases, before the first rupee of revenue. Riders dislike price surprises and waiting in the dark. Captains lose too much of every fare to commission.

The approach

One Flutter and Dart codebase delivers a rider app, a captain app and a web operations console on a shared design system, backed by a single ride server that enforces every rule. Fixed fares, OTP-verified pickups and swipe-to-confirm controls remove the ambiguity from each step.

The result

A complete, tested platform that launches under an operator's own name, colours and fares on iOS, Android and the web, backed by 21 automated API tests. The screens above are real captures from a live test ride between the apps.

Three products, one ride

For riders

Rider app

  • Book a bike, auto or cab in three taps
  • A fixed fare shown before booking, recalculated on the server
  • Live arrival countdown, captain name, plate and a four-digit ride OTP
  • Share trip and SOS on every in-ride screen
  • Receipt, rating, optional tip and full trip history
For captains

Captain app

  • Go online and accept with one swipe inside a 15-second ring
  • A zero-commission breakdown on every payment
  • Wrong OTPs refused by the server
  • Today's earnings, the week at a glance and instant payout
  • One big action per screen, confirmed with a swipe
For operators

Operations console

  • Revenue, rides, live rides and captains online, against yesterday
  • A live fleet map and an activity feed that refreshes every two seconds
  • Open any ride for its timeline and OTP, or cancel it
  • Suspend a captain or block a rider in one click
  • Fare tables and announcements reach both apps within 10 seconds

One ride, five states

  1. searchingRider books

    Picks a drop, sees fixed fares for bike, auto and cab, and books. A ride OTP is created.

    Rider app
  2. acceptedCaptain accepts

    Nearby captains of that vehicle type see the request with a 15-second ring. The first swipe wins.

    Captain app
  3. arrivedAt the pickup

    The rider watches the countdown and plate. The captain swipes “Arrived”.

    Captain app
  4. ongoingOTP starts the trip

    The rider reads out the code. The server checks it and never shows it to the captain.

    Both apps
  5. completedPaid and rated

    Payment is settled by UPI, wallet or cash, then the rider rates and tips.

    Both apps
Built with
  • Flutter 3.47
  • Dart 3
  • Shared design system
  • Dart REST API
  • SQLite · PostgreSQL
  • Phone OTP sign-in
  • Hashed sessions
  • 21 API tests
The full Bingo case study

Market, audience, deployment and running costs.

Everything an operator needs to decide: how the market is moving from commission to subscription, what riders, captains and operators each want, how HALO takes Bingo from signed proposal to first paid ride, and what the outside services cost to run.

  • Market evaluation
  • Audience research
  • Pain points
  • How it works
  • How to deploy
  • Running costs
Read the full case study →

HALO Cockpit

Full visibility. Every single day.

Category
Client delivery workspace
Format
Web workspace
Views
Overview · Sprints · Demos · Decisions · Files
Built for
Clients and their delivery team

The challenge

Clients often have to wait for a status call to learn what shipped, what is next and what a project has spent. Decisions get buried in email threads, and problems surface late.

The approach

One workspace that shows sprint progress, the next live demo, open decisions, budget and files. Clients see the same view as the delivery team, and every decision is kept on record.

The result

A single place to answer the questions a client asks most: where are we, what do you need from me, and are we on track? Try it below.

Try the interactive demo

Sample data. Nothing you do here is saved, and it doesn't show a real client's project.

halo.cockpit / sample-product Demo
  • Weekly live demoEvery week, on your calendar, in your time zone.
  • One shared viewYou and the team work from the same picture of the project.
  • Decisions on recordEvery choice is logged with its reason. Nothing gets lost.
Your product next

Your product
is next.