Build your own Strava.

# Build an original app inspired by Strava

You are an experienced mobile product designer and mobile engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Android. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original Android running and cycling log called Milepath, inspired by Strava. It is for individuals recording their own outdoor activities and reviewing a private history. The primary journey is granting location access, starting an activity, pausing or stopping, and reopening its real recorded route and summary. Deliver a native Android Studio project; a map with invented points does not satisfy the recording journey.

## Design
Use an original high-contrast recording screen with large start, pause, resume, and finish controls. Show elapsed active time, distance, location accuracy, and recording status at a glance. Make the map secondary to controls, display a persistent recording notification, and explain gaps honestly. Provide accessible labels, outdoor-readable text, and confirmations that do not interfere with pausing.

## Features
1. Activity recorder: choose run or ride, request location permission in context, and record timestamped coordinates only during an explicit session. Handle approximate access, unavailable GPS, and permission denial without fabricating a route. Manual activity logging remains available.

2. Lifecycle: start the supported Android location foreground service while the app is visible, declare required service types and permissions, and provide notification actions. Keep the active session durable across screen lock; show an interrupted state after process loss rather than assuming recording continued.

3. Metrics: calculate distance from validated points and active duration from pause intervals. Filter implausible jumps using a documented rule, retain accuracy metadata, and avoid accumulating distance during pauses. Show units and rounding consistently.

4. History: save a title and optional notes, browse activities by date and type, inspect the recorded polyline and splits, edit metadata, and delete an activity with confirmation. Work offline, including summaries; identify when a background map needs internet.

5. Portability: export an activity as standards-based GPX through the native share sheet and import a bounded user-owned GPX for viewing. Validate coordinates and file size. Keep imported routes distinct from activities actually recorded by the app.

## Tech stack
Use Kotlin, Jetpack Compose, Room, and Android location APIs or a maintained location provider. Isolate the recorder in a foreground service and use a suitable map SDK under its terms, with attribution and server-safe credential restrictions where applicable. Provide the Gradle project, manifest, emulator route fixture, and installation instructions. Target current SDK behavior using official permission documentation. Do not build a WebView shell or require Strava credentials, APIs, or scraped activity data.

## Data & behavior
Activity {id, sport, startedAt, endedAt, state, title, notes, distanceMeters, activeMillis}; TrackPoint {activityId, sequence, latitude, longitude, altitude, accuracyMeters, recordedAt}; PauseInterval; RecordingCheckpoint; ImportedRoute. Persist batches and checkpoints transactionally, recompute summaries from source points, and stop location subscriptions on finish/delete. Store sensitive location history locally by default, expose export/delete, and ensure diagnostics do not log exact coordinates.

Acceptance checks and scope:
Record a deterministic emulator route, pause while moving, resume, lock the screen, and verify GPX points plus distance after reopen. Test a GPS jump, permission revocation, approximate location, duplicate finish, service stop, and process interruption. Verify foreground-service behavior on a real Android device when available and state any untested battery restrictions. Exclude social feeds, segment leaderboards, live public location sharing, wearables, coaching, and claims of navigation or emergency reliability.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.