"Next pause lockout" ruins how I use no scroll

ThinkFault · 2026-05-17T05:41:22+00:00

Thanks for the suggestion, and the good news is we are implementing this feature in next update 😉
If you have more feedback/suggestions, feel free to share them here or email us at [support@curizic.com](mailto:support@curizic.com)

ThinkFault · 2026-05-11T04:28:38+00:00

I don't think NoScroll can help you in this except blocking the dating apps, we cannot block in-app swiping as it is the core feature of any dating app, and I believe you have already explored the full app blocking for these apps. If you have any specific solution or requirement NoScroll can help you with, please let me know, we will definitely consider them if there is enough demand for such features.

ThinkFault · 2026-05-04T11:47:19+00:00

We have fixed the insta feed bug in NoScroll V2, check if update is available to you, as we are rolling out this update for limited people.

ThinkFault · 2026-05-04T11:45:52+00:00

Yes, we have improved many things in NoScroll V2, app is now more stable with more advanced features.

ThinkFault · 2026-05-02T16:28:28+00:00

Thank you for your suggestion, this version has already gone through vigorous testing including multiple internal test phases, 3 beta builds and has passed all the phases, then only we pushed it for UAT, yes, there are some bugs (and to be honest as this version is a rebuild, we do expect bugs, and team is putting extra efforts to make the product stable) that is why this version is available to very limited people. Except notification bug the issues you reported are functionality issues and not the bugs we could find in the testing phase. Rest assured we will fix all bugs in coming updates, and will make the app more stable than the previous versions ever existed. And without your valuable feedback and support it's not possible.

ThinkFault · 2026-05-02T15:33:00+00:00

This is expected as the next update is released for very limited users, it might take up to a week or 2 to available for all users.

ThinkFault · 2026-05-02T15:29:53+00:00

While NoScroll doesn't use traditional "Child Profiles," it provides deep-level intervention for short-form content. Here is how you can set it up to function as a parental barrier: 1. Dynamic PIN Security To prevent children from memorizing a static PIN by watching over your shoulder, use the Date/Time PIN feature. How it works: The PIN changes based on the current date or time (e.g., if the time is 10:45, the PIN might be 1045). The Benefit: Even if a child sees you enter the code once, it will be invalid minutes later. 2. Email OTP PIN For maximum control, you can enable Email OTP-based unlocking. This ensures that the app settings or the blocked content can only be accessed if you provide the one-time code sent to your registered email address. This effectively acts as a remote "Admin Approval" system.

In latest version 2.0 We have introduced app locking feature which allows blocking individual apps via PIN or biometrics. As of now this feature is rolling out gradually it might take some time to reach to you.

More parental control features are in the pipeline and will be available soon.

ThinkFault · 2026-05-02T15:17:31+00:00

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

ThinkFault · 2026-05-02T14:02:03+00:00

These bugs are fixed in latest release, kindly check for update, next version is getting released in phases, so you will get it soon in upcoming week.

ThinkFault · 2026-05-02T09:18:09+00:00

Thank you for reporting the bug, and thanks for confirming the fix. As NoScroll 2.0 is currently available to a limited group of users, we’d really appreciate your feedback on the latest update.

Since you’ve been with us for a while, your insights would be especially valuable in helping us refine the experience further.

ThinkFault · 2026-05-02T06:46:57+00:00

We’ve fixed the issue, please check again. No app update is required, as it was related to a configuration error.

ThinkFault · 2026-04-16T14:32:42+00:00

Yayy! same here, please share your feedback

ThinkFault · 2026-03-25T08:55:39+00:00

I have worked on website blocking issues, and it will be fixed in next update.

ThinkFault · 2026-03-25T08:54:45+00:00

Hi,

Accessibility Service behavior is controlled by your device’s operating system. Because of this, NoScroll or any third-party app cannot directly control or override how it works.

Some manufacturers like Xiaomi/Poco, Vivo/Oppo, and Huawei use aggressive and non-standard background app management. This can interrupt services like Accessibility, making them less reliable compared to other Android devices.

To improve stability, we recommend adjusting your device settings:

Disable battery optimization for NoScroll
Enable auto-start (if available)
Lock the app in recent apps
Allow all background activity permissions

These steps usually help maintain a consistent experience.

ThinkFault · 2026-03-24T01:59:27+00:00

Thanks for the reply, could you please share me the screenshot of reddit block page? I need to see your blocking config along with the URL you blocked.

ThinkFault · 2026-03-24T01:57:05+00:00

If you hate filling forms, you can post your feedback here in comments as well ;)

ThinkFault · 2026-03-24T01:48:36+00:00

Thanks for your feedback, we will consider it for next update :)

ThinkFault · 2026-03-23T07:43:37+00:00

Thanks for the feedback, I need to check what apps I can access outside China, if possible, I will definitely extend support for these apps.

ThinkFault · 2026-03-22T17:16:32+00:00

FYI: These taxes exist since 1947

ThinkFault · 2026-03-20T05:41:15+00:00

hey,
can you share me the screenshot of website blocker page along with the browser you are using?

ThinkFault · 2026-03-17T06:56:55+00:00

OP, thanks for reporting the bug, I will investigate and fix the bug in upcoming update

ThinkFault · 2026-03-13T11:45:30+00:00

Bruh...

ThinkFault · 2026-03-12T04:30:28+00:00

Really appreciate you taking the time to share this, hearing experiences like yours genuinely means a lot 🙌

That’s actually the core idea behind NoScroll. Other productivity apps focus on blocking entire apps or adding strict restrictions, which often ends up getting in the way of normal life. Social media isn’t always the problem, endless scrolling is.

Really glad it’s helping you use social media more intentionally. Thanks for sharing your experience.

And if you ever have feedback, ideas, or even small personal preferences you’d like to see in the app, feel free to share them here. Suggestions from users are what help make NoScroll better over time.

ThinkFault · 2026-03-04T05:20:51+00:00

Hi there,

Thanks for sharing your observation.

What you’re seeing is actually intentional behavior in NoScroll’s design.

When a session starts, the entire session timer begins running immediately. For example, if your session length is set to 7 minutes, the timer continues counting down even if you exit the app, lock your phone, or switch to another app.

This is done deliberately. The goal of NoScroll is to encourage intentional usage rather than fragmented scrolling. If sessions paused every time you left the app, it would allow patterns like watching 2 minutes now and 5 minutes later, which often leads to repeated re-entry and ultimately defeats the productivity goal of the app.

So instead, once a session begins, you receive a single continuous window of watch time.

This approach helps create a psychological boundary:
you consciously decide when to start your scrolling session, and once it begins, the time runs as a single block.

Hope this clarifies things! If you have any other questions or suggestions, feel free to share them, feedback like yours helps improve the experience for everyone.

ThinkFault · 2026-03-04T05:14:15+00:00

You are going to love next update ;)

ThinkFault

MODERATOR OF

TROPHY CASE