Shufflow

The description states that Shufflow is an AI-native productivity app. It includes:

• A Flow Cube as a visual symbol of workflow.
• Swipe-based task switching: right to move to a recommended next task, left to return to the previous one.
• An adaptive timer and visual feedback system, redesigned around this interaction model.
• The use of AI tools (GPT-5.6 and Codex) in both research and implementation phases.

The app is described as being built with codex, gemini, gpt, loveable — though only GPT-5.6 and Codex are mentioned in the narrative.

Inference: The product appears to be a task management or productivity tool that attempts to reduce cognitive load by using simple, fidget-inspired gestures for task switching, rather than traditional UI elements like buttons or dropdowns.

The description states that Shufflow is an ADHD-friendly productivity app. It positions itself as helping users stay productive even when attention shifts — a claim rooted in user insights from interviews.

It also claims to be AI-native, using AI tools like GPT-5.6 and Codex for both design and development.

The evolution of the positioning appears to have started with:

• User interviews highlighting the use of fidget toys.
• A decision to integrate fidget-inspired movements into digital interaction.
• Use of AI to research, prototype, and refine these interactions.

Inference: The positioning evolved from a user insight into a product concept that blends accessibility with AI-driven design. It is not yet clear if this has been validated beyond the hackathon context.

The description states that Shufflow is designed for users with ADHD, who experience attention shifts and may benefit from a system that adapts to their working patterns.

It also mentions that the team interviewed users with attention difficulties, suggesting an initial focus on this group.

Inference: The initial ICP appears to be individuals with ADHD or attention-related challenges. However, there is no evidence of segmentation beyond this group or how they are defined in terms of behavior or demographics.

The description does not provide any information about:

• Revenue model
• Pricing structure
• Monetization strategy
• Customer acquisition costs
• Unit economics

Not evidenced

The project was built during a Build Week hackathon, using AI tools like:

• GPT-5.6 for research and idea generation.
• Codex for implementation and codebase understanding.

It includes:

• A Flow Cube visual element
• Swipe-based task transitions (right to advance, left to retreat)
• Visual feedback tied to these interactions
• Integration of new gestures with existing task states

The team used a short-cycle feedback loop, testing versions with users and iterating quickly.

Inference: The technical approach is AI-assisted, iterative, and user-centered. It suggests a lean development process but lacks evidence of scalability or long-term architecture planning.

The description states:

• Shufflow was submitted to the OpenAI 2026 hackathon
• The team has 3 members
• They are onboarding early testers
• They plan to develop a user-ready version over the next two months

There is no evidence of:

• Revenue
• Customer base
• Product adoption
• Market traction
• Metrics on user engagement or retention

Not evidenced

The description does not mention any competitors.

It does not state whether Shufflow is positioned against existing productivity tools (e.g., Notion, Todoist, Toggl, etc.), nor does it describe how its fidget-inspired interaction model differentiates from those.

Not evidenced

• No revenue or customer data: The project is in early development and lacks any evidence of traction.
• Unverified claims: All claims about user needs, AI use, and product effectiveness are self-reported.
• Limited team size: Only 3 members, which may limit execution capacity.
• Unclear scalability: No mention of how the app would scale beyond a hackathon prototype.
• No pricing or monetization strategy: The business model is not described.
• Unproven user feedback loop: While they mention testing with users, there is no evidence of actual early adopters or measurable outcomes.

Inference: The project is in a very early stage and lacks commercial validation. It is unclear whether the interaction model will be effective beyond the prototype phase.

1. What specific user insights from interviews led to the fidget-inspired interaction system?
2. How many users have you tested with, and what were their feedback cycles like?
3. Have you validated that the swipe-based task switching improves productivity or reduces cognitive load for ADHD users?
4. What is your plan for monetization and customer acquisition beyond the hackathon?
5. How do you intend to scale beyond a 3-person team?
6. Are there any technical limitations or scalability concerns with the current AI-assisted development approach?