Considerate Software Checklist

No infinite scroll or endless content feeds

Infinite scroll removes natural stopping points, making it harder for users to disengage. Give users a clear end.

No streak mechanics that punish missed days

Streaks that "break" create anxiety and guilt. Show patterns informatively without loss-aversion tactics.

Notifications are opt-in, with clear explanation of what users will receive

Users should actively choose notifications after understanding exactly what they'll get—not be enrolled by default.

Clear "done" states — users know when their task is complete

Help users accomplish their goal and move on. Ambiguous completion states keep people lingering unnecessarily.

No guilt messaging when users leave

"Are you sure? You'll lose progress!" is manipulation. Respect the user's decision to close the app.

Badge counts only for actionable items, not engagement bait

Red badges trigger compulsive checking. Reserve them for things that genuinely need attention.

All prices visible before entering any purchase flow

Users shouldn't have to start a checkout process to learn what something costs.

Subscriptions only when justified by ongoing value

Sync, cloud storage, and active development justify recurring costs. A static utility app doesn't.

Cancellation takes the same effort as subscribing

If subscribing takes one tap, cancelling should too. Hidden cancellation flows are hostile.

Existing users keep access to features they already paid for

Don't charge users twice for the same features. They'll remember.

No fake urgency, countdown timers, or decoy pricing

Psychological pricing tricks manipulate decisions. Let the product speak for itself.

Data stored on-device when possible

Local-first architecture means your data exists even without internet, and you control it completely.

Each feature only collects the data it needs to work

Don't collect data "for future features" or "to improve services." Collect what you need, when you need it.

Users can see what data is collected and why, in-app

Explain data collection in plain language within the app—not buried in a legal document.

Users can export their data in a standard format

JSON, CSV, or PDF exports let users take their data elsewhere. No vendor lock-in.

Account deletion actually deletes all user data

"Delete my account" should mean delete—not "archive" or "anonymize."

No third-party analytics that build advertising profiles

Analytics that feed advertising networks turn your users into products. Find privacy-respecting alternatives.

Supports current OS version and at least one version back

Users shouldn't be forced to upgrade their devices to keep using your app.

Crashes and data-loss bugs are prioritized and fixed promptly

Bugs that affect user data or stability come before new features.

App status and future plans communicated honestly

If development is paused or the app is being sunset, users deserve to know.

Users not forced to pay more to keep features they already have

Moving existing features behind a paywall breaks the implicit contract with users.

Working features not removed without a migration path

If a feature must go, help users transition. Don't just pull the rug.