Logging - Use a centralized class for all logging — NEVER use or raw - Define log levels: , , , , , - In dev flavor: log everything (verbose and above) - In staging: log info and above - In production: log warning and above only, route to Crashlytics - Include context in logs: - NEVER log sensitive data (passwords, tokens, PII) at any level Flutter DevTools - Use Widget Inspector to debug layout issues and identify unnecessary rebuilds - Use Performance Overlay ( ) to monitor frame rates - Use Timeline View to identify jank — target 16ms per frame (60fps) - Use Memory View to detect memory le…