Every Apple Feature Hiko Uses to Calculate Your Real Calorie Burn

Most fitness apps use a single Apple framework — HealthKit — and call it integration. Hiko uses more than 15 Apple frameworks and APIs working together to deliver calorie calculations based on real metabolic science. Every framework serves a specific purpose in the LCDA equation pipeline. Here is what each one does.

HealthKit — The Foundation

HealthKit is where Hiko gets the physiological data that makes individualized calorie calculation possible.

Hiko reads: body mass, height, lean body mass, biological sex, date of birth, resting heart rate, heart rate variability, and sleep data. Each of these variables feeds into the LCDA equation or the resting metabolic rate baseline. A 90 kg person with 20% body fat burns calories at a different rate than a 90 kg person with 35% body fat — HealthKit provides the data to distinguish between them.

Hiko writes: completed workouts, active energy burned, walking and hiking distance, and GPS routes. Every workout Hiko records appears in the Health app and is available to any other app the user authorizes.

HKWorkoutSession manages the live workout on Apple Watch. If the app crashes mid-workout or the Watch restarts, the workout session recovers automatically. No data is lost.

All HealthKit processing happens on-device. Hiko never uploads health data to a server.

Core Location and MapKit — Terrain Intelligence

GPS does more than draw a line on a map. Hiko uses Core Location for three distinct calculations: speed (meters per second for the LCDA velocity term), elevation change (for grade calculation), and geographic position (for terrain lookup).

The terrain system uses reverse geocoding against OpenStreetMap surface data to detect what you are walking on. Hiko maps GPS coordinates to one of 9 terrain types — paved, compact dirt, gravel, grass, loose dirt, forest trail, snow, mud, and sand — each with a validated Soule and Goldman terrain coefficient. When you walk from pavement onto a gravel trail, Hiko detects the surface change and adjusts the LCDA equation in real time.

MapKit renders your route after the workout with terrain segments color-coded by surface type.

Core Motion — Movement Science

The barometric altimeter in Core Motion provides continuous altitude data independent of GPS. Hiko fuses barometric altitude with GPS elevation to calculate grade — the slope you are walking on — which is one of the largest variables in the LCDA equation. A 10% uphill grade can double your calorie burn compared to flat ground at the same speed.

CMDeviceMotion delivers sensor-fused accelerometer and gyroscope data. Hiko uses this for cadence detection, step counting validation, and motion state classification.

Coming: CMBatchedSensorManager will enable arm swing amplitude analysis on Apple Watch, feeding a Core ML model trained to classify gait patterns. Arm swing data can distinguish between loaded and unloaded walking gaits, improving the accuracy of the load carriage calculation when the user does not manually enter pack weight.

WatchKit and SwiftUI — Native Watch Experience

Hiko is a fully standalone watchOS app. It does not require the iPhone to be present. You can start a ruck from your wrist, track every metric in real time, and save the workout — all without your phone.

The Digital Crown adjusts pack load weight during a workout. Turn the crown to add or subtract kilograms without stopping. Haptic feedback confirms interval transitions during IWT workouts — a distinct tap pattern tells you when to switch between fast and nikoniko pace without looking at the screen.

All UI on both iPhone and Apple Watch is built entirely in SwiftUI. No UIKit, no storyboards, no Interface Builder files.

App Intents and Siri — Hands-Free Control

Rucking with a heavy pack and trekking poles means your hands are occupied. Hiko exposes 8 App Intents for complete voice control of workouts:

• Start a workout: “Hey Siri, start a ruck with 15 kg in Hiko”
• Change terrain: “Hey Siri, change terrain to gravel in Hiko”
• Check calories: “Hey Siri, how many calories so far in Hiko”
• Adjust load: “Hey Siri, set pack weight to 20 kg in Hiko”
• Toggle poles: “Hey Siri, enable trekking poles in Hiko”
• Check pace: “Hey Siri, what’s my current pace in Hiko”
• Pause workout: “Hey Siri, pause my workout in Hiko”
• End workout: “Hey Siri, end my workout in Hiko”

Every intent works mid-workout. You never need to touch the screen.

SwiftData — Local Persistence

All workout history is stored on-device using SwiftData. Every completed workout — including second-by-second calorie data, terrain segments, grade profile, and heart rate samples — persists locally.

There is no cloud database. There is no sync service. There is no account to create. SwiftData stores everything on the device in a local persistent container. If you delete the app, the workout data in HealthKit remains. If you reinstall, Hiko rebuilds its local history from HealthKit.

