flutter_gemma 0.10.0
flutter_gemma: ^0.10.0 copied to clipboard
The plugin allows running the Gemma AI model locally on a device from a Flutter application. Includes support for Gemma 3 Nano models with optimized MediaPipe GenAI v0.10.24.
# Flutter Gemma
The plugin supports not only Gemma, but also other models. Here's the full list of supported models: Gemma 2B & Gemma 7B, Gemma-2 2B, Gemma-3 1B, Gemma 3 Nano 2B, Gemma 3 Nano 4B, Phi-2, Phi-3 , Phi-4, DeepSeek, Falcon-RW-1B, StableLM-3B.
*Note: Currently, the flutter_gemma plugin supports Gemma-3, Gemma 3 Nano (with multimodal vision support), Phi-4 and DeepSeek.
Gemma is a family of lightweight, state-of-the art open models built from the same research and technology used to create the Gemini models
Bring the power of Google's lightweight Gemma language models directly to your Flutter applications. With Flutter Gemma, you can seamlessly incorporate advanced AI capabilities into your iOS and Android apps, all without relying on external servers.
There is an example of using:
Features #
- Local Execution: Run Gemma models directly on user devices for enhanced privacy and offline functionality.
- Platform Support: Compatible with iOS, Android, and Web platforms.
- πΌοΈ Multimodal Support: Text + Image input with Gemma 3 Nano vision models (NEW!)
- π οΈ Function Calling: Enable your models to call external functions and integrate with other services (supported by select models)
- LoRA Support: Efficient fine-tuning and integration of LoRA (Low-Rank Adaptation) weights for tailored AI behavior.
Installation #
-
Add
flutter_gemma
to yourpubspec.yaml
:dependencies: flutter_gemma: latest_version
-
Run
flutter pub get
to install.
Setup #
- Download Model and optionally LoRA Weights: Obtain a pre-trained Gemma model (recommended: 2b or 2b-it) from Kaggle
- For multimodal support, download Gemma 3 Nano models that support vision input
- Optionally, fine-tune a model for your specific use case
- If you have LoRA weights, you can use them to customize the model's behavior without retraining the entire model.
- There is an article that described all approaches
- Platform specific setup:
iOS
- Enable file sharing in
info.plist
:
<key>UIFileSharingEnabled</key>
<true/>
- Change the linking type of pods to static, replace
use_frameworks!
in Podfile withuse_frameworks! :linkage => :static
Android
- If you want to use a GPU to work with the model, you need to add OpenGL support in the manifest.xml. If you plan to use only the CPU, you can skip this step.
Add to 'AndroidManifest.xml' above tag </application>
<uses-native-library
android:name="libOpenCL.so"
android:required="false"/>
<uses-native-library android:name="libOpenCL-car.so" android:required="false"/>
<uses-native-library android:name="libOpenCL-pixel.so" android:required="false"/>
Web
-
Web currently works only GPU backend models, CPU backend models are not supported by MediaPipe yet
-
Multimodal support (images) is in development for web platform
-
Add dependencies to
index.html
file in web folder
<script type="module">
import { FilesetResolver, LlmInference } from 'https://cdn.jsdelivr.net/npm/@mediapipe/tasks-genai';
window.FilesetResolver = FilesetResolver;
window.LlmInference = LlmInference;
</script>
Usage #
The new API splits functionality into two parts:
- ModelFileManager: Manages model and LoRA weights file handling.
- InferenceModel: Handles model initialization and response generation.
The updated API splits the functionality into two main parts:
- Access the plugin via:
final gemma = FlutterGemmaPlugin.instance;
- Managing Model Files with ModelFileManager
final modelManager = gemma.modelManager;
Place the model in the assets or upload it to a network drive, such as Firebase.
ATTENTION!! You do not need to load the model every time the application starts; it is stored in the system files and only needs to be done once. Please carefully review the example application. You should use loadAssetModel and loadNetworkModel methods only when you need to upload the model to device
Usage #
1.Loading Models from assets (available only in debug mode):
Don't forget to add your model to pubspec.yaml
- Loading from assets (loraUrl is optional)
await modelManager.installModelFromAsset('model.bin', loraPath: 'lora_weights.bin');
- Loading from assets with Progress Status (loraUrl is optional)
modelManager.installModelFromAssetWithProgress('model.bin', loraPath: 'lora_weights.bin').listen(
(progress) {
print('Loading progress: $progress%');
},
onDone: () {
print('Model loading complete.');
},
onError: (error) {
print('Error loading model: $error');
},
);
2.Loading Models from network:
-
For web usage, you will also need to enable CORS (Cross-Origin Resource Sharing) for your network resource. To enable CORS in Firebase, you can follow the guide in the Firebase documentation: Setting up CORS
- Loading from the network (loraUrl is optional).
await modelManager.downloadModelFromNetwork('https://example.com/model.bin', loraUrl: 'https://example.com/lora_weights.bin');
- Loading from the network with Progress Status (loraUrl is optional)
modelManager.downloadModelFromNetworkWithProgress('https://example.com/model.bin', loraUrl: 'https://example.com/lora_weights.bin').listen(
(progress) {
print('Loading progress: $progress%');
},
onDone: () {
print('Model loading complete.');
},
onError: (error) {
print('Error loading model: $error');
},
);
- Loading LoRA Weights
- Loading LoRA weight from the network.
await modelManager.downloadLoraWeightsFromNetwork('https://example.com/lora_weights.bin');
- Loading LoRA weight from assets.
await modelManager.installLoraWeightsFromAsset('lora_weights.bin');
- Model Management You can set model and weights paths manually
await modelManager.setModelPath('model.bin');
await modelManager.setLoraWeightsPath('lora_weights.bin');
You can delete the model and weights from the device. Deleting the model or LoRA weights will automatically close and clean up the inference. This ensures that there are no lingering resources or memory leaks when switching models or updating files.
await modelManager.deleteModel();
await modelManager.deleteLoraWeights();
5.Initialize:
Before performing any inference, you need to create a model instance. This ensures that your application is ready to handle requests efficiently.
Text-Only Models:
final inferenceModel = await FlutterGemmaPlugin.instance.createModel(
modelType: ModelType.gemmaIt, // Required, model type to create
preferredBackend: PreferredBackend.gpu, // Optional, backend type, default is PreferredBackend.gpu
maxTokens: 512, // Optional, default is 1024
);
πΌοΈ Multimodal Models (NEW!):
final inferenceModel = await FlutterGemmaPlugin.instance.createModel(
modelType: ModelType.gemmaIt, // Required, model type to create
preferredBackend: PreferredBackend.gpu, // Optional, backend type
maxTokens: 4096, // Recommended for multimodal models
supportImage: true, // Enable image support
maxNumImages: 1, // Optional, maximum number of images per message
);
6.Using Sessions for Single Inferences:
If you need to generate individual responses without maintaining a conversation history, use sessions. Sessions allow precise control over inference and must be properly closed to avoid memory leaks.
- Text-Only Session:
final session = await inferenceModel.createSession(
temperature: 1.0, // Optional, default is 0.8
randomSeed: 1, // Optional, default is 1
topK: 1, // Optional, default is 1
);
await session.addQueryChunk(Message.text(text: 'Tell me something interesting', isUser: true));
String response = await session.getResponse();
print(response);
await session.close(); // Always close the session when done
- πΌοΈ Multimodal Session (NEW!):
final session = await inferenceModel.createSession();
// Text + Image message
final imageBytes = await loadImageBytes(); // Your image loading method
await session.addQueryChunk(Message.withImage(
text: 'What do you see in this image?',
imageBytes: imageBytes,
isUser: true,
));
String response = await session.getResponse();
print(response);
await session.close();
- Asynchronous Response Generation:
final session = await inferenceModel.createSession();
await session.addQueryChunk(Message.text(text: 'Tell me something interesting', isUser: true));
session.getResponseAsync().listen((String token) {
print(token);
}, onDone: () {
print('Stream closed');
}, onError: (error) {
print('Error: $error');
});
await session.close(); // Always close the session when done
7.Chat Scenario with Automatic Session Management
For chat-based applications, you can create a chat instance. Unlike sessions, the chat instance manages the conversation context and refreshes sessions when necessary.
Text-Only Chat:
final chat = await inferenceModel.createChat(
temperature: 0.8, // Controls response randomness
randomSeed: 1, // Ensures reproducibility
topK: 1, // Limits vocabulary scope
);
πΌοΈ Multimodal Chat (NEW!):
final chat = await inferenceModel.createChat(
temperature: 0.8, // Controls response randomness
randomSeed: 1, // Ensures reproducibility
topK: 1, // Limits vocabulary scope
supportImage: true, // Enable image support in chat
);
- Synchronous Chat:
await chat.addQueryChunk(Message.text(text: 'User: Hello, who are you?', isUser: true));
String response = await chat.generateChatResponse();
print(response);
await chat.addQueryChunk(Message.text(text: 'User: Are you sure?', isUser: true));
String response2 = await chat.generateChatResponse();
print(response2);
- πΌοΈ Multimodal Chat Example:
// Add text message
await chat.addQueryChunk(Message.text(text: 'Hello!', isUser: true));
String response1 = await chat.generateChatResponse();
// Add image message
final imageBytes = await loadImageBytes();
await chat.addQueryChunk(Message.withImage(
text: 'Can you analyze this image?',
imageBytes: imageBytes,
isUser: true,
));
String response2 = await chat.generateChatResponse();
// Add image-only message
await chat.addQueryChunk(Message.imageOnly(imageBytes: imageBytes, isUser: true));
String response3 = await chat.generateChatResponse();
- Asynchronous Chat (Streaming):
await chat.addQueryChunk(Message.text(text: 'User: Hello, who are you?', isUser: true));
chat.generateChatResponseAsync().listen((String token) {
print(token);
}, onDone: () {
print('Chat stream closed');
}, onError: (error) {
print('Chat error: $error');
});
- π οΈ Function Calling
Enable your models to call external functions and integrate with other services. Note: Function calling is only supported by specific models - see the Model Support section below.
Step 1: Define Tools
Tools define the functions your model can call:
final List<Tool> _tools = [
const Tool(
name: 'change_background_color',
description: "Changes the background color of the app. The color should be a standard web color name like 'red', 'blue', 'green', 'yellow', 'purple', or 'orange'.",
parameters: {
'type': 'object',
'properties': {
'color': {
'type': 'string',
'description': 'The color name',
},
},
'required': ['color'],
},
),
const Tool(
name: 'show_alert',
description: 'Shows an alert dialog with a custom message and title.',
parameters: {
'type': 'object',
'properties': {
'title': {
'type': 'string',
'description': 'The title of the alert dialog',
},
'message': {
'type': 'string',
'description': 'The message content of the alert dialog',
},
},
'required': ['title', 'message'],
},
),
];
Step 2: Create Chat with Tools
final chat = await inferenceModel.createChat(
temperature: 0.8,
tools: _tools, // Pass your tools
supportsFunctionCalls: true, // Enable function calling (optional, auto-detected from model)
);
Step 3: Handle Different Response Types
The model can now return two types of responses:
// Add user message
await chat.addQueryChunk(Message.text(text: 'Change the background to blue', isUser: true));
// Handle async responses
chat.generateChatResponseAsync().listen((response) {
if (response is TextResponse) {
// Regular text token from the model
print('Text: ${response.token}');
// Update your UI with the text
} else if (response is FunctionCallResponse) {
// Model wants to call a function
print('Function Call: ${response.name}(${response.args})');
_handleFunctionCall(response);
}
});
Step 4: Execute Function and Send Response Back
Future<void> _handleFunctionCall(FunctionCallResponse functionCall) async {
// Execute the requested function
Map<String, dynamic> toolResponse;
switch (functionCall.name) {
case 'change_background_color':
final color = functionCall.args['color'] as String?;
// Your implementation here
toolResponse = {'status': 'success', 'message': 'Color changed to $color'};
break;
case 'show_alert':
final title = functionCall.args['title'] as String?;
final message = functionCall.args['message'] as String?;
// Show alert dialog
toolResponse = {'status': 'success', 'message': 'Alert shown'};
break;
default:
toolResponse = {'error': 'Unknown function: ${functionCall.name}'};
}
// Send the tool response back to the model
final toolMessage = Message.toolResponse(
toolName: functionCall.name,
response: toolResponse,
);
await chat.addQuery(toolMessage);
// The model will then generate a final response explaining what it did
final finalResponse = await chat.generateChatResponse();
print('Model: $finalResponse');
}
Function Calling Best Practices:
- Use descriptive function names and clear descriptions
- Specify required vs optional parameters
- Always handle function execution errors gracefully
- Send meaningful responses back to the model
- The model will only call functions when explicitly requested by the user
πΌοΈ Message Types (NEW!) #
The plugin now supports different types of messages:
// Text only
final textMessage = Message.text(text: "Hello!", isUser: true);
// Text + Image
final multimodalMessage = Message.withImage(
text: "What's in this image?",
imageBytes: imageBytes,
isUser: true,
);
// Image only
final imageMessage = Message.imageOnly(imageBytes: imageBytes, isUser: true);
// Tool response (for function calling)
final toolMessage = Message.toolResponse(
toolName: 'change_background_color',
response: {'status': 'success', 'color': 'blue'},
);
// Check if message contains image
if (message.hasImage) {
print('This message contains an image');
}
// Create a copy of message
final copiedMessage = message.copyWith(text: "Updated text");
π¬ Response Types (NEW!) #
When using function calling, the model can return different types of responses:
// Handle different response types
chat.generateChatResponseAsync().listen((response) {
if (response is TextResponse) {
// Regular text token from the model
print('Text token: ${response.token}');
// Use response.token to update your UI incrementally
} else if (response is FunctionCallResponse) {
// Model wants to call a function
print('Function: ${response.name}');
print('Arguments: ${response.args}');
// Execute the function and send response back
_handleFunctionCall(response);
}
});
Response Types:
TextResponse
: Contains a text token (response.token
) for regular model outputFunctionCallResponse
: Contains function name (response.name
) and arguments (response.args
) when the model wants to call a function
9.Checking Token Usage You can check the token size of a prompt before inference. The accumulated context should not exceed maxTokens to ensure smooth operation.
int tokenCount = await session.sizeInTokens('Your prompt text here');
print('Prompt size in tokens: $tokenCount');
10.Closing the Model
When you no longer need to perform any further inferences, call the close method to release resources:
await inferenceModel.close();
If you need to use the inference again later, remember to call createModel
again before generating responses.
π― Supported Models #
Text-Only Models #
- Gemma 2B & Gemma 7B
- Gemma-2 2B
- Gemma-3 1B
- Phi-4
- DeepSeek
- Phi-2, Phi-3, Falcon-RW-1B, StableLM-3B
πΌοΈ Multimodal Models (Vision + Text) #
- Gemma 3 Nano E2B - 1.5B parameters with vision support
- Gemma 3 Nano E4B - 1.5B parameters with vision support
π οΈ Model Function Calling Support #
Function calling is currently supported by the following models:
β Models with Function Calling Support #
- Gemma 3 Nano models (E2B, E4B) - Full function calling support
- Gemma 3 Nano Local Asset models - Full function calling support
- Qwen models - Full function calling support
β Models WITHOUT Function Calling Support #
- Gemma 3 1B models - Text generation only
- DeepSeek models - Text generation only
- Phi models - Text generation only
Important Notes:
- When using unsupported models with tools, the plugin will log a warning and ignore the tools
- Models will work normally for text generation even if function calling is not supported
- Check the
supportsFunctionCalls
property in your model configuration
π Platform Support #
Feature | Android | iOS | Web |
---|---|---|---|
Text Generation | β | β | β |
Image Input | β | β | β οΈ |
Function Calling | β | β | β |
GPU Acceleration | β | β | β |
Streaming Responses | β | β | β |
LoRA Support | β | β | β |
- β = Fully supported
- β οΈ = In development
The full and complete example you can find in example
folder
Important Considerations #
- Model Size: Larger models (such as 7b and 7b-it) might be too resource-intensive for on-device inference.
- Function Calling Support: Only Gemma 3 Nano models support function calling. Other models will ignore tools and show a warning.
- Multimodal Models: Gemma 3 Nano models with vision support require more memory and are recommended for devices with 8GB+ RAM.
- LoRA Weights: They provide efficient customization without the need for full model retraining.
- Development vs. Production: For production apps, do not embed the model or LoRA weights within your assets. Instead, load them once and store them securely on the device or via a network drive.
- Web Models: Currently, Web support is available only for GPU backend models. Multimodal support is in development.
- Image Formats: The plugin automatically handles common image formats (JPEG, PNG, etc.) when using
Message.withImage()
.
π Troubleshooting #
Multimodal Issues:
- Ensure you're using a multimodal model (Gemma 3 Nano E2B/E4B)
- Set
supportImage: true
when creating model and chat - Check device memory - multimodal models require more RAM
Performance:
- Use GPU backend for better performance with multimodal models
- Consider using CPU backend for text-only models on lower-end devices
Memory Issues:
- Reduce
maxTokens
if experiencing memory issues - Close sessions and models when not needed
- Monitor token usage with
sizeInTokens()
π What's New #
β
π οΈ Advanced Function Calling - Enable your models to call external functions and integrate with other services (Gemma 3 Nano models only)
β
π¬ Enhanced Response Types - New TextResponse
and FunctionCallResponse
types for better handling
β
πΌοΈ Multimodal Support - Text + Image input with Gemma 3 Nano models
β
π¨ Enhanced Message API - Support for different message types including tool responses
β
βοΈ Simplified Setup - Automatic vision modality configuration
β
π Cross-Platform - Works on Android, iOS, and Web (text-only)
β
πΎ Memory Optimization - Better resource management for multimodal models
Coming Soon:
- Enhanced web platform support for images
- More multimodal model support
- Video/Audio input capabilities