Why does yeshcube develop Distraction-Free Apps for the attention economy?

Distraction-Free Apps is the design criterion yeshcube uses to develop applications centered on a defined function, with limited interruptions and without mechanisms intended to extend usage artificially.

The principle begins with a basic consideration: attention is a limited resource. An application may support a task while also introducing notifications, unnecessary journeys, stimuli or design decisions that compete with the person’s main purpose.

The criterion applies to the apps that accompany the hub’s products and programs, where the screen is an instrumental step. It does not describe a yeshcube position on digital design in general, and it coexists with solutions that need an extensive visual interface when the task requires one.

Distraction-Free Apps defines a design direction. Effectiveness, accessibility and effects on wellbeing require assessment for each application, population and context.

The attention economy

Many digital platforms generate value through advertising, subscriptions, purchases or data processing. Some of these models use time spent, frequency of use and interaction as performance indicators.

This structure can encourage functions intended to sustain activity:

• Frequent notifications.
• Autoplay.
• Infinite scrolling.
• Rewards for returning each day.
• Visible social metrics.
• Continuous recommendations.
• Interruptions intended to recover a user.
• Processes that make leaving a function or service difficult.

The presence of these functions does not establish manipulative intent by itself. Assessment requires examination of purpose, context, presentation and the effect on a person’s ability to decide.

The European Commission uses the term dark pattern for design decisions that deceive, manipulate or materially impair a person’s capacity to make free and informed decisions. The Digital Services Act prohibits these practices for services within its scope.

Interruptions and attention

A brief notification may divert attentional resources even when the person does not open the application.

An experiment published in 2015 found that receiving mobile-phone notifications affected performance during an attention-demanding task. The effect appeared without direct interaction with the device, supporting the hypothesis that the signal may activate thoughts unrelated to the main activity.

The result relates to a specific experimental task. It does not establish that every notification produces lasting impairment or a health problem.

Real-world impact depends on several factors:

• Frequency of interruption.
• Relevance of the alert.
• Difficulty of the main task.
• Timing.
• Ability to postpone it.
• The person’s situation.
• Time required to recover context.

Responsible design should consider these factors before adding reminders and alerts.

Context switching and cognitive load

Moving between tasks requires a person to leave one mental representation and reconstruct another.

For simple activities, the cost may be limited. For complex work, returning may require recalling decisions, recovering information and finding the exact point where the interruption occurred.

An application can reduce this load through:

• Grouped alerts.
• Focus modes.
• Automatic state saving.
• Brief confirmations.
• Clear points for resuming.
• Granular notification settings.
• No interruption during sensitive processes.

The objective is to protect task continuity, particularly where reading, reflection, learning, creativity or emotional regulation is involved.

Problematic use and mental health

Research has identified associations between some digital-use patterns and anxiety, depression, stress, sleep difficulties or lower perceived wellbeing.

These associations require cautious interpretation. Intensive use may contribute to a problem, reflect an existing difficulty or form part of a two-way relationship.

Screen time alone also does not describe the quality of an experience. A family video call, educational task, medical consultation and passive scrolling session may take the same time while serving different purposes.

A useful assessment should examine:

• The activity being performed.
• The need it is intended to address.
• Whether the person retains control over the session.
• What occurs before and after use.
• Whether the application displaces sleep, relationships or responsibilities.
• Whether signs of dependence or distress appear.
• Which groups face greater risk.

Distraction-Free Apps does not assume that reducing usage time automatically improves psychological wellbeing. The criterion aims to remove unnecessary stimuli and assess outcomes linked to each product’s purpose.

Attentional autonomy

Attentional autonomy describes a person’s capacity to decide where, when and for how long to direct attention.

An interface may support this capacity through clear information, understandable options and accessible exits. It may weaken it by hiding consequences, introducing artificial urgency or making an interaction difficult to end.

Consumer-protection authorities have documented patterns such as misleading buttons, complex cancellation processes, fake countdowns, confusing privacy options and unnecessary data collection.

These practices may affect purchases, subscriptions, privacy, consent and use of time.

The criterion applies autonomy across the complete product journey:

• Session initiation.
• Configuration.
• Permissions.
• Data use.
• Alert activation.
• Pausing.
• Completion.
• Cancellation.
• Information deletion.

Design principles

Defined purpose

