Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #7,000 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
Stride Mix is a self-reported web application that dynamically generates music playlists for running intervals based on an energy curve derived from interval timing and effort levels. It uses YouTube playback and allows users to customize tracks per phase of their workout.
What changed
The project was submitted as part of a hackathon, indicating it is in early development or prototype form. No commercial traction, revenue, or customer data are evidenced.
Single most important open question
Is there any evidence that the product has been used beyond the author’s own testing or demo environment?
What The Product Actually Is
The description states:
- Stride Mix is a web app built with HTML, CSS, and vanilla JavaScript.
- It reads interval plans as an energy curve where each phase maps to a 1–5 effort level.
- It builds a queue of music tracks that match the effort level of each interval phase.
- The app uses YouTube for playback via embedded player.
- It includes a timer with coaching cues and allows users to edit intervals, reorder phases, or swap tracks.
- It supports drag-and-drop mini player and search functionality via YouTube.
Inference The product is a single-page application (SPA) that runs in the browser without build steps or frameworks. It uses serverless functions for YouTube API access and relies on pre-defined audio IDs for playback in demos.
Positioning & Claim Evolution
The description states:
- The app addresses the “rhythm problem” of regular playlists not matching effort levels during running intervals.
- It aims to provide music that moves with the workout — high energy during pushes, calm during recovery.
- It is described as not trying to beat-match cadence to the millisecond but instead aligning energy with effort.
Inference The positioning is centered on solving a specific pain point in interval training: mismatched music and effort. The app positions itself as an intelligent playlist generator for runners, not a general-purpose music player or fitness tracker.
Target Customer & ICP
The description states:
- The target user is someone who runs intervals and struggles with playlists that don’t match their effort levels.
- It is aimed at runners who want to avoid using their phone mid-run and prefer an app that adapts to their workout rhythm.
Inference The ICP appears to be runners doing interval training, particularly those who are tech-savvy or interested in optimizing their workouts with digital tools. No specific demographics or user segments are detailed.
Business Model & Pricing Evidence
Not evidenced.
Technical & Delivery Signals
The description states:
- Built with HTML5, CSS3, JavaScript (vanilla), SVG, PWA, responsive design, and Web Speech API.
- Uses the History API for URL slugs (/build, /mix, /run).
- No build step or framework used — dependency-free.
- Playback runs through YouTube player; no audio mixing or overlapping.
- Serverless function (api/search.js) handles YouTube search with a free key.
- Core is static-hosted with SPA fallback server.
Inference The technical stack suggests a lightweight, self-contained web app with minimal dependencies and a focus on performance and portability. The use of YouTube playback and no audio mixing implies a low-risk, scalable approach to music delivery.
Traction & Maturity Signals
Not evidenced.
Competitive Context
Not evidenced.
Key Risks & Red Flags
- The product is described as a hackathon submission with no evidence of commercial traction or user adoption.
- It relies on YouTube playback and lacks a rights-cleared catalog, which may limit scalability or monetization.
- No mention of data privacy, user retention, or long-term engagement strategies.
- The app’s reliance on pre-defined audio IDs for demo purposes suggests it is not yet production-ready.
Diligence Questions To Ask The Founders
- Has the product been tested by users beyond the author's own use?
- Are there any plans to monetize or scale the service?
- What are the limitations of relying on YouTube playback for music delivery?
- How is the energy curve calculated, and how does it handle edge cases like very short intervals?
- Is there a plan to integrate with Spotify or other music platforms?
Investment/Partnership Verdict
Not evidenced.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.