LockFit

LockFit is an Android app that blocks distracting apps until a user completes a GPS-verified gym workout, granting limited screen time in the form of "digital keys". The app was built by a 15-year-old developer as part of the OpenAI 2026 hackathon. It integrates Google Maps and Google Places APIs to locate gyms, and uses AI tools (Claude, Codex) for development. The description states that it is designed to motivate gym attendance through enforced app blocking.

What changed: The project was submitted as a hackathon entry with no evidence of commercial traction or user adoption.

Single most important open question: Is there any evidence of actual usage, revenue, or customer feedback beyond the author's self-report?

The description states that LockFit is an Android app that blocks distracting apps until a GPS-verified gym workout is completed. After completing the workout, users receive a “key” granting limited screen time on blocked apps. Users can also choose to have between zero and four Jokers per month, which provide temporary access without completing a workout.

Evidence: The author's own write-up describes how it works.

Inference: The app uses GPS verification for gym attendance and integrates with Google Maps/Places APIs.

The author states that the app was inspired by a desire to motivate gym attendance without relying on willpower. It is positioned as a tool that removes choice by blocking social media and other distracting apps until a workout is completed.

Evidence: The "Inspiration" section of the write-up.

Inference: The app aims to combine fitness motivation with digital discipline, using gamification elements like “keys” and “Jokers.”

The description does not state specific customer segments or personas. It implies a general audience interested in fitness motivation and digital self-control, but no explicit ICP is defined.

Evidence: Not evidenced.

Inference: Likely young adults or students who struggle with phone usage and want to build fitness habits.

The description does not mention any pricing model or monetization strategy. It only describes the core functionality of app blocking and screen time allocation.

Evidence: Not evidenced.

Inference: If launched commercially, it might be a freemium model with optional in-app purchases for Jokers or premium features.

The project was built using React Native, Kotlin, and Expo.io. It integrates Google Maps API, Google Places API, and uses AI tools like Claude and Codex for development. The author notes challenges with Google API integration and emphasizes the importance of manual control over code repositories.

Evidence: The "How we built it" and "Challenges we ran into" sections.

Inference: The app is technically feasible but may have performance or scalability limitations due to its early-stage development.

There is no evidence of user adoption, revenue, or customer engagement beyond the author's own account. The project was submitted as a hackathon entry and has not been released on any app store.

Evidence: Not evidenced.

Inference: The app is in an early prototype phase with no commercial traction.

The description does not mention competitors or similar products. It is unclear whether there are existing apps that offer similar functionality (e.g., screen time management, fitness motivation).

Evidence: Not evidenced.

Inference: This could be a niche product in the intersection of productivity and fitness tech, but no competitive landscape is described.

• The app is a hackathon project with no evidence of commercial viability or user feedback.
• It was built by a 15-year-old developer, raising questions about long-term maintenance and scalability.
• No revenue model or monetization strategy is described.
• The use of AI tools for development suggests potential dependency on external services that may not be stable or scalable.

Evidence: Not evidenced.

Inference: Risk of technical debt, lack of user traction, and limited commercial potential due to early-stage development.

1. What is the actual user experience like in practice? Has anyone used it beyond the prototype?
2. How does the GPS verification process work, and what happens if a gym is not detected or verified?
3. Are there any plans to monetize the app, and how do you intend to attract users?
4. What are the technical limitations of the current implementation, and how would you scale it?
5. Is there any feedback from potential users or beta testers?