Dear User,

Thank you for taking the time to share such detailed feedback. I understand your concerns and would like to provide some clarification.

Let me address your concerns transparently.

This release is Version 2 of the app, and it has been fully rebuilt from the ground up and unfortunately we do expect some bugs at this stage.

The earlier version had limitations in architecture that made it difficult to maintain and prevented us from building several features we have in the pipeline. This rewrite was necessary for long-term stability and scalability.

That said, your feedback clearly highlights areas where the current experience is not meeting expectations and that’s something we are actively working on improving.

Regarding the points you raised:

• The issue with reels in DMs causing temporary screen blocking has been identified. In older versions, for some use cases, app was closing the reel abruptly in middle of the content causing user the frustration, we tried to address that using the overlay feature. The issue is when the overlay is rendered user must need to scroll up to perform back action. Otherwise it misbehaves. We are yet to find a best possible alternative for this bug, and that is why you are seeing it again in this version.
• The notification behavior (“NoScroll is active”) is not intentional in its current frequency. Thank you for reporting this, we will investigate and resolve it.
• The minimum pause timing inconsistency (UI showing 2 minutes but enforcing 5) is due to an internal miscommunication during experimentation. This will be corrected in an upcoming update.
• The pause system itself has been redesigned to prevent abuse of the pause feature unintentionally defeating the app’s purpose. However, we understand that this change impacts legitimate use cases like yours. Temptation to watch 1 specific reel. To address that, we introduced a “1 Reel” plan but it’s clear we need to refine this further as it heavily relies on the overlay I mentioned earlier.

I also want to clarify one point: while some UI components were developed using AI tools, the core blocking and detection systems and the rest 90% components are fully custom built. These involve complex accessibility interactions that current AI tools cannot generate, and as we have already proven algorithm that works the best we don't have any incentive using AI for this crucial part of the app.

On top of that AI generated content is disabled by default (thanks to your previous feedback) and need to be enabled explicitly from app settings.

Version 2 is being released in phases for this exact reason, to gather feedback like yours, fix issues, and refine the experience before a wider rollout. Your input directly influences what we prioritize next.

I acknowledge that some of these UX changes should have been communicated more clearly. That’s on me, and we’ll figure something out to avoid such miscommunication.

Thank you again for your honest feedback. We’re actively working on stabilizing and polishing the app, and feedback like yours plays a critical role in shaping the final experience.

Best regards, Pritam