BloqueApp¶
BloqueApp helps an adult make intentional time for selected apps, with local Android restrictions and optional partner-approved access. This site explains how to use it, how its parts fit together, and what it can and cannot do. The app interface is in English; documentation is available in English and Spanish.
Choose a reading path:
- Using the app: Start with the practical guide, then look up shared concepts, terms, and current limitations.
- Software engineering: Read architecture, algorithms, security, and tools. The shared concepts page connects these topics to user-visible behavior.
- Computer-science review: Begin with architecture and algorithms, then follow the concept links to the user workflows and their constraints.
Use the language selector to read the same topics in Español. UI labels and protocol names remain as they appear in the product.
What BloqueApp does¶
For a quick visual tour: everyday choices → approval flow → local access decisions. For initial setup, see Device Owner enrollment and pairing.
Android applies locally saved rules to selected apps. A person can explicitly start a session that spends credit from a shared group time bank, or request a separate fixed-duration allowance from a partner. Sleep rules prevent bank access; a sleep exception must be explicitly requested and approved. Once verified and activated, saved local protection can continue without an internet connection.
The approver uses a web page and can receive browser notifications. The server stores requests and decisions and issues signed allowances. A notification is a prompt to review a request; it is not approval or access authority.
Read by topic¶
The public product site maintains the current product description, terms, privacy policy, payment and refund information and support contact. Those pages cover BloqueApp specifically. Payments are currently unavailable. Before enabling Wompi or another processor, the operator must update those pages for the actual recipient, pricing, payment data, delivery and refunds; the present preview is not an active checkout.
- Guide — bank sessions, partner allowances, sleep, requests, setup, and recovery.
- Concepts — canonical explanations of bank credit, allowances, sleep, policy, requests, and offline behavior.
- Glossary — terms used consistently across the site.
- Limitations — supported boundaries and unfinished capabilities.
- Architecture — component boundaries and data flow.
- Algorithms — policy evaluation, usage accounting, and complexity assumptions.
- Security — authorization, signatures, privacy, and threat boundaries.
- Tools — implementation technologies and engineering workflow.