From HEIC to Print: Building a Mobile Photo Printing App

From HEIC to Print: Building a Mobile Photo Printing App

A user takes a photo on an iPhone and opens a mobile photo printing app. A minute later, they find that the HEIC-format photo isn't accepted by the printing service. The app offers conversion, but after upload, colors are distorted and the image looks blurry when printed. This error results from improper handling of color profiles and compression. Our task is to ensure smooth delivery of the result without technical failures or quality loss. We guarantee that every step—from photo selection to sending to the printing service—is refined to the smallest detail. Over years of working with photo studio chains, we've accumulated experience to avoid typical problems: incorrect color reproduction, resolution errors, and upload failures for large batches.

Without proper conversion, color correction, and large file management, a mobile photo printing app can lose up to 40% of users at the photo upload stage. We build solutions that address these issues at the stack level—from Swift and Kotlin to WorkManager and Core Image.

What Technical Challenges Does a Mobile Photo Printing App Solve?

HEIC Conversion and Color Correction. iPhones shoot in HEIC; most printing services accept JPEG. On-device conversion with sRGB color profile preservation is critical. Our implementation uses CGImageDestination with quality 0.95, ensuring minimal loss.

Resolution Check. Minimum quality for a 10×15 cm print is 1200×900 px at 300 DPI. The app automatically warns if the photo is too small and suggests replacing it.

Editor with Preset Formats. The user crops photos to common formats (10×15, 15×20, 20×30, square) with a fixed aspect ratio. Basic brightness and contrast adjustments are done via Core Image on iOS and ColorMatrix on Android.

Why Is HEIC Conversion So Important?

HEIC uses HEVC compression, reducing file size by 50% compared to JPEG, but requires hardware support. On iOS, conversion is performed via PHImageManager and CGImageDestination. Apple Developer Documentation: Image I/O describes this process. Without this handling, users encounter upload errors or wasted time waiting. Our approach guarantees compatibility with any printing service.

How to Set Up HEIC Conversion on iOS?

1. Request the image via PHImageManager with highQualityFormat option.
2. Obtain CGImage from the response.
3. Create a CGImageDestination with JPEG type and quality 0.95.
4. Save the result to Data. The code below demonstrates this algorithm:

import Photos
import ImageIO

func convertHEICtoJPEG(asset: PHAsset, completion: @escaping (Data?) -> Void) {
    let options = PHImageRequestOptions()
    options.deliveryMode = .highQualityFormat
    options.isNetworkAccessAllowed = true
    options.isSynchronous = false

    PHImageManager.default().requestImage(
        for: asset,
        targetSize: PHImageManagerMaximumSize,
        contentMode: .aspectFit,
        options: options
    ) { image, info in
        guard let cgImage = image?.cgImage else {
            completion(nil)
            return
        }

        let mutableData = NSMutableData()
        guard let destination = CGImageDestinationCreateWithData(
            mutableData, kUTTypeJPEG as CFString, 1, nil
        ) else {
            completion(nil)
            return
        }

        let jpegOptions: [CFString: Any] = [
            kCGImageDestinationLossyCompressionQuality: 0.95,
            kCGImagePropertyColorModel: kCGImagePropertyColorModelRGB
        ]

        CGImageDestinationAddImage(destination, cgImage, jpegOptions as CFDictionary)
        CGImageDestinationFinalize(destination)

        completion(mutableData as Data)
    }
}

How We Do It: Stack and Case Study

From our practice: an app for a regional chain of photo studios. Requirements: photo upload, editor, integration with the printing service's internal API, payment via Stripe.

iOS: Swift 5.9, SwiftUI for UI, Combine for reactive streams, Core Image for image processing. HEIC conversion is performed asynchronously via PHImageManager.

Resolution check:

func checkPrintQuality(image: UIImage, printSizeInches: CGSize) -> PrintQuality {
    let requiredWidth = printSizeInches.width * 300
    let requiredHeight = printSizeInches.height * 300

    return image.size.width >= requiredWidth && image.size.height >= requiredHeight
        ? .good
        : image.size.width >= requiredWidth * 0.7 ? .acceptable : .poor
}

Android: Kotlin, Jetpack Compose, Coil for image loading, Coroutines + Flow for asynchrony. Large batch upload is handled via WorkManager with Wi-Fi-only constraint:

class PhotoUploadWorker(
    context: Context,
    params: WorkerParameters
) : CoroutineWorker(context, params) {

    override suspend fun doWork(): Result {
        val photoIds = inputData.getStringArray("photoIds") ?: return Result.failure()
        val orderId = inputData.getString("orderId") ?: return Result.failure()

        photoIds.forEachIndexed { index, photoId ->
            val photo = photoRepository.getById(photoId)
            val success = uploadPhoto(photo, orderId)

            if (!success) return Result.retry()

            setProgress(workDataOf(
                "uploaded" to index + 1,
                "total" to photoIds.size
            ))
        }

        return Result.success()
    }
}

val constraints = Constraints.Builder()
    .setRequiredNetworkType(NetworkType.UNMETERED)
    .build()

What Is Included in Photo Printing App Development

• Analytics and design: requirements gathering, UI prototyping, mockup approval.
• Development: implementation of server side and client (iOS / Android / cross-platform).
• Integration with printing service: connection to Cewe, Fujifilm, or custom REST API.
• Testing: functional, load, user acceptance (UAT).
• Deployment: publishing to App Store and Google Play, setting up TestFlight and Firebase App Distribution.
• Support: 30-day warranty, post-release maintenance.
• Deliverables: full source code, documentation, API keys, admin panel access, staff training, and 30-day bug fix warranty. Development cost starts from $15,000 depending on complexity.

Which Editor Is Better: Core Image vs GPUImage?

For basic operations (brightness, contrast), built-in Core Image / ColorMatrix suffices and is about 2x faster for simple edits. If Instagram-level filters are needed, we use GPUImage on Android and CIFilter with metal shaders on iOS. Here's a comparison:

Contact us for a free consultation on editor selection.

Estimated Timelines and Cost

Cost is calculated individually, depending on scope and complexity. We provide a free project estimate—reach out to us for a consultation.

Why Choose Us?

Over 5 years building mobile apps in the printing industry. Completed 20+ projects—from small services to federal chains. We guarantee compliance with App Store Review Guidelines (Section 4.2/5.1) and Google Play policies. We provide full documentation and staff training.

Need help with your project? Request a consultation—we'll tell you how to optimize your photo printing app.

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.