Integration Best Practices & Anti-Patterns
Recommended Implementation Architecture
- Use infinite retry loops for connection issues
- Display detailed license information on successful validation
- Implement periodic checks (every 10 minutes)
- Create configuration file with default values
Unsafe & Prohibited Integration Patterns
- Disabling plugin on connection timeout
- Hardcoding credentials in source code
- Exposing error details to end users
- Running validation on main thread
Best practices questions
Should my plugin disable itself when verification times out?
No. NETWORK_ERROR, TIMEOUT, SERVER_ERROR and similar codes are transient: retry with backoff. Disable only on definitive rejections, or after several consecutive definitive failures in periodic checks.
Can license checks run on the main thread?
Never. Verify asynchronously on startup and re-check every 10 minutes off the main thread.
What is safe to log about licenses?
Detailed license info on success is fine. Never log license keys, HWIDs, or URLs, and never expose error details to end users.
Built by Ulises - Citymoon Dynamics