Removed duplicate words: puzzle (already in title/subtitle), water (already in title/subtitle), sort (already in title/subtitle), games (already in title/subtitle)
DriveCode Studio
Free ASO Developer Tools
Deterministic utilities to pack keywords, eliminate rejection risks, and optimize app store metadata without guessing.
iOS Keyword Field 100-Byte Packer
Apple limits the keyword field strictly to 100 bytes (UTF-8). This tool removes spaces, eliminates cannibalization from Title/Subtitle, and handles multi-byte Cyrillic characters.
37 / 100 bytes (37 chars)63 bytes remaining
Optimized Packed Keyword String
relaxing,logic,brain,zen,liquid,tubes
Metadata Policy & Rejection Guard
Instantly detect prohibited pricing terms ('free'), unverifiable claims ('best', '#1'), calls to action ('download now'), emojis, and rival platform mentions.
Found 4 policy blocker(s)
App Store Connect field limitBEST Water Sort 🔥 Free Download - also on Android
Title is 49 characters — the limit is 30
Cut 19 characters. App Store Connect will not accept the current value.
App Review Guideline 2.3.10android
Title names another platform: android
Remove "android". Apple rejects metadata referencing rival platforms — this is the most common rejection for cross-platform studios copying Play copy across.
App Review Guideline 2.3.7free
Title contains pricing language: free
Remove "free". Pricing belongs in the price field, and it wastes indexed characters.
App Review Guideline 2.3.1best
Title makes an unverifiable claim: best
Replace "best" with something specific and provable, or drop it.
Suggested Safe Replacement
BEST Water Sort 🔥 Free
Release Notes (What's New) Quality Checker
Catch generic boilerplate ('bug fixes and performance improvements') that can trigger app review rejections on significant releases.
5 words · 1 linesApp Review 2.3.12
Generic boilerplate detected
Apple and Google advise against generic phrases like 'bug fixes and improvements' for major updates. Name specific features, fixes, or optimizations.
Best Practices for Release Notes:
- Highlight 2–3 specific changes or fixes that directly benefit users.
- Keep the first 3 lines engaging — they appear before the 'More' truncation on mobile.
- Avoid generic boilerplate on major version bumps.