Recommended Free Tools
An indie game is ready to ship when one frozen release candidate has passed functional, compatibility, performance, accessibility, localization, online-service, store, and recovery checks on every supported platform. Record each check as pass, blocked, or untested; close or explicitly waive every blocker and critical defect; then smoke-test the exact package players will download.
The checklist below turns that decision into a repeatable release process rather than a last-minute playthrough.
As an Amazon Associate I earn from qualifying purchases.
1. Freeze and identify the release candidate
Do not run a final pass against a moving target. First freeze one named build: a version number, changelist, or source-control hash. Record the build ID, target platforms, test environment, tester, date, result, and links to related bugs. If the build changes, mark which checks must be rerun instead of assuming the previous results still apply.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRelease-candidate record
- Build identity: version, changelist or commit hash, package name and upload time.
- Scope: supported operating systems, storefronts, languages, input methods and online features.
- Environment: device model, CPU/GPU tier, RAM, operating-system version, display, controller, audio device and network condition.
- Ownership: tester, date, result, bug IDs and the release owner who can waive a known issue.
- Change impact: a list of checks to repeat after any code, asset, configuration, backend or store-package change.
Keep functional testing separate from store, age-rating and certification checks. A game can be fun and stable while still failing a platform submission requirement.
2. Build a device and environment matrix
Test real hardware, not only emulators or simulated profiles. Apple’s pre-submission guidance specifically says to test on each device platform where the app could be used, rather than relying on simulated environments. Select at least the minimum supported specification and a representative high-end specification for every platform you claim to support.
| Matrix area | What to include | Minimum evidence to capture |
|---|---|---|
| Operating system | Every supported OS version and edition | Install, launch, suspend/resume and update result per OS |
| Hardware | CPU/GPU tiers, RAM, storage type and realistic free-space conditions | Frame pacing, memory use, loading and crash behavior |
| Display | Windowed, fullscreen, ultrawide, supported resolutions and aspect ratios | Scaling, safe-area, text readability and UI alignment |
| Input | Keyboard/mouse, each supported controller, touch and handheld controls | Detection, rebinding, disconnect/reconnect and focus behavior |
| Audio | Speakers, headphones, volume changes and device switching | Correct routing, subtitles and recovery after unplugging |
| Network | Offline, normal broadband, high latency, packet loss and reconnects | Timeout, retry, messaging and state consistency |
For Android, Google Play’s Pre-launch Reports exercise a range of devices and report stability, performance, accessibility, compatibility, and security or privacy issues. To become eligible, publish the game to a default closed or open testing track. Treat the report as an additional signal, not a substitute for your own minimum-specification hardware.
3. Run the functional and regression pass
Installation, launch and lifecycle
- Install from the same package players will receive, not a developer-only build.
- Perform a clean install, launch, quit, uninstall and reinstall.
- Apply a patch, then test rollback or recovery if the platform supports it.
- Interrupt the game during loading and saving; verify that it either resumes safely or reports a recoverable error.
- Test suspend and resume, alt-tab, display-mode changes, controller disconnect/reconnect and loss of focus.
Core loop and progression
Start with a new profile and play through the complete intended loop to late-game or end-state content. Verify every progression gate, unlock, quest and objective state. Exercise checkpoints, fail states, win states, pause paths, restart paths and any branching conclusion. A level that works in isolation can still break when entered through an unusual unlock order or after a reload.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Save, profile and migration behavior
- Autosaves and manual saves at safe points and during transitions.
- Cloud saves where offered, including upload, download and conflict handling.
- Missing, corrupted or incompatible saves with a clear recovery path.
- Multiple profiles or accounts and correct separation of their progress.
- Migration from an older build, including changed data, removed content and interrupted migration.
Menus, settings and economy
Open every menu and setting. Test tutorial prompts, inventory actions, purchases, rewards, currency changes, confirmation dialogs and cancellation paths. Check rebinding, audio and video settings, language selection, difficulty or assist options, and whether settings persist after restarting. Regression-test every fixed high-severity defect and every system touched since the previous build; do not limit regression to the feature that visibly changed.
4. Test performance, stability and recovery
Measure more than an average frame rate. Record frame pacing and low points, loading times, memory use, CPU/GPU utilization, thermal or battery impact on mobile, network latency and reconnect behavior, and degradation during long sessions.
Stress scenarios
- Many enemies, particles, physics objects and simultaneous NPC activity.
- Large streaming areas, rapid travel and asset-heavy transitions.
- Saving while audio, effects and background simulation are active.
- Repeated loading, death and restart cycles.
- Extended play sessions followed by suspend and resume.
- Nearly full storage where that condition is realistic for the target device.
Capture crash logs, device information, timestamps and reproducible steps for every failure. Platform sources do not define one universal crash-free rate, frame-rate floor, bug count or tester count for every genre and device. Set ship-blocking thresholds for your game’s risk profile, document who approved them, and apply them consistently to the named release candidate.
5. Verify accessibility and usability
Accessibility is a functional requirement, not a metadata claim. Test the features you intend to advertise on the target devices and with the actual shipped build.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Readable text at every supported size, with sufficient contrast and no information conveyed only by color.
- Captions and subtitle timing, speaker identification, audio controls and independent volume channels where provided.
- Controls for screen shake and flashing, plus a safe response to photosensitive-risk settings.
- Full remapping, hold-versus-toggle choices and sensible defaults.
- Difficulty or assist options that preserve progress and do not trap the player in a menu.
- Predictable menu focus order and navigation without a mouse where relevant.
- Recovery after input loss, controller replacement or an interrupted accessibility setting change.
On Apple product pages, developers can declare support for VoiceOver, Voice Control, Larger Text and Captions; those declarations create an Accessibility Nutrition Label. Claim only capabilities that were tested on the devices and OS versions you support.
6. Check localization and shipped content
Switch languages on a fresh profile and during an existing save. Check every supported language for truncated strings, missing translations, font fallback, text overflow and right-to-left layout where applicable. Verify date and number formatting, subtitles, voice-over selection, images containing text, controller prompts, achievements, store text and legal notices.
Maintain a content inventory that lists each piece of text, voice, image, achievement, tutorial and legal copy. Recheck it after late edits so new material is not left untranslated or absent from age-rating declarations.
Age-rating review
Answer rating questionnaires against the content that will actually ship. Reconfirm violence, gambling-like mechanics, user interaction, purchases and online communication. A changed reward system, chat feature or cutscene can invalidate an earlier rating even when the executable itself appears stable.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match7. Exercise online, multiplayer and service failures
Test the complete account and entitlement lifecycle, including failure paths:
Rank #4
- Account creation, sign-in failure, expired sessions and sign-out.
- Entitlement restoration, purchases and a missing or delayed receipt.
- Invites, matchmaking, host migration, reconnects and version mismatch.
- Region and language settings, chat, reporting and moderation controls.
- Maintenance and outage messaging, full servers and unavailable services.
- Poor latency, packet loss, deliberate disconnects and clock changes.
Confirm that analytics, crash reporting, privacy disclosures and consent behavior are correct in every supported region. Verify that a service outage cannot corrupt local progress or leave a player in an unrecoverable session.
8. Complete store, certification and release operations
Run the platform’s current requirements as a dedicated pass. For Steamworks, use the Game Build checklist and verify the release action: it publishes the store package, marks the game playable and released, and applies the release timestamp.
Store-package checklist
- Correct depots or packages, launch options, redistributables and permissions.
- Achievements, cloud saves and controller configuration.
- Price, regional availability and age rating.
- Screenshots, trailers, capsule art, description, support URL, privacy policy and contact information.
- Final store validation with no missing files, invalid metadata or blocked dependencies.
Apple’s submission guidance states that App Store distribution reaches 175 storefronts and 50 languages. It also requires privacy details for the app and integrated third-party partners. Apple reviews apps and updates for safety, security, reliability, metadata and in-app purchases. Run the final package through the store’s validation tools, then perform a clean-install smoke test from the uploaded artifact—not from a local development copy.
9. Use a focused beta instead of collecting vague opinions
Stage the testers
- Run an internal smoke pass covering install, launch, first-time setup, core loop, save, quit and relaunch.
- Invite outside players who match the target audience and the real hardware mix.
- Give each session a short charter covering onboarding, core loop, accessibility, performance and failure recovery.
- Review reports daily, reproduce them on the named build, and send fixes back through regression.
Apple’s TestFlight supports up to 100 internal testers and up to 10,000 external testers. Those are service limits, not a required tester count. A smaller, well-selected group that covers your platforms and player types is more useful than a large group that all uses the same device.
Best Value
Required bug-report fields
- Build number or release-candidate ID.
- Device model, OS version, input device and network condition.
- Exact reproduction steps and frequency.
- Expected result versus actual result.
- Screenshot, video, save file or log when available.
- Severity and whether progress, purchases, privacy or safety are affected.
10. Triage defects and make the ship decision
| Severity | Definition | Release treatment |
|---|---|---|
| Blocker | Prevents launch, installation or progression, or corrupts progress | Must be fixed before release |
| Critical | Core-loop failure, severe crash, security issue or store-rejection risk | Close or explicitly waive by the release owner |
| Major | Substantial feature or device failure with meaningful player impact | Fix, defer with a documented workaround, or remove the affected claim |
| Minor | Localized, low-impact or cosmetic defect | Prioritize against risk and available time |
| Polish | Presentation improvement without functional harm | Track separately from ship blockers |
For every accepted known issue, document affected platforms, player impact, workaround, owner and follow-up plan. Ship only when blockers and critical issues are closed or explicitly waived, required platform checks pass, and the final uploaded build receives a clean smoke test. The release owner should sign the pass, blocked and untested list so an untested area is never mistaken for a pass.
11. Know when outside QA is justified
Bring in an independent game-QA team when your staff cannot cover the supported device matrix, long-session performance, multiplayer edge cases, accessibility or certification requirements. External coverage may include gameplay, performance, compatibility, multiplayer, monetization and App Store or Google Play policy testing.
Before engagement, verify the exact scope, target platforms, confidentiality terms, turnaround, reporting format and current partner terms. Keep ownership of the release decision: an outside report expands coverage, but your team still defines acceptable risk and confirms the final candidate.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →12. Final release-candidate sign-off
- Freeze the candidate and record its exact identity.
- Mark every functional, compatibility, performance, accessibility, localization, online, store and certification check pass, blocked or untested.
- Close or formally waive blockers and critical defects with owner, impact and workaround documented.
- Upload the final artifact and run a clean-install smoke test from that artifact.
- Verify store metadata, ratings, privacy details, regional availability and release timing.
- Archive logs, test results, known issues, approvals and the rollback or recovery plan.
- Release only after the release owner signs the candidate; monitor crash reports, support channels and service health immediately afterward.
There is no universal published number of bugs, testers, crash-free sessions or frames per second that makes every indie game safe to ship. A defensible launch is one in which the supported experience, the known risks and the limits of your evidence are all explicit for one identifiable build.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
