Case Study · Mobile only · Telecom

Pocket eSIM
Buy data. Install. Land. Roam.

Prepaid eSIM for 160–200+ countries. Not a website with a QR PDF. Native iOS and Android: pick a plan, pay in-app (no subscription), install via QR, in-app, or SM-DP+ + activation code.

What shipped: native apps (Play: app.pocketesim.com, App Store: Pocket eSim: Travel & Internet). Node.js API for catalog, orders, and eSIM profiles. Integration with carrier SM-DP+ (GSMA SGP.22). Keep the primary SIM for calls; Pocket eSIM is data.

iOS 15.1+ Android SM-DP+ · eUICC
What we built Technology Play Store
Traveler activating an eSIM on a phone in an airport
QR / LPA
200+ countries
Pay as you go
NRT Wi-Fi · 5GB Japan plan
Install before the lounge. Roam on landing.
Play + App Store
iOS Native · App Store
Android Native · Play Store
SM-DP+ GSMA eSIM install
Node.js Orders & profiles
What we shipped

Mobile only. The eUICC is the product.

No ops web console in this case study. If install fails at immigration Wi-Fi, the app failed.

iOS

Add eSIM from the app, QR, or Settings → Cellular → SM-DP+ address + activation code. iOS 15.1+.

Shipped

Android

SIM manager / scan carrier QR. Same order object.

Shipped

Support path

WhatsApp/email from the stores. Order id is in PostgreSQL, not a screenshot.

Shipped
The problem

Airport kiosk SIMs are the competitor.

Before eSIM, Lena queued for a physical SIM, lost her home number for a week, or paid carrier roaming. QR PDFs in email failed because the phone could not scan itself.

  • QR on the same phoneYou cannot scan a QR that is on the device you are installing.
  • Roaming surpriseHome carrier bill after “just maps.”
  • No top-up objectSecond purchase was a new email thread.
One real run

Lena · IST → NRT

  1. Night before — Buys 5GB Japan in iOS IAP. Pay-as-you-go, not a sub.
  2. Lounge Wi-Fi — In-app install (no second screen). Profile hits the eUICC.
  3. Landing — Data roaming on Pocket eSIM. Primary SIM still for WhatsApp calls if she wants.
  4. Day 4 — Top-up in the same order family. Support can see the ICCID.
Topic by topic

Telecom work, point to point

01 · Catalog

Plans as SKUs

Before

A blog of “we sell eSIM.”

After

Country packages, GB, validity. Store IAP.

02 · Pay

No subscription

Before

Hidden renewals.

After

Play/App IAP. Pay-as-you-go as the listing says.

03 · Install

LPA / QR / SM-DP+

Before

Email PDF only.

After

In-app, QR, or manual SM-DP+ + code.

04 · Dual SIM

Keep the number

Before

Swap plastic, lose OTP SMS.

After

Data on Pocket eSIM, voice on primary.

05 · Abroad

Wi-Fi first

Before

Must be home to activate.

After

Activate on airport Wi-Fi.

06 · Support

Order is data

Before

“I bought something.”

After

Order id, ICCID, install state.

Technology (from the live product)

Native iOS & Android. SM-DP+ and Node.js.

Taken from the Play listing and App Store page: prepaid eSIM, QR / in-app / manual SM-DP+, 200+ countries, IAP not subscriptions, 24/7 support. We do not fake a carrier core — we orchestrate GSMA download onto the eUICC.

Source: Play Store (app.pocketesim.com) and App Store (id6476932559); pocketesim.com install guides (QR and SM-DP+).

iOS Android Node.js PostgreSQL GSMA SGP.22 SM-DP+ Store IAP
Native iOS & Android

Catalog, purchase, install instructions, usage. No WebView checkout as the only path.

SM-DP+ / LPA

Activation code + SM-DP+ address, QR, or carrier in-app install.

Node.js API

Plans, orders, profile lifecycle, support lookup.

PostgreSQL

Users, IAP receipts, ICCIDs, top-ups.

Outcomes

What changed after go-live

Connected before immigration

Install on lounge Wi-Fi.

No roaming shock

Prepaid GB. Primary number stays.

Support has an ICCID

Top-up is not a new mystery.

Build yours

Need travel eSIM done properly?

Native iOS/Android, SM-DP+, Node.js orders — the Pocket eSIM shape.

Start a conversation Back to portfolio