# A habit app stops repeating itself

Companion to /learn/google-play/long-description/

## Outcome
Write a Google Play description that explains the product clearly and survives a factual review.

Fictional example, not a client result.

## Scenario
DayLoop is a fictional habit app. Its draft repeats “habit tracker” in nearly every sentence, but never explains how a user starts a routine or reviews progress. The team has confused thematic relevance with repetition. A visitor can identify the category and still have no reason to choose this product.

## Reasoning
Outline the questions the description must answer: who it serves, what outcome it supports, how the workflow works and which limitations matter. Use the audience’s language naturally within those explanations. Compare every factual claim with the current product. Avoid writing a list of aspirational features merely because those phrases appear in research.

## Action
Open with a specific supported use case, then describe setting up a routine, recording completion and reviewing the pattern. Group additional features around user jobs. State material limitations clearly where they affect expectations. Read the result aloud and remove repetitive sentences that add no information. A useful final review asks whether a person could explain the app accurately after reading it.

## Trap to avoid
Do not optimise toward a universal keyword-density target. The draft should remain useful to a person evaluating the product. Repetition that weakens clarity is not made persuasive by a spreadsheet percentage.

## Advanced considerations
Treat description work as a message system. The opening, screenshots and onboarding should describe compatible expectations. If each tells a different story, rewrite the brief before polishing individual sentences. Record which passage answers which user question, then remove sections that merely restate the opening. Review localized drafts independently rather than assuming an English structure reads naturally everywhere.

## Exercise
The research map contains “team habits,” but DayLoop has no collaboration feature. Can that phrase be included in a benefits paragraph?

## Suggested answer
Not as a promise of collaboration. Remove the unsupported positioning or clarify the actual individual workflow. A relevant-sounding phrase is not a reason to imply a feature the user will not find.

## Your worksheet

### Audience and primary job
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Opening value proposition
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Core workflow in plain language
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Supporting features with product evidence
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Limitations and claim review
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Final copy owner and release version
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

## A worked description draft for DayLoop
This fictional draft assumes individual routines, step completion and a history view. It is deliberately short because those assumptions do not justify more promises. Expand it only with verified product details that answer a real user question.

Fictional copy exercise, not an approved listing or a claim that this wording improves rankings.
Passage | Example copy | Editorial job
Opening | Build a morning routine you can follow one step at a time. DayLoop lets you arrange your own steps and record each one as you complete it. | Establish the outcome and mechanism
Workflow | Choose the steps that matter to your morning, put them in order and use your routine when you are ready to begin. | Explain how to start
Progress | Review your recorded completions in the history view and use them to reflect on your routine. | Describe a supported feature without promising behaviour change
Boundary | DayLoop is designed for individual routines. It does not provide shared team tracking. | Set expectations for an unsupported adjacent use case

### Edit an inflated sentence into product information
Replace “The ultimate habit tracker that guarantees success” with a statement about the actual action: “Arrange your routine and record completed steps.” The rewrite removes an unsupported outcome and supplies a mechanism. It is not automatically the final headline; compare it with the audience and the rest of the listing before approval.

### Review the description as a system of claims
For each sentence, name the product screen or owner that can verify it. Confirm whether restrictions vary by plan, market or version and disclose material limits accurately. Remove unsupported collaboration, automation or reminder claims rather than assuming that familiar category features must exist. A description can be grammatically excellent and still misrepresent the product.

### Use the available length with purpose
Google currently permits 4,000 characters in the full description; this is a ceiling, not a target. Its guidance discourages repetition and asks for accurate, straightforward copy. Add detail when it resolves a real question. Review the short description separately so the full description develops the message instead of simply duplicating it.

## Continue reading
- /learn/keywords/search-intent/
- /learn/conversion/value-proposition/
- /learn/google-play/short-description/