Developing an AI Assistant in Mobile Apps with GPT-4o

We frequently encounter clients who want to integrate an AI assistant into their mobile app but are unsure about the architecture. The most common mistake is using GPT-4-turbo instead of GPT-4o and building separate pipelines for text, images, and voice. GPT-4o is a multimodal model: it accepts text, images, and audio in a single API call. This changes the assistant's architecture: instead of separate pipelines for OCR + text + voice, you use one endpoint gpt-4o with content of type array. A mobile app that doesn't leverage this loses half the model's value. Our experience shows that proper multimodal integration reduces development time by 30% and improves UX through a unified data flow.

OpenAI API Integration: What Really Matters

The basic call is via POST /v1/chat/completions. On iOS, use the official openai-swift package or a thin wrapper on URLSession—no need for heavy HTTP clients. On Android, use the official OpenAI Kotlin client or OkHttp.

Key parameters for a mobile assistant:

let request = ChatCompletionRequest(
    model: "gpt-4o",
    messages: conversationHistory,
    stream: true,           // streaming is mandatory for UX
    maxTokens: 1024,
    temperature: 0.7
)

Streaming Is Mandatory for UX

A user waiting 5–8 seconds of silence before seeing a response will close the app. With stream: true, the first token arrives within 300–500 ms, and text appears character by character. Implementation on iOS via URLSession + AsyncBytes or EventSource for SSE. On Android, OkHttp with Enqueue and line-by-line reading. We ensure streaming works stably even on unstable connections using retry with exponential backoff.

Multimodality of GPT-4o. Sending an image:

let message = ChatMessage(role: .user, content: [
    .text("What is depicted in this screenshot?"),
    .imageURL(base64Image: imageBase64, detail: .auto)
])

detail: .auto lets the model choose between low (85 tokens) and high (up to 1700 tokens) based on the task. For document analysis, use high; for quick responses, use low.

How to Integrate GPT-4o into a Mobile App?

Step-by-step integration:

1. Set up API client — create configuration with base URL and key (via server proxy).
2. Configure streaming — enable stream: true and implement token streaming.
3. Manage context — implement a sliding window with summarization via GPT-4o-mini.
4. Handle errors — implement exponential backoff with jitter for rate limits.

When to Use GPT-4o-mini for Summarization?

If the dialog history exceeds a threshold (e.g., 4000 tokens), compress it using GPT-4o-mini. This is 20× cheaper than a full pass through GPT-4o. Algorithm: keep the last N messages intact, replace earlier ones with a summary placed as a system message at the start of the history. Count tokens via tiktoken server-side or heuristically.

Comparison: GPT-4o vs GPT-4-turbo for Mobile Scenarios

Typical Errors and Their Handling

func retryWithBackoff<T>(maxAttempts: Int = 3, operation: () async throws -> T) async throws -> T {
    var attempt = 0
    while attempt < maxAttempts {
        do {
            return try await operation()
        } catch APIError.rateLimitExceeded {
            let delay = Double.random(in: 1.0...2.0) * pow(2.0, Double(attempt))
            try await Task.sleep(nanoseconds: UInt64(delay * 1_000_000_000))
            attempt += 1
        }
    }
    throw APIError.maxRetriesExceeded
}

API Key Security

You must never hardcode the OpenAI API key in a mobile app—it can be extracted from the binary in minutes. The correct scheme: the mobile client authenticates on your own backend, and the backend proxies requests to OpenAI with the key from environment variables. Additionally, implement per-user rate limiting. This complies with App Store Review Guidelines.

Our Process

• Requirements audit: which modalities are needed (text only, images, voice), whether a server proxy is required, history management (how long to store, syncing across devices).
• Development: API client → streaming UI → history management → multimodality → error handling → server proxy.
• Deployment and testing: load testing of streaming, rate limit checks, debugging on real devices.

What's Included

• Ready-to-use OpenAI API integration (GPT-4o, GPT-4-turbo, GPT-4o-mini)
• Streaming chat UI supporting text, images, and voice
• Server proxy for secure API key storage
• Context management module with summarization
• Deployment and customization documentation
• Team training (2 hours online)
• 1 month of post-delivery support

Timeline Estimates

Text assistant with streaming and history: 1–2 weeks. With images, voice, server proxy, and context management: 3–5 weeks. Cost is calculated individually after requirements audit.

Get a consultation for your project—our team will assess the task within two days. Our experience includes over 20 AI assistant integrations for iOS and Android, 5+ years in mobile technologies. Certified engineers guarantee compliance with OpenAI API best practices.

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.

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.

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.