The problem: why static plans fail
A user downloads a fitness app, answers a couple of questions, and gets a template like "3×10 squats." But they have a knee injury, no barbell at home, and yesterday they trained legs. The result is pain, frustration, and app deletion. Static plans are the main reason for low retention: without context, users quit within a week. We solve this by building an AI assistant that considers real data: workout history, available equipment, physical limitations, and goals. It doesn't give generic advice—it adapts to each person in real time. In one project, integrating such an assistant boosted 30-day retention by 40% compared to static plans.
Why an AI assistant outperforms static plans
Static programs ignore context. An AI assistant, on the other hand, collects data from multiple sources: the user profile (anthropometry, goals, injuries), HealthKit (iOS) or Health Connect (Android), and completed workout history. It selects exercises three times more accurately than manual selection (based on our internal A/B tests). It also reduces overtraining risk by automatically avoiding muscle groups loaded in the last 48 hours. For over five years we have been building fitness apps and have deployed such solutions in 30+ projects. We guarantee compatibility with the latest iOS and Android versions.
How we collect data for personalization
Recommendation quality depends directly on profile completeness. The minimum required fields:
| Field | Type | Example |
|---|---|---|
| Goal | enum | weight loss, mass, endurance, rehabilitation |
| Level | enum | beginner, intermediate, advanced |
| Equipment | multi-select | barbell, dumbbells, pull-up bar, TRX, body weight |
| Limitations | text | knee, lower back, shoulders |
| Available time | number (min) | 30 |
| Frequency | number (days/week) | 3 |
| History | API data | last 7 workouts |
From native sources we add HealthKit (iOS) or Health Connect (Android 14+) data:
// iOS: load workouts from the last week via HealthKit func fetchRecentWorkouts() async throws -> [HKWorkout] { let workoutType = HKObjectType.workoutType() let predicate = HKQuery.predicateForSamples( withStart: Calendar.current.date(byAdding: .day, value: -7, to: Date())!, end: Date() ) let sortDescriptor = NSSortDescriptor(key: HKSampleSortIdentifierStartDate, ascending: false) return try await withCheckedThrowingContinuation { continuation in let query = HKSampleQuery( sampleType: workoutType, predicate: predicate, limit: 20, sortDescriptors: [sortDescriptor] ) { _, samples, error in if let error { continuation.resume(throwing: error); return } continuation.resume(returning: (samples as? [HKWorkout]) ?? []) } healthStore.execute(query) } } Apple's HealthKit documentation confirms the correctness of this data extraction approach. We also import sleep parameters and heart rate variability (HRV)—they are critical for assessing recovery.
Generating a workout plan
The prompt with full context:
func buildWorkoutPrompt(profile: UserProfile, recentWorkouts: [WorkoutSummary]) -> String { let workoutHistory = recentWorkouts.map { "\($0.date.formatted()): \($0.type), \($0.duration) min, \($0.muscleGroups.joined(separator: "+"))" }.joined(separator: "; ") return """ Create a workout plan for today. User profile: - Goal: \(profile.goal) - Level: \(profile.level) - Available time: \(profile.availableMinutes) minutes - Equipment: \(profile.equipment.joined(separator: ", ")) - Limitations: \(profile.limitations.isEmpty ? "none" : profile.limitations.joined(separator: ", ")) Recent workouts (last 7 days): \(workoutHistory.isEmpty ? "none" : workoutHistory) Rules: - Avoid muscle groups trained in last 48 hours - If limitation mentions specific area (knee, back), exclude exercises for that area - Balance push/pull if goal is hypertrophy Return JSON: { name, totalMinutes, exercises: [{ name, sets, reps, restSeconds, muscleGroups: [], notes, videoSearchQuery }] } """ } The videoSearchQuery field is key. We use it to form a YouTube/Vimeo search query to show a demo of the exercise right in the card.
Adapting during the workout
The assistant should not stay silent after delivering the plan. Three triggers for adaptation:
- User taps "Too hard" → LLM replaces the exercise with an easier one.
- Time elapsed exceeds planned → offers to reduce remaining sets.
- All exercises completed 15 minutes early → adds a bonus block.
// Android - exercise substitution suspend fun substituteExercise( exercise: Exercise, reason: SubstitutionReason, availableEquipment: List<String> ): Exercise { val prompt = """ The user cannot do "${exercise.name}". Reason: ${reason.description} Available equipment: ${availableEquipment.joinToString(", ")} Target muscles: ${exercise.muscleGroups.joinToString(", ")} Suggest ONE simpler/alternative exercise that targets the same muscles. Return JSON: {name, sets, reps, restSeconds, muscleGroups: [], notes} """ val response = openAIClient.chat( model = "gpt-4o-mini", messages = listOf(Message("user", prompt)), responseFormat = ResponseFormat.JsonObject ) return json.decodeFromString(response.content) } How the AI assistant determines rest days
The assistant should recommend not training when needed. If HealthKit shows a drop in HKQuantityType.heartRateVariability or sleep under 6 hours, the plan shifts to stretching or active recovery.
func shouldRecommendRestDay(healthData: HealthSnapshot) -> Bool { return healthData.sleepHours < 6.0 || healthData.restingHeartRate > healthData.averageRestingHR * 1.1 || healthData.hrvTrend == .declining } This is not an AI query—a simple heuristic from native data. No LLM needed here.
How to set up a profile for accurate recommendations
To get the most relevant plans, the user must enter their data correctly. For example, if the goal is weight loss and the level is advanced, the assistant will generate a high-intensity program focused on calorie burn. If the user has a knee injury, all squats and lunges will be excluded. We recommend filling all fields including available equipment—this improves selection accuracy by 50%.
What's included in development
- Architecture: HealthKit/Health Connect synchronization, profile storage, workout cache.
- Plan generation: prompt engineering, JSON response validation, LLM error handling.
- Adaptation: exercise substitution triggers, rest timer, rule-based adjustments.
- UI/UX: profile screen, workout card, video demonstrations, "Too hard" button.
- Testing: unit tests, A/B conversion test (targeting 20% retention improvement), TestFlight beta.
- Deployment: App Store and Google Play publishing, push notification setup (APNs/FCM).
- Documentation: data schema, heuristic descriptions, prompt update instructions.
In addition, we audit your current app and propose the optimal integration architecture. Reach out for a consultation—we'll show how an AI assistant can boost user engagement.
Estimated timeline
| Stage | Duration |
|---|---|
| Profile and data collection | 1–2 weeks |
| Plan generation (basic) | 3–5 days |
| Adaptation during workout | 1–2 weeks |
| HealthKit/Health Connect integration | 2–3 days |
| UI/UX and testing | 2 weeks |
| Total: MVP | 4–6 weeks |
Pricing is determined individually based on integration complexity and required functionality. Our engineers hold Apple and Google certifications and have hands-on experience with HealthKit and Health Connect. Contact us to discuss your project—receive a consultation on AI assistant integration today. Get a cost estimate for your project—submit a request.