Resources & guides

Dependency update checklist

1. Pin current versions (lock file committed).
2. Read changelogs for breaking changes.
3. Update one group at a time: build tools first, then UI libraries, then the rest.
4. After each group run the full test suite and manually check key journeys.
5. Record in the decision log what was updated and why anything was deferred.

Mobile release readiness

• Version and build numbers incremented
• Build signed with the correct certificate
• Data declarations checked against current SDKs
• Screenshots match the current interface
• Reviewer test account is valid
• Rollback plan: previous build available

How to write a useful bug report

A good report saves days. Include: what you did (steps), what you expected, what happened, device/browser and app version, time with timezone, a screenshot or screen recording. Never send passwords — we never ask for them.

Accessibility minimum for any interface

• Everything reachable by keyboard, focus visible
• Text contrast at least 4.5:1
• Every field has a visible label
• Errors explain how to fix them
• Motion turns off with "reduce motion"
• Images have text alternatives

Glossary for product owners

Technical debt

Deferred improvements that make future changes costlier.

CI/CD

Automated build, verification and deployment of changes.

Target API

The Android version an app is built for; Google Play periodically raises the minimum.

Staged rollout

Releasing an update to a share of users first.