Rocky

The description states:

• Rocky is a macOS desk companion — a boxer whose physical condition is a live readout of your work state.
• It tracks unread Teams messages, which add weight to Rocky’s stance (e.g., shadowboxing when clean, taking body shots when debt piles up).
• It uses the Accessibility API and Microsoft Graph API to monitor activity and message queues.
• It intervenes when a user is distracted and someone is waiting on them — walking in from screen edge, naming the distraction, identifying who needs you, and delivering a motivational quote.
• It also reacts to system load (CPU, thermal state) with ambient cues.

Inference Rocky is a productivity tool that uses character-based feedback to signal work state and interrupt users only when there is actual message debt, not just screen time.

The description states:

• The product was inspired by the frustration of opening Teams and being overwhelmed by messages.
• It aims to provide a “signal you could read from across the room” without needing to open the app.
• It combines two truths: are you behind on people, and are you actually working right now.

Inference The positioning is that Rocky is a visual and auditory productivity companion that bridges communication overload and focus interruption — not just a distraction blocker but a “work state communicator.”

The description states:

• The product targets users who work in environments with Microsoft Teams, especially those who are overwhelmed by message volume.
• It is built for macOS users, specifically those using desktop apps and managing focus while juggling interruptions.

Inference The target customer is likely a knowledge worker or developer using macOS and Microsoft Teams, who experiences communication overload and seeks a visual indicator of their work state.

Not evidenced.

The description does not mention pricing, monetization, or any business model beyond the hackathon project.

The description states:

• Built with Swift, SwiftUI, Accessibility API, Microsoft Graph API, OAuth2, and other macOS-specific frameworks.
• Uses ActivityMonitor to track frontmost app via NSWorkspace activation events.
• Implements a custom OAuth device code flow instead of using libraries like MSAL.
• Tracks distraction streaks with grace windows and escalating cooldowns.
• Uses a debt score mapped to Rocky’s stance, with smoothing for visual fluidity.

Inference The technical stack is native macOS, with strong integration into system-level telemetry and Microsoft Teams APIs. The architecture is designed to avoid third-party dependencies and is built under tight time constraints.

Not evidenced.

There is no mention of users, adoption, revenue, or any traction metrics beyond the hackathon submission.

Not evidenced.

The description does not reference competitors or market positioning beyond its own claims.

• Prototype-only: The product was built for a hackathon and is described as a prototype with no evidence of further development or traction.
• No monetization model: No pricing, revenue, or business model is mentioned.
• Single-person team: The project has only one member (Osho Kharbanda), which may limit scalability or long-term maintenance.
• Limited scope: Features like multi-account support, replies, and Slack/Gmail integration were cut from v1 due to time constraints.

1. Has Rocky been used beyond the hackathon environment?
2. Are there any users or early adopters who have provided feedback on its utility?
3. What is the plan for monetization or commercialization?
4. How does the team intend to scale beyond a single-person build?
5. Is there any intention to expand beyond macOS or Microsoft Teams?