The One Dependency I Refuse to Add to Any RAXXO Tool

Description and use

The author refuses to add third‑party analytics SDKs to his tools to avoid extra user costs and data collection. He relies on server logs and support messages for insight, adding only minimal error reporting as an exception.

Problem

Adding third‑party analytics SDKs to tools introduces hidden costs to users and slows decision making for the developer.

Outcome

Tools remain lightweight and privacy‑respectful, but data collection is slower and less granular, leading to occasional uncertainty in feature decisions.

Workflow

• 1. Identify potential dependency
• 2. Ask what it costs the user (network call, cookie, permission)
• 3. Reject if it adds cost without user benefit
• 4. Use existing signals (logs, support, issues) for insights
• 5. Add minimal error reporting only when necessary

Evidence

I pulled the snippet the same day and wrote the rule down somewhere I would actually see it again: before adding a dependency, ask what it costs the person using the tool

Source

The exception is error reporting, and only error reporting: if a RAXXO tool crashes, it can send me the crash trace and nothing else

Source