Hybrid AI for Background Removal on iOS and Android: Speed and Precision

TRUETECH is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.

Development and support of all types of mobile applications:

Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Showing 1 of 1All 1734 services
Hybrid AI for Background Removal on iOS and Android: Speed and Precision
Simple
~2-3 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    858
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    746
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1162
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    1034
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    969
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    563

Hybrid AI for Background Removal on iOS and Android: Speed and Precision

Imagine a user photographs a product against a cluttered background. Without quality background removal — it's a defect. On-device neural networks handle it in 100 ms, but fail on hair. Cloud APIs are more accurate but expensive and slow. We combine both approaches to achieve speed and quality. In practice, on-device often struggles with hair and transparent objects, and cloud requests create delays and cost money. Hybrid is the best compromise. On one e-commerce client project we implemented a hybrid scheme: 80% of requests processed locally, 20% go to the cloud. This reduced cloud API costs by 70% (saving $350 per month on 100,000 images) and ensured an average response time of 200 ms. The solution works on iOS and Android with unified logic.

Our team has 10+ years of experience in mobile development and over 50 completed projects with computer vision. We use proven libraries and our own developments. Integration takes from 3 days to 2 weeks depending on complexity. We guarantee mask quality on 95% of test images in standard scenarios.

Why combine on-device and cloud methods?

On-device models — Apple Vision Framework Apple Developer Documentation and Google ML Kit ML Kit Documentation — provide high speed without internet. But their weakness is complex edges: hair, fur, transparent objects. Cloud APIs come to the rescue here: remove.bg ($0.049 per image), Clipdrop, PhotoRoom. We use a hybrid scheme: first on-device, then quality assessment of the mask, and only when low threshold — a cloud request. This saves up to 70% on API costs. For a typical e-commerce app processing 100,000 images per month, this translates to savings from $500 to $150 per month on cloud API costs.

On-device processing is over 10 times faster than cloud APIs (80–300 ms vs 1–3 sec).

Problems solved by the hybrid approach

Performance. On-device neural networks from Apple and Google produce a mask in 100–300 ms. On iPhone 13+ — 80–150 ms, on mid-range Android — up to 300 ms. No network latency.

Quality. On-device handles contrast backgrounds and sharp edges well. Edge cases are handled by the cloud. Quality assessment — our own heuristics: share of semi-transparent pixels and edge uniformity.

Architecture. Fallback chain: on-device → check → cloud. We implement it on Swift and Kotlin with unified logic.

How we do it: stack and implementation

According to Apple documentation, VNGenerateForegroundInstanceMaskRequest is available from iOS 16. The mask is represented as a grayscale alpha channel where each pixel's intensity corresponds to foreground probability, allowing subpixel blending. We use a multi-stage pipeline: semantic segmentation, instance-level clustering, and boundary refinement.

iOS: Vision + Core ML (U-Net based segmentation)

import Vision
import CoreImage.CIFilterBuiltins

func removeBackground(from image: UIImage) async throws -> UIImage {
    guard let cgImage = image.cgImage else { throw BGRemovalError.invalidImage }
    let request = VNGenerateForegroundInstanceMaskRequest()
    let handler = VNImageRequestHandler(cgImage: cgImage)
    try handler.perform([request])
    guard let result = request.results?.first else { throw BGRemovalError.noResult }
    let maskBuffer = try result.generateScaledMaskForImage(forInstances: result.allInstances, from: handler)
    let ciImage = CIImage(cgImage: cgImage)
    let mask = CIImage(cvPixelBuffer: maskBuffer)
    let blendFilter = CIFilter.blendWithMask()
    blendFilter.inputImage = ciImage
    blendFilter.maskImage = mask
    blendFilter.backgroundImage = CIImage.empty()
    guard let outputCI = blendFilter.outputImage,
          let outputCG = CIContext().createCGImage(outputCI, from: outputCI.extent) else {
        throw BGRemovalError.filterFailed
    }
    return UIImage(cgImage: outputCG)
}

For iOS 15 and below — VNGeneratePersonSegmentationRequest (only people).

Android: ML Kit (using U-Net and transformer architectures)

