PyTorch Mobile Development: Integration, Optimization, Inference

Machine Learning Development with PyTorch Mobile: Integration, Optimization, Inference

Your data science team trained a model in PyTorch, and now you need to run it on a mobile device. Converting to TFLite or Core ML requires rewriting part of the graph — no time, and non-standard operations aren't supported. We help port PyTorch models to iOS and Android via PyTorch Mobile, preserving accuracy and performance. Our experience — 30+ projects with ML on mobile devices, including NLP, CV, and recommendation systems. We guarantee model compatibility with target devices. Switching to on-device inference reduces cloud AI costs by up to 70%.

PyTorch Mobile is less common compared to TFLite and Core ML, but it wins in several scenarios. Primarily where the data science team works in PyTorch and doesn't want to spend time converting to another format. Or when a model uses custom operations that TFLite doesn't support. Additionally, PyTorch Mobile provides a unified API for both platforms, simplifying maintenance. It also supports quantization via qnnpack, yielding a 2-3x performance boost on convolution operations.

Why PyTorch Mobile Instead of TFLite?

If your model uses custom layers (e.g., custom attention), TFLite requires writing operators in C++ — weeks of work. PyTorch Mobile accepts TorchScript directly, and many operations are built-in. Comparison: for BERT-lite, conversion via ONNX to TFLite would take 2 days, while via TorchScript it takes 3 hours. PyTorch Mobile is better for rapid prototyping and models with unique architectures.

In this article, we'll cover how to convert a model to TorchScript, optimize it for mobile using optimize_for_mobile, perform INT8 quantization for speed, and integrate it into iOS and Android apps with Lite Interpreter. We'll also show a real case with BERT-lite, where the model size decreased from 23 MB to 6 MB, and inference time on a Pixel 6 was 45 ms for 128 tokens. This approach allows using powerful models on mobile devices without compromising the user experience.

TorchScript: The Key Requirement for PyTorch Mobile

PyTorch Mobile only works with TorchScript models — neither eager mode nor torch.fx works. Conversion via torch.jit.trace or torch.jit.script. The difference is fundamental: trace records the execution path for specific inputs and cannot handle data-dependent branching. script analyzes the graph statically and correctly handles if/for, but requires type annotations. If the model contains if x.shape[0] > 1:, trace silently records only one branch. In production, this manifests as incorrect results on certain batch sizes rather than a crash — hard to catch.

After conversion, optimize with optimize_for_mobile:

from torch.utils.mobile_optimizer import optimize_for_mobile scripted = torch.jit.script(model) optimized = optimize_for_mobile(scripted) optimized._save_for_lite_interpreter("model.ptl") 

.ptl (Lite Interpreter format) is not the same as .pt. On mobile, you use Lite Interpreter — it doesn't support all PyTorch operations, but has a smaller binary size.

How to Correctly Convert a Model to TorchScript?

The choice between trace and script depends on the model's dynamism. For models with conditional operators, script is the only option. We recommend writing tests after conversion: run the model on synthetic data and compare outputs before and after. If the discrepancy exceeds 1%, we locate the problematic node. This ensures the model works identically on mobile as on the server.

Quantization and Performance

Post-training static quantization for mobile:

model.qconfig = torch.quantization.get_default_qconfig('qnnpack') # for ARM torch.quantization.prepare(model, inplace=True) # run calibration dataset torch.quantization.convert(model, inplace=True) 

qnnpack is the backend for ARM processors (what you need for Android and iOS). fbgemm is for x86 and doesn't work on mobile. This is a common mistake: a developer quantizes with fbgemm on a laptop and wonders why the model doesn't speed up on a phone.

Why Quantization with qnnpack and Not fbgemm?

Because mobile ARM processors use NEON instructions. qnnpack is optimized for them, fbgemm is for AVX2 on x86. Choosing the wrong backend results in zero speedup. In practice, the gain from INT8 on ARM: 2-3x on operations like Linear and Conv2d. On iPhones with Neural Engine, PyTorch Mobile does not leverage it directly — unlike Core ML. If you need Neural Engine on iOS, the correct path is conversion via coremltools, not PyTorch Mobile.

Integration on Android and iOS

Android. Dependency org.pytorch:pytorch_android_lite (Lite Interpreter). Inference:

val module = LiteModuleLoader.load(assetFilePath("model.ptl")) val inputTensor = TensorImageUtils.bitmapToFloat32Tensor(bitmap, mean, std) val output = module.forward(IValue.from(inputTensor)).toTensor() 

Offload image preprocessing (normalization, resize) to Executors.newSingleThreadExecutor() — not on the main thread.

iOS. CocoaPod LibTorch-Lite. Work through TorchModule:

let module = TorchModule(fileAtPath: modelPath) let result = module.predict(image: &tensorData) 

All inference on DispatchQueue.global(qos: .userInitiated).

Example: NLP task, BERT-lite for classifying reviews inside a corporate app. The DS team worked in PyTorch, converting to TFLite was not desired (custom attention block). We used TorchScript + INT8 quantization (qnnpack). Model size decreased from 23 MB to 6 MB, inference on Pixel 6 — 45 ms for 128 tokens. Sufficient for real-time analytics.

How We Work: From Analysis to Deployment

1. Model analysis — evaluate the graph, operations, size. Identify problematic nodes for TorchScript.
2. Conversion and optimization — write conversion script, test on desktop, then optimize with optimize_for_mobile and quantize.
3. App integration — add Lite Interpreter, write wrapper for inference on a background thread to keep UI responsive.
4. Device testing — verify output correctness (compare with original model), measure performance, temperature, memory usage.
5. Deployment and monitoring — upload to App Store / Google Play, use Firebase for metrics. Updating the model only requires replacing model.ptl.

What's Included in the Work

• Full documentation on conversion and integration (including troubleshooting).
• Source code for iOS (Swift) and Android (Kotlin) integration.
• Instructions for updating the model without rebuilding the app.
• Support during store release (handling issues if the model violates guidelines).
• Guaranteed compatibility with iOS 15+ and Android 12+.

Timelines and Cost

Conversion and integration of a ready PyTorch model into Android or iOS — 1–2 weeks, including TorchScript debugging and device testing. Cost is calculated individually. Contact us for a project estimate — we'll provide approximate time and budget.

Common Mistakes in PyTorch Mobile Integration

• Using fbgemm for quantization instead of qnnpack.
• Forgetting to save the model in Lite Interpreter format (.ptl).
• Running inference on the main thread — causes UI freezes.
• Not checking that the model uses unsupported operations (e.g., torch.einsum may not be available).
• Not accounting for model size during loading — large models (>50 MB) may be evicted from memory.

We have been working with mobile development since the release of PyTorch Mobile and have completed 30+ projects with ML integration. Our experience spans over 10 years. We guarantee model compatibility with target devices.

Want to port your model to mobile? Contact us for a free consultation on timelines and complexity.