Connect Integration Best Practices
Initialization and Configuration
Always Provide a Manifest
Always Provide a Manifest
- Users see your app name and URL on their device
- Helps with trust and security
- Required for Connect to function properly
Initialize Once Per Session
Initialize Once Per Session
TrezorConnect.init() only once when your app starts:Handle Initialization Errors
Handle Initialization Errors
Error Handling
Always Check Result Success
Always Check Result Success
Implement User-Friendly Error Messages
Implement User-Friendly Error Messages
Handle Device States
Handle Device States
Security Best Practices
Never Request Private Keys
Never Request Private Keys
Verify Addresses on Device
Verify Addresses on Device
- Protects against malware showing fake addresses
- Users can verify the address on trusted device screen
- Critical for security
Validate Transaction Data
Validate Transaction Data
Use HTTPS in Production
Use HTTPS in Production
Performance Optimization
Batch Address Requests
Batch Address Requests
Cache Non-Sensitive Data
Cache Non-Sensitive Data
Implement Timeout Handling
Implement Timeout Handling
Suite Development Best Practices
Code Organization
Follow Conventional Commits
Follow Conventional Commits
Use TypeScript Strictly
Use TypeScript Strictly
Write Tests for New Features
Write Tests for New Features
Performance
Optimize Bundle Size
Optimize Bundle Size
Use React Best Practices
Use React Best Practices
Testing
Use Trezor User Env for E2E Tests
Use Trezor User Env for E2E Tests
Mock External Dependencies
Mock External Dependencies
Documentation Best Practices
Document Public APIs
Document Public APIs
Keep README Updated
Keep README Updated
- Add to feature list
- Update setup instructions if needed
- Include usage examples
- Update dependencies section
Write Helpful Error Messages
Write Helpful Error Messages