Prompt Engineering for Mobile AI Assistant

Prompt Engineering for Mobile App AI Assistant

We've seen this happen: a GPT-4o model without a properly tuned prompt will answer one question verbosely, change tone on the next, and return JSON instead of text on the third. Prompt engineering is not just about 'writing a good instruction'—it's about controlling model determinism through system prompts, few-shot examples, and context window management. Our experience shows that a well-tuned prompt reduces erroneous answers by 40% and improves user satisfaction. We have years of experience developing mobile apps with AI assistants and know all the typical pitfalls. Without a proper prompt, users get irrelevant answers, hurting retention. Our approach is based on deep knowledge of both iOS/Android development and LLM behavior. We offer end-to-end configuration: from scenario analysis to final testing.

System Prompt: Structure Matters

A poor system prompt: 'You are a useful assistant in our app. Answer briefly and to the point.'

A working system prompt contains four zones:

• Role and domain constraints: 'You are the assistant of a personal finance app. Only answer questions related to budgeting, expense categorization, and financial planning. For off-topic questions, say: "I only help with personal finance questions."'
• Output format: If the assistant must return structured data, describe the schema directly in the system prompt with an example. The model follows the format much more reliably when it sees a concrete sample.
• Tone and style: 'Answer concisely—no more than 3 sentences. Do not use bullet lists in conversational responses. Do not start with "Sure!" or "Great question!"'
• User context: Dynamically inject information: user name, current app section, recent actions.

func buildSystemPrompt(user: User, currentScreen: AppScreen) -> String {
    return """
    You are the financial assistant of MoneyMap app.
    User: \(user.name), currency: \(user.currency).
    Current section: \(currentScreen.description).
    Monthly budget: \(user.monthlyBudget). Spent: \(user.spent).
    Answer concisely in English, without lists.
    """
}

Few-Shot Examples and Context Window Management

Few-shot means 2–5 question-answer pairs at the start of a conversation. They serve as behavior templates. Critical: examples must cover edge cases, not just 'ideal' scenarios.

A common problem with mobile assistants is the limited context window during long sessions. GPT-4o-mini has 128K tokens, but costs grow linearly.

How to Choose Temperature and top_p?

temperature=0—deterministic output, the model always picks the most probable token. For structured responses (JSON, numbers, classification), set 0 or 0.1. For text generation 'in style', use 0.7–0.9.

top_p=0.9 + temperature=0.7—a standard combination for a conversational assistant. Do not tweak both parameters simultaneously—they interact unpredictably.

Steps for Prompt Engineering Configuration

What's Included in the Work?

• Development of a system prompt tailored to your app's specifics
• Creation of few-shot examples for edge cases
• Configuration of context window management strategy (sliding window, summary, RAG)
• Integration into iOS/Android/Flutter code
• Documentation of prompts and recommendations for further optimization
• Training your team on prompt engineering
• Support for 30 days after launch

Why Trust Us with Configuration?

Our team has extensive experience in mobile development and numerous implemented projects with AI assistants. We guarantee that the configured prompt will meet all App Store Review Guidelines and Google Play Console requirements. We provide a quality certificate and full documentation. Reduce support costs by up to 30% through high-quality prompts.

Contact us to discuss configuring your assistant. We'll evaluate the task and propose an optimal solution.

As researchers note, "prompt quality directly affects the accuracy and safety of AI assistant work" (OpenAI, Prompt Engineering Guide).

Learn basic concepts at Prompt engineering.

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.