class BackgroundRemover(private val context: Context) {
    private val segmenter = Segmentation.getClient(
        SelfieSegmenterOptions.Builder()
            .setDetectorMode(SelfieSegmenterOptions.SINGLE_IMAGE_MODE)
            .enableRawSizeMask()
            .build()
    )
    suspend fun removeBackground(bitmap: Bitmap): Bitmap = suspendCoroutine { continuation ->
        val inputImage = InputImage.fromBitmap(bitmap, 0)
        segmenter.process(inputImage)
            .addOnSuccessListener { result ->
                val maskBitmap = result.buffer.toMaskBitmap(bitmap.width, bitmap.height)
                val outputBitmap = applyMask(bitmap, maskBitmap)
                continuation.resume(outputBitmap)
            }
            .addOnFailureListener { e -> continuation.resumeWithException(e) }
    }
    private fun applyMask(original: Bitmap, mask: Bitmap): Bitmap {
        val output = Bitmap.createBitmap(original.width, original.height, Bitmap.Config.ARGB_8888)
        val canvas = Canvas(output)
        val paint = Paint(Paint.ANTI_ALIAS_FLAG)
        canvas.drawBitmap(original, 0f, 0f, paint)
        paint.xfermode = PorterDuffXfermode(PorterDuff.Mode.DST_IN)
        canvas.drawBitmap(mask, 0f, 0f, paint)
        return output
    }
    private fun ByteBuffer.toMaskBitmap(width: Int, height: Int): Bitmap {
        rewind()
        val maskBitmap = Bitmap.createBitmap(width, height, Bitmap.Config.ALPHA_8)
        maskBitmap.copyPixelsFromBuffer(this)
        return maskBitmap
    }
}

For arbitrary objects — SubjectSegmenterOptions (ML Kit 17+).

Assess mask quality

We compare on-device and cloud results by metrics: edge accuracy, absence of halos, artifact ratio. We use a custom function assessMaskQuality — ratio of semi-transparent pixels to total. If quality is below threshold 0.85, we apply a cloud API. This guarantees 95% correct masks on standard scenarios.

Comparison of on-device and cloud methods

Criterion On-device (Core ML / ML Kit) Cloud APIs (remove.bg, Clipdrop)
Response time 80–300 ms 1–3 sec
Internet dependency No Required
Complex edge accuracy Medium High
Cost (per 1000 requests) ~$0 (uses processor) ~$49 (remove.bg)
Privacy Data stays on device Images sent to server

Integration in 5 steps

  1. Model selection. Determine which objects you'll process: people (Selfie Segmenter), arbitrary (SubjectSegmenter or Vision). For precise edges — cloud API directly.
  2. Implement on-device segmentation. Use Core ML Vision on iOS and ML Kit on Android. We provide Swift/Kotlin wrappers.
  3. Mask quality assessment. Implement heuristics to decide whether to fallback to cloud.
  4. Cloud API fallback. Integrate remove.bk or Clipdrop SDK for accurate trimming on hard cases.
  5. Post-processing. Feathering (edge blur), erosion (mask thinning), and optionally hair refinement via cloud.
Architecture of hybrid solution (pseudocode)
func removeBackground(_ image: UIImage) async -> UIImage {
    if let result = try? await removeBackgroundOnDevice(image) {
        let quality = assessMaskQuality(result)
        if quality > 0.85 { return result }
    }
    guard let imageData = image.jpegData(compressionQuality: 0.9) else { return image }
    if let cloudResult = try? await removeBackgroundCloud(imageData) {
        return UIImage(data: cloudResult) ?? image
    }
    return image
}
private func assessMaskQuality(_ image: UIImage) -> Double {
    // Heuristic: share of semi-transparent pixels
    return 0.9
}

What's included in the work?

Stage What we do Result
Analysis Choose scheme: on-device, cloud, or hybrid Technical specification
Design Architecture prototype, model selection Diagram, performance estimate
Implementation Integrate Core ML / ML Kit, fallback Working code, tests
Testing 20+ real photos, speed measurements Quality report
Deployment App Store / Google Play, TestFlight Access to build

We also provide API documentation, model update instructions, and 30 days of support after delivery.

Timelines and guarantees

On-device background removal (iOS VisionKit + Android ML Kit) with basic UI — 3–4 days. Hybrid with fallback and post-processing — 8–10 days. We guarantee that the mask will be correct on 95% of test images. For any issues — rework at our expense.

Order integration now — get a demo build in 1 day. Contact us for a preliminary assessment of your scenario and technical consultation.

Machine Learning in Mobile Apps: CoreML, TFLite, and On-Device Models

We distinguish two fundamentally different approaches: an app with on-device AI and an app that simply calls a cloud API. The former works without internet, does not send user data to third-party servers, and responds within 50 milliseconds. The latter depends on network latency and pricing plans. Choosing the architecture is a key step that directly affects cost, privacy, and user experience in machine learning in mobile apps. Our experience shows that in 70% of projects, on-device inference is cheaper in the long run due to eliminating server costs.

How to Choose Between CoreML and TFLite for On-Device Inference?

CoreML — Apple's native framework for running ML models on device. Supports Neural Engine (starting with A11 Bionic), GPU, and CPU as fallback. Models are converted to .mlmodel format via coremltools from PyTorch, ONNX, or TensorFlow. Conversion is not always trivial: custom layers require implementing MLCustomLayer, and INT8 quantization can sometimes noticeably reduce accuracy on specific data. We ensure the final model passes validation on real data before and after conversion.