Each application should state the need it addresses.

Secondary functions require a clear relationship with that purpose. Content, metrics and journeys that do not contribute to the objective may increase load and reduce comprehension.

A defined purpose also supports evaluation. The relevant question is whether the person completed the task safely and understood the process.

Proportionate interaction

Appropriate duration depends on the function.

Starting an experience, recording a preference or configuring a device may require a brief interaction. Learning a skill, completing an assessment or reviewing complex information may take longer.

Distraction-Free Apps does not impose a universal duration. Design should use the necessary steps and provide a recognizable end point.

Contained visual hierarchy

Visual design should provide orientation without competing for attention.

This may include:

• Legible typography.
• Sufficient contrast.
• A limited number of primary actions.
• Animations linked to a function.
• No persistent decorative movement.
• Colors suited to the context.
• Spacing that supports reading.
• Understandable states and errors.

A restrained palette does not guarantee a distraction-free experience. Structure, content, transitions and product decisions carry equal weight.

Justified notifications

Every notification should respond to an identifiable need.

Before adding one, the team should define:

• Which event triggers it.
• Which benefit it provides.
• What happens when it is not sent.
• Whether alerts can be grouped.
• Whether sound or vibration is necessary.
• How it can be disabled.
• How long it remains useful.
• Which groups may experience adverse effects.

Commercial or return prompts should remain separate from alerts relating to safety, operation or an explicit request.

Visible completion

A session needs an end point.

The product may indicate that an action is complete, save the result and allow the person to leave without automatically presenting a chain of related content.

Visible completion reduces uncertainty about unfinished work and supports return to the main activity.

Configurable control

People should be able to adjust:

• Alert frequency.
• Sound and vibration.
• Autoplay.
• Personalization.
• Data collection.
• History.
• Memory.
• Social functions.
• Reminders.
• Account deletion.

Default settings should reflect the level of risk and intended audience. Products for children or vulnerable people need stronger measures.

Practices incompatible with the criterion

Functions whose primary purpose is to increase retention or return artificially are kept out of the design of these applications.

This exclusion applies to the applications the hub develops. It does not certify third-party applications that integrate its technologies, which follow their own design criteria.

Scrolling without end points

Infinite scrolling removes natural boundaries between blocks of content.

It may serve a purpose in some exploration tasks, although mechanisms are still required for orientation, stopping and context recovery.

In wellbeing, learning or regulation products, a finite structure commonly supports progress comprehension and completion.

Chained autoplay

Autoplay can reduce steps in a requested sequence.

Where it starts successive content without a clear decision, it may extend a session and make disengagement more difficult.

Its use should be optional, predictable and reversible.

Rewards detached from the objective

Points, badges, streaks and rankings may support some activities.

They may also move motivation away from the underlying objective and toward maintaining a metric.

Their inclusion requires justification of the behavior being reinforced, supporting evidence and the consequences of interrupting the sequence.

Losing a streak should not create guilt, disproportionate punishment or loss of essential functions.

Artificial urgency

Countdowns, expiring content and scarcity messages may pressure a decision.

Urgency should be used only where a real and explainable limitation exists.

Difficulty leaving or canceling

Rejecting, pausing or canceling should be as understandable as activation.

Hidden controls, irrelevant steps and guilt-inducing messages compromise freedom of decision.

Application across the yeshcube ecosystem

Distraction-Free Apps operates as a cross-cutting criterion for interfaces associated with yeshcube products and solutions.

Specific implementation depends on each product’s development status and confirmed functions. The principle may guide:

• Starting an experience.
• Configuring a device.
• Selecting content.
• Playback control.
• Privacy management.
• Voluntary recording of information.
• Reviewing results.
• Ending a session.

The criterion is particularly relevant to audio-first and zero-screens products. In these systems, an application may operate as a configuration or control layer while the primary experience occurs through sound, voice, physical interaction or the surrounding environment.

A visual interface remains appropriate where it provides accessibility, precision, transparency or control.

VVAVVE

VVAVVE is conceived as a portable audio-based experience.

An associated interface may apply Distraction-Free Apps principles to support selection and control without requiring sustained visual attention during the experience.

Specific functions, step counts, automatic closure and available metrics should be described only once implemented and verified.

The design criterion may establish these objectives:

