Back to Documentation
Mobile App Integration
Collect feedback directly in your iOS or Android app.
Planned
The native SDKs are not released yet.
The CocoaPods, Gradle, npm and Flutter packages described on this page are a preview of the planned interface — they are not published, so the install commands below will not resolve.
What works in a mobile app today: open your survey's public URL in a WebView, or post responses straight to the REST API. Both are supported and need no SDK.
// Any WebView, iOS or Android
https://survey.aitocha.com/s/your-survey-slugSee the API reference for submitting responses directly, or tell us which platform you need so we can prioritise it.
Planned SDKs
iOS SDK
Swift & Objective-C
Android SDK
Kotlin & Java
iOS Installation
Swift Package Manager
// In Xcode: File → Add Packages // Enter URL: https://github.com/aitochasurveys/ios-sdk
CocoaPods
# Podfile pod 'AitochaSurveys', '~> 1.0'
Usage (Swift)
import AitochaSurveys // Initialize in AppDelegate AitochaSurveys.configure(surveyId: "YOUR_ID") // Show survey AitochaSurveys.show(from: viewController) // With user info AitochaSurveys.show( from: viewController, user: ["email": "user@example.com"] )
Android Installation
Gradle
// build.gradle (app)
dependencies {
implementation 'com.aitochasurveys:sdk:1.0.0'
}Usage (Kotlin)
import com.aitochasurveys.AitochaSurveys
// Initialize in Application
AitochaSurveys.configure(this, "YOUR_ID")
// Show survey
AitochaSurveys.show(activity)
// With user info
AitochaSurveys.show(activity, mapOf(
"email" to "user@example.com"
))React Native
npm install @aitochasurveys/react-native
import AitochaSurveys from '@aitochasurveys/react-native';
// Configure
AitochaSurveys.configure({ surveyId: 'YOUR_ID' });
// Show
AitochaSurveys.show();Flutter
# pubspec.yaml dependencies: aitocha_surveys: ^1.0.0 import 'package:aitocha_surveys/aitocha_surveys.dart'; // Configure AitochaSurveys.configure(surveyId: 'YOUR_ID'); // Show AitochaSurveys.show(context);
Best Practices
- Show surveys after key actions (purchase, support ticket, etc.)
- Don't interrupt critical user flows
- Respect user preferences (allow opt-out)
- Test on both platforms before release