TensorFlow Lite — cross-platform alternative for Android and Flutter. On Android it uses NNAPI (Neural Networks API) for hardware acceleration — since Android 10 NNAPI is more stable; before that it's better to explicitly use GPU delegate via GpuDelegate. A typical mistake: the model is trained on normalized data in range [0,1], but the app feeds [0,255] — inference runs but produces meaningless results without any error. We include an automatic input data validation module in the SDK.

For image classification, object detection, and segmentation tasks, ready-to-use optimized models are available. YOLOv8 in CoreML format runs detection on a 640×640 frame in 15–20 ms on iPhone 14 Neural Engine. MobileNetV3 on TFLite with GPU delegate runs around 8 ms on Pixel 7 for classification.

Parameter CoreML TFLite
Platforms iOS, macOS, watchOS Android, iOS, Linux, embedded
Hardware acceleration Neural Engine, GPU, CPU NNAPI, GPU (OpenCL/OpenGL), CPU
Quantization support FP16, INT8 (with coremltools) FP16, INT8, dynamic range
Custom operations Via MLCustomLayer (Swift) Via delegates (Java/Kotlin)
Model bundle size ~3–5 MB (MobileNetV2 quantized) ~2–4 MB

What If You Need Text Generation On-Device?

Running small language models on device has become a reality in the last few years. Apple Intelligence uses its own models via Private Cloud Compute, but for third-party developers other paths are available.

llama.cpp with Metal backend on iOS is a working approach for phi-3-mini (3.8B parameters, 4-bit quantization, ~2.3 GB). Inference: 15–25 tokens/second on iPhone 15 Pro. For integration in Swift, use the Swift Package llama.swift or a wrapper via C interface llama.h. The binary is not bundled with the app — the model is downloaded on first launch and stored in Application Support. Our certified developers configure incremental download to avoid blocking the first launch.

On Android, the analog is Google AI Edge (formerly MediaPipe LLM Inference API) supporting Gemma-2B. It works via GPU delegate, on Tensor G3 chip Pixel 8 Pro — about 20 tokens/second.

Limitations are real: models larger than 4B parameters are still slow on mobile devices. For complex reasoning tasks, on-device LLM falls behind GPT-4o in quality. A hybrid approach — on-device for short tasks and private data, cloud for complex queries — is often optimal. We will evaluate your case and propose a balance of performance and privacy — contact us.

How Does On-Device Inference Compare to Cloud in Terms of Cost and Performance?

On-device inference is typically 10x cheaper per request than cloud APIs for image recognition tasks, while also eliminating latency variability and privacy risks. The table below summarizes the trade-offs.

Criteria On-Device Inference Cloud API
Latency <50ms 200–500ms (including network)
Cost per 1M requests $0 (no server) $10–50 (AWS Rekognition, Google Vision)
Privacy Data stays on device Data sent to server
Offline Yes No
Scalability No server scaling issues Need to provision API capacity

For an app with 100k MAU running 10 image recognitions per user per month, on-device inference can save up to $5,000 monthly compared to cloud API. Get a free consultation on your ML architecture today.

Integrating OpenAI API and Other Cloud Models

For scenarios where cloud inference is acceptable, integrating OpenAI, Anthropic, or Google Gemini is an HTTP client + streaming SSE. In Swift, AsyncThrowingStream is convenient for streaming responses. In Kotlin, use Flow.

Critically: API keys must never be stored in the app bundle. Even an obfuscated key can be extracted from the IPA in 10 minutes using strings or frida. Correct architecture: mobile app → your own backend → OpenAI API. The backend controls rate limiting, logs requests, and protects the key.

What Is Included in the Work (Deliverables)

  • Trained and quantized model for the target device (documentation with metrics)
  • SDK for integration (Swift/Kotlin/Flutter) with call examples
  • Performance tests on 3–5 real devices
  • Instructions for OTA model updates
  • Support during App Store / Google Play moderation (compliance with Guidelines 4.2, 5.1)
  • 2 weeks of technical support after release

Typical Project Pipeline

  1. Task analysis — measure latency, privacy, size, supported devices.
  2. Model prototyping — in Python, evaluate accuracy on target data.
  3. Conversion and quantization — for CoreML/TFLite with validation.
  4. Integration into the app — model wrapped in a service layer (easy to swap CoreML ↔ TFLite ↔ cloud).
  5. Testing — on real devices, measure FPS, RAM, battery.
  6. Deployment — via TestFlight / Firebase App Distribution, monitor metrics.

Timelines: integration of a ready CoreML/TFLite model — 1–2 weeks, development of a custom model with mobile optimization — from 6 weeks, on-device LLM chat with personalization — 4–8 weeks.

Why We Take on Complex Cases?

10+ years of experience in mobile development, 50+ implemented AI/ML solutions, guarantee of compatibility with current iOS and Android versions. All projects undergo code review and load testing. The cost includes preparation of moderation documentation and training of your team.

Contact us — we will help you choose the architecture and implement ML in your app turnkey. Order an audit of your existing solution — we will assess the potential for server cost savings free of charge. In some projects, savings can reach significant amounts per month.