WorkoutKit — Structured Training

WorkoutKit enables Hiko to build structured IWT interval plans using Apple’s CustomWorkout API. A standard Shinshu IWT session — 5 sets of 3-minute fast and 3-minute slow intervals — is defined as a structured workout with phase-specific heart rate zone alerts.

These structured plans integrate with Apple’s Workout app for scheduling and appear on the Watch face as upcoming workouts. Heart rate alerts tap your wrist when you drift outside the target zone for each interval phase.

Foundation Models and SpeechAnalyzer — On-Device Voice Intelligence

iOS 26 introduces two frameworks that enable natural language workout control without Siri invocation.

SpeechAnalyzer provides always-on speech detection during workouts. Instead of raising your wrist and saying “Hey Siri,” you speak naturally: “change to gravel” or “five more kilos.” SpeechAnalyzer detects the speech, transcribes it on-device, and passes the text to Hiko’s command parser.

Foundation Models with the @Generable macro provides structured output parsing on Apple silicon. Hiko defines a command schema — terrain changes, load adjustments, workout controls — and the on-device language model parses natural speech into structured commands. “I think this is more like packed dirt” becomes a terrain change to compact dirt. All processing runs on the Neural Engine. No audio or text leaves the device.

Privacy by Architecture

Hiko contains no analytics SDK. No tracking pixels. No ad network frameworks. No server calls during or after workouts. No telemetry of any kind.

Every calculation runs on Apple silicon — the A-series chip on iPhone, the S-series chip on Apple Watch. The LCDA equation, terrain detection, heart rate analysis, and voice command parsing all execute locally. The only network requests Hiko makes are OpenStreetMap tile fetches for terrain data, and those contain no user-identifiable information.

The App Store privacy nutrition label for Hiko reads: Data Not Collected. That is not a policy choice that could change — it is an architectural fact. There is no server to send data to.

The Full Stack

Every Apple framework Hiko integrates and what it does:

Framework	What Hiko Uses It For
HealthKit	Body metrics, workout recording, heart rate, routes
Core Location	GPS speed, elevation, terrain coordinate lookup
Core Motion	Barometric altimeter, accelerometer, gyroscope
WatchKit	Standalone Apple Watch app
SwiftUI	All UI on iPhone and Apple Watch
SwiftData	Local workout history storage
App Intents	8 Siri voice commands for hands-free control
WorkoutKit	Structured IWT interval plans with HR zones
Core ML	Arm swing gait classification on Neural Engine
Foundation Models	Natural language command parsing on-device
SpeechAnalyzer	Always-on voice detection during workouts
MapKit	Route rendering with terrain segment visualization
WidgetKit	Watch complications and iPhone widgets
StoreKit	In-app purchase management

Each framework exists in the stack because it solves a specific problem in the calorie calculation pipeline or the workout experience. Nothing is included for the sake of integration.

Frequently Asked Questions

How many Apple frameworks does Hiko use?

Hiko integrates 14 Apple frameworks and APIs. Each one serves a specific function in the calorie calculation pipeline, workout tracking, or user interaction layer. The full list is in the table above.

Does Hiko work offline?

Yes. All calorie calculations, workout tracking, and data storage work without an internet connection. Terrain auto-detection requires a network connection for OpenStreetMap lookups, but you can set terrain manually when offline. Voice commands via Siri and Foundation Models also work offline — all processing runs on-device.

Is Hiko a native Apple Watch app?

Yes. Hiko is a fully standalone watchOS app built in SwiftUI. It does not require the iPhone to be nearby. You can start, track, and save a complete workout from your wrist, including load adjustment via Digital Crown and interval transitions with haptic feedback.

Does Hiko collect any user data?

No. Hiko’s App Store privacy label is “Data Not Collected.” There is no analytics framework, no tracking SDK, no server to receive data, and no account system. All health data stays in HealthKit on your device. All workout history stays in SwiftData on your device. This is not a privacy policy — it is the architecture of the app.

Why does Hiko need so many frameworks?

Accurate calorie calculation for loaded walking requires body composition data (HealthKit), real-time speed (Core Location), grade from altitude changes (Core Motion), terrain surface type (Core Location with OpenStreetMap), and individualized metabolic modeling. Each framework provides a variable that the LCDA equation needs. Remove any one of them and the calculation loses accuracy.