• Direct access to primary functions.
• Visible pause and completion controls.
• No additional content during the experience.
• Configuration separated from the moment of use.
• Notifications that can be disabled.
• Clear information about data and permissions.

These objectives require validation through usability testing and incident monitoring.

Somia

Somia is the yeshcube artificial-intelligence architecture that may be integrated into yeshcube or third-party products.

Interfaces associated with Somia may apply Distraction-Free Apps through brief journeys, understandable controls and the absence of stimuli that compete with the purpose of the specific solution.

The architecture does not determine duration, modality or interface by itself. Each integration needs to define:

• The primary channel.
• The role of the screen.
• Available functions.
• Required data.
• Interaction limits.
• Exit mechanisms.
• Safety measures.
• The applicable evaluation.

Evaluation measures

The success of a Distraction-Free App should not depend exclusively on time spent, return frequency or interaction count.

Measures should relate to purpose:

• Task-completion rate.
• Time required to complete the function.
• Errors and abandonment.
• Interface comprehension.
• Number of interruptions.
• Enabling and disabling alerts.
• Use of pause or exit functions.
• Accessibility incidents.
• Task-related satisfaction.
• Reported adverse effects.
• Achievement of predefined objectives.

A brief session may indicate efficiency or abandonment. A long session may represent friction or an activity that genuinely requires time. Interpretation needs context.

Evidence and validation

Distraction-Free Apps proposes a general design hypothesis: reducing stimuli and retention mechanisms unrelated to purpose may improve control, clarity and the ability to complete a task.

The hypothesis needs assessment for every product.

A validation process may include:

1. Defining the purpose and intended users.
2. Identifying potential sources of distraction.
3. Reviewing notifications, rewards and journeys.
4. Conducting accessibility testing.
5. Evaluating usability.
6. Comparing interface alternatives.
7. Recording errors and interruptions.
8. Measuring task-related outcomes.
9. Monitoring unexpected effects.
10. Reviewing evidence before wider use.

Evidence obtained from one application cannot be transferred automatically to another with a different function, population or context.

Solutions incorporating these applications document their maturity through the ERL scale, which places the transfer threshold at ERL-3.

Regulation and responsible design

The Digital Services Act establishes obligations concerning dark patterns, the protection of minors, transparency and systemic risks for certain platforms.

Legal scope depends on the service type, scale, function and use context.

Other relevant areas may include:

• Consumer protection.
• Data protection.
• Accessibility.
• Digital services.
• Advertising.
• Childhood.
• Medical devices.
• Sector-specific legislation.

Distraction-Free Apps is an internal design criterion. Applying it does not replace legal analysis or establish regulatory compliance by itself.

Limits of the criterion

Reducing stimuli may create clearer interfaces and may hide functions where the architecture becomes too minimal.

Removing reminders may protect against interruption and may reduce the usefulness of an application that needs to alert a person about an appointment, medication or risk.

Avoiding social metrics may reduce comparative pressure and may limit community functions that offer support under specific conditions.

A simple application may remain manipulative through pricing, permissions, language or cancellation processes.

The criterion is not universal within the hub either. Some tasks require comparing items, reviewing series of data or editing precisely, and for those an extensive visual interface is the appropriate option.

Distraction-free design requires balance between reduction, accessibility, sufficient information and capacity for control.

Relationship with the other design criteria

Distraction-Free shares a purpose with audio-first and zero-screens, and each answers a different question.

Audio-first decides which channel is primary in an experience. Zero-screens decides whether a screen forms part of the pathway. Distraction-Free decides, where a screen exists, which mechanisms are kept out of it.

All three apply per product and per context. None describes the hub’s position on technology in general, and none establishes by itself the effectiveness, accessibility or safety of a solution.

An application should support a function, communicate what is necessary and allow completion. The criterion shifts evaluation from retention toward outcome, and requires examination of whether a notification, reward, recommendation or screen provides verifiable value.

References

Stothart, C., Mitchum, A. and Yehnert, C. (2015). The Attentional Cost of Receiving a Cell Phone Notification. Journal of Experimental Psychology: Human Perception and Performance, 41(4), 893-897.

European Commission. The Digital Services Act.

European Commission. Digital Services Act: Questions and Answers.

Federal Trade Commission. (2022). Bringing Dark Patterns to Light.

Discover the Allies program →

Fill in the contact form →