Mobile App Development for Crypto Launchpad (IDO/IEO)

We build mobile launchpads turnkey — from scratch to publication in App Store and Google Play. Development complies with App Store Review Guidelines (Section 4.2, 5.1). A crypto launchpad (IDO or IEO) is a platform where users participate in token sales. In the mobile app we implement: a project showcase, participation mechanism with USDT/BNB investment, tier access system, and vesting claim after TGE.

Moving IDO to a mobile app brings three key advantages: retention through push notifications (1.3–1.4x conversion increase), convenient transaction signing via WalletConnect or built-in wallet, and a unique UX with a token portfolio dashboard and participation history. We’ll assess your project and propose a solution within 1–2 days.

How Is the Tier System Structured?

Most launchpads use a tier system: the more native tokens a user holds (or the longer they are staked), the higher the tier—and the larger the IDO allocation. The tier is calculated based on balance + staking at the snapshot block. The logic resides on the smart contract side or off-chain with Merkle-proof.

// iOS — check user tier
struct UserTier {
    let level: Int        // 0–4
    let name: String      // Bronze / Silver / Gold / Platinum / Diamond
    let stakedAmount: BigDecimal
    let allocationMultiplier: Decimal
}

func getUserTier(address: EthereumAddress) async throws -> UserTier {
    let staked = try await stakingContract.balanceOf(account: address)
    return TierCalculator.calculateTier(stakedAmount: staked)
}

UI: profile screen with current tier, next tier, and amount to add. Progress bar "to next tier". Example tier table:

IDO Project Screen

The individual IDO page is the core of the launchpad. Structure:

• Header: logo, name, network, token contract
• Timer: time to start/end/claim
• Progress: raised X of Y USDT (progress bar)
• Token price, total supply, vesting schedule
• "Participate" button (only during whitelisting/sale period)
• Tabs: About / Tokenomics / Team / Whitepaper

Sale progress is real-time via TokensPurchased(buyer, amount) event or polling every 30 seconds.

How to Participate in an IDO

1. Whitelist registration. Sign a message (EIP-712) or send a transaction registerForSale(projectId).
2. Approval. After verification (manual or automatic), the user receives an allocation.
3. Approve token. The user calls approve to allow the smart contract to spend USDT/BNB.
4. Purchase. The transaction buy(amount) is sent. The user sees the estimated token amount and vesting schedule.
5. Track status. The project screen shows sale progress and time until claim start.

// Android — participate in IDO via smart contract
suspend fun participateInIdo(
    saleContract: String,
    paymentToken: String,   // USDT address
    paymentAmount: BigInteger
): String {
    // Step 1: approve USDT
    val approveTx = approveERC20(token = paymentToken, spender = saleContract, amount = paymentAmount)
    waitForReceipt(approveTx)

    // Step 2: participation
    val buyFunction = Function("buy", listOf(Uint256(paymentAmount)), emptyList())
    return sendTransaction(to = saleContract, data = FunctionEncoder.encode(buyFunction))
}

Why Is Vesting Important?

Vesting prevents immediate token dumping. After TGE (Token Generation Event), tokens unlock according to a schedule. The smart contract stores a vestingSchedule for each participant.

// iOS — calculate available claim
func availableToClaim(beneficiary: EthereumAddress) async throws -> BigUInt {
    let schedule = try await vestingContract.getVestingSchedule(address: beneficiary)
    let elapsed = BigUInt(Date().timeIntervalSince1970) - schedule.startTime
    let vested = min(schedule.totalAmount, schedule.totalAmount * elapsed / schedule.duration)
    return vested - schedule.released
}

Claim screen: vesting progress (visual timeline), unlocked today, total locked, "Claim" button with amount.

Staking the Native Token

Staking is the foundation of the tier system. The user deposits tokens into a staking contract (stake(amount)) and receives a tier. The lock period may be fixed or flexible with a reduced multiplier.

