Key Takeaways
- iPhone (A18): 1–3B models, ~3 tok/sec. Llama 3.2 1B is practical.
- Android (Snapdragon X): 7B models, ~5 tok/sec. Practical for chat.
- iPad (M4): 7–13B models, ~15 tok/sec. Best mobile experience.
- Offline inference = privacy, no API costs, no latency.
- As of April 2026, on-device LLMs are niche but growing rapidly.
Mobile Hardware for AI in 2026
| Device | Max Model Size | Speed | Memory |
|---|---|---|---|
| iPhone 16 (A18) | — | 3 tok/sec | — |
| iPhone 16 Pro (A18 Pro) | — | 4 tok/sec | — |
| Android (Snapdragon X) | — | 5 tok/sec | — |
| iPad Pro (M4) | — | 15 tok/sec | — |
Best Mobile LLM Apps (April 2026)
| App | Platform | Supported Models | Cost |
|---|---|---|---|
| Ollama (iOS) | iPhone, iPad | — | Free |
| LLaMa Lite | Android | — | Free |
| Chatlize | iOS, Android | — | Free + Pro |
| Jan AI (Mobile) | Android (beta) | — | Free |
Frameworks for Mobile LLM Development
iOS: Core ML, Metal Performance Shaders (Apple's optimization tools).
Android: TensorFlow Lite, ONNX Runtime, Snapdragon Neural Processing Engine.
Developers can convert Llama, Qwen, and Mistral models to mobile-optimized formats.
Realistic Mobile Performance
Mobile is slow compared to desktop:
| Device | Model | Tokens/Sec |
|---|---|---|
| Desktop RTX 4090 | Llama 7B | — |
| iPad M4 | Llama 7B | — |
| Android (Snapdragon X) | Llama 7B | — |
| iPhone 16 Pro | Llama 3B | — |
Common Mobile LLM Mistakes
- Trying to run 7B models on iPhone. Max practical is 3B. Anything larger causes crashes or extreme slowness.
- Expecting latency like desktop. Mobile is 20–50× slower. Accept 2–5 second response times.
- Using cloud APIs as fallback. If offline offline is the goal, design UX for slow, local-only inference.
- Not optimizing for battery. Mobile inference drains battery quickly. Limit response length and batch size.
Sources
- Apple A18 Chip — apple.com/iphone-16/specs
- Snapdragon X Performance — qualcomm.com/snapdragon-x-series
- Ollama iOS App — github.com/jmorello/Ollama-SwiftUI
- TensorFlow Lite — tensorflow.org/lite