SDK maze
The collection of platform-specific SDKs, payment adapters, compliance review processes, performance ceilings, and localization rules that studios re-implement per SuperApp when porting a MiniApp game.
Every SuperApp has its own SDK. Telegram's Mini Apps SDK, WeChat's Mini Games framework, LINE's LIFF, Discord's Embedded App SDK, Meta's Instant Games SDK, STAN's Mini App SDK. Each handles authentication, in-app purchases, share-to-friend, native UI surfaces, and platform notifications differently.
A studio shipping the same game to two platforms re-implements the SDK layer twice. To three platforms, three times. The actual gameplay is small relative to the platform integration work. This is the SDK maze: not a single problem but a class of problems that consistently eats studio engineering time.
Four areas dominate the maze: payments (Stars vs TON vs LINE Pay vs WeChat Pay vs UPI vs Discord IAP vs Meta IAP), compliance (per-platform content review with different rejection categories), performance (4MB to 30MB bundle ceilings depending on platform), and localization (some platforms route language through the URL, some through device locale, some through user-account locale).
Hangar is the automation layer that reduces the SDK maze from per-studio engineering to a per-platform adapter shipped by us.
Related terms.
An app that runs inside a SuperApp without a separate app-store install. Players or users launch it from a chat, a contact, or a channel.
A messaging or social app that has expanded into a multi-purpose platform hosting payments, mini-apps, games, identity, and commerce inside ...
A web app that runs inside Telegram through the Mini Apps WebView API. Players launch it from a bot, a chat, or a channel.
A MiniApp game inside WeChat Mini Programs. Runs on a custom JavaScript engine with native canvas API and a 4MB initial bundle limit.