// Android — staking with lock period
data class StakingOption(
    val lockDays: Int,
    val tierMultiplier: Double,  // 1.0x / 1.5x / 2.0x
    val earlyUnstakePenalty: Int // % fee for early withdrawal
)

Display on unstake: penalty and days remaining in lock.

Push Notifications and Reminders

• Whitelist start for favorite projects
• Application approved/rejected
• IDO starts in 1 hour
• Participation transaction confirmed
• Token unlock via vesting (claim available)

Users subscribe to notifications for specific projects—not a broadcast to all.

What Is Included in Development

• Design mockups (Figma) and prototyping
• iOS (Swift 5.9+, SwiftUI) and Android (Kotlin, Jetpack Compose) development
• Smart contract integration (EVM, Solana)
• Backend (Node.js/Python) with GraphQL or REST API
• Staking and tier distribution system
• Vesting mechanism with custom schedules
• Push notifications (APNs/FCM)
• WalletConnect integration and store deployment
• Audit and testing (unit, UI, integration)
• Technical documentation and team training

Development Timelines

MVP launchpad: 6–8 weeks. With KYC integration, multi-chain support (EVM + Solana), referral program — 3 months.

We have 5+ years of experience in mobile development and over 10 successfully launched crypto projects. We guarantee quality, timelines, and App Store review compliance. Contact us for a free assessment of your project — we'll calculate cost within 2 days.

Get a consultation on your project — we'll estimate timeline and cost within 2 days.

Payments in Mobile Apps: In-App Purchase, StoreKit 2, Google Billing, Stripe, RevenueCat

In every monetization project, we balance App Store and Google Play policies, PCI DSS requirements, and purchase verification logic on the backend. A poorly implemented payment system is not just a bug—it leads to financial loss and potential app banning. Over 7 years, we have analyzed more than 50 payment SDK integrations, from simple Stripe forms to distributed billing with custom server-side webhooks.

In-App Purchase: Two Platforms, Two Different APIs

If your app sells digital content or subscriptions, Apple and Google require you to use their payment systems. This is non-negotiable: violating App Store rule 3.1.1 or Google Play Developer Policy results in app removal. Physical goods and offline services are a different story.

StoreKit 2 (iOS 15+)

StoreKit 2 is a complete overhaul of the original StoreKit with async/await API. Product.products(for:), product.purchase(), Transaction.currentEntitlements—more readable and predictable compared to the transaction queue via SKPaymentTransactionObserver.

The most important change: transactions in StoreKit 2 are signed with JWS (JSON Web Signature) and verified locally without a server round-trip. Transaction.verificationResult returns .verified(Transaction) or .unverified(Transaction, VerificationError). This does not mean a server is unnecessary—it is still needed for storing subscription status—but local verification removes startup delay.

StoreKit.AppTransaction verifies the actual app download from the App Store. Required for paid downloads or non-renewing purchases.

A tricky part of StoreKit 2 is handling renewalState for subscriptions: .subscribed, .expired, .inBillingRetryPeriod, .inGracePeriod, .revoked. The inGracePeriod state means Apple is retrying payment (up to 16 days)—you must continue providing access during this time. Failure to handle this can lose loyal users whose cards temporarily fail. Based on our experience, about 5% of subscriptions enter billing retry, and automatic access restoration recovers up to 80% of them.

Google Play Billing Library (v6+)

Google Billing is more complex than StoreKit in terms of scenario handling. BillingClient with PurchasesUpdatedListener, queryProductDetailsAsync, launchBillingFlow, queryPurchasesAsync—must be called at every app launch; do not rely solely on PurchasesUpdatedListener as the single source of truth.

Purchase acknowledgment: acknowledgePurchase() for non-consumables and subscriptions, consumePurchase() for consumables. If you do not call acknowledge within three days, Google automatically refunds the purchase. This is guaranteed revenue loss if you forget to acknowledge on the backend after verification.

ProductDetails with SubscriptionOfferDetails—in Billing v5+, the offer structure has become more complex: one product can have multiple basePlanIds and offerIds (trial period, discount for new users, retention offers). BillingFlowParams.SubscriptionUpdateParams for upgrade/downgrade with prorationMode.

Why Is Server-Side Verification Mandatory?

Never trust only client-side code when unlocking paid content. Client-side verification can be bypassed by modifying the app.

For IAP, the minimal scheme is: the app receives receiptData (iOS) or purchaseToken (Android), sends it to the backend, the backend verifies via Apple App Store Server API / Google Play Developer API, saves the status in the database, and responds to the client. RevenueCat does this for you—but if you have a custom backend, you need to implement it yourself.

Webhooks are more important than they seem. Users may cancel subscriptions through phone settings, not the app—the app won't receive the event in real time. Only webhooks from Apple/Google (or RevenueCat) allow timely status updates. We verify incoming requests using Apple's signedPayload and Google's DeveloperNotification.

How Does RevenueCat Simplify Integration?

Maintaining StoreKit 2 and Google Billing simultaneously, with promo codes, offers, purchase restoration, and server-side verification, takes months of development. RevenueCat handles most of this layer.

RevenueCat is not just a payment SDK. It offers:

• A unified API for iOS and Android (and Stripe for web)
• Server-side verification and subscription status storage
• Webhooks for events (purchase, renewal, cancellation, billing issue)
• Analytics for cohorts, MRR, churn
• A/B testing of offers via Experiments

Purchases.configure(withAPIKey:) at startup, Purchases.shared.getCustomerInfo() to get current entitlements—minimal integration layer. Purchases.shared.purchase(package:) instead of directly calling StoreKit/Billing.

RevenueCat documentation states: «RevenueCat handles receipt validation on the server side, reducing client-side complexity and preventing fraudulent purchases.»

Limitations of RevenueCat: it is paid (free up to $2.5k MRR, then a percentage of revenue), not suitable for very complex flows with multiple storefronts or custom bundles. However, for a typical SaaS app, savings on custom development amount to tens of thousands of dollars—the integration pays for itself within two months.

Stripe in Mobile Apps

Stripe is used for physical goods, services, and B2B payments where IAP is not required by platform policy.

Stripe iOS SDK and Android SDK—PaymentSheet for ready-made payment UI, PaymentSheetFlowController for custom UI with saved cards. Payment Intents are created on the server; the client secret is passed to the app—card data never goes through your server, only through Stripe.

Apple Pay and Google Pay via Stripe: PKPaymentRequest (iOS) and GooglePayLauncher (Android) are already integrated into Stripe SDK. Apple Pay conversion rates are 1.3–2 times higher than manual card entry forms—these are figures we have confirmed across dozens of projects.

Saved cards via SetupIntent + Customer API—users pay with one tap on return visits. Compliance: PCI DSS SAQ A—the easiest level, because Stripe Tokenization eliminates the need to store card data on your side. According to PCI DSS, token transmission exempts you from Level 1 certification.

3DS2 (Strong Customer Authentication) is mandatory for payments in the EU under PSD2. Stripe handles it automatically via PaymentIntent.confirmPayment, but you need to correctly handle the .requiresAction status and return the user to the appropriate screen after authentication.

What Is Included in the Work (Deliverables)

Process and Timeline

We start by clarifying the business model: subscriptions, one-time purchases, consumables, freemium. The architecture depends on this. Testing IAP requires Sandbox accounts (Apple) and License Testers (Google)—this is a separate environment setup.

Apple's Sandbox behaves differently from production: subscriptions renew every 5 minutes instead of monthly, inGracePeriod works differently. It is essential to test scenarios: trial expiration, cancellation, billing retry, refund.

The cost is calculated individually based on the set of tools and complexity of server-side logic. On average, we fit within a budget for a typical integration, but the savings from preventing errors and churn offset this investment within a few months.

Get a consultation for your project—contact us. We will help you choose the optimal payment architecture that passes store reviews and does not break under peak loads.