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?
- Request the image via
PHImageManagerwith highQualityFormat option. - Obtain CGImage from the response.
- Create a CGImageDestination with JPEG type and quality 0.95.
- 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() Example WorkManager Configuration for Background Upload
WorkManager allows upload even when the app is closed. We specify UNMETERED to avoid mobile data usage. Progress is tracked via setProgress.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:
| Parameter | Core Image (iOS) / ColorMatrix (Android) | GPUImage (iOS) / RenderScript (Android) |
|---|---|---|
| Performance | Sufficient for basic operations, 30% slower for complex filters | 30–50% faster for complex filters |
| Library size | Built into OS, doesn't increase app size | Adds ~5–10 MB to APK/IPA |
| Video support | Requires additional processing, 3x slower | Native support, up to 3x acceleration |
| Recommendation | For simple editors (cropping, adjustments) | For Instagram-like filters and collages |
Contact us for a free consultation on editor selection.
Estimated Timelines and Cost
| Component | Timeline | Cost (USD) |
|---|---|---|
| Basic version (photo selection, cropping, upload, payment) | 5–8 weeks | $15,000 – $25,000 |
| Advanced editor (filters, text, collages) | +3–4 weeks | +$8,000 – $12,000 |
| Integration with printing service | 1–2 weeks | $3,000 – $6,000 |
| Store publishing | 1–2 weeks | $1,500 |
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.







