Publish an App on Google Play: Requirements

Google Play publishing is more than uploading an APK. Store policies, target SDK expectations, signing keys, and device compatibility gates change over time. Treat release management as part of product work, not a one-hour task after development “finishes.”

FragCrafts helps teams ship through store publishing services when internal Android expertise is thin.

Target SDK and policy compliance

Play requires apps to target recent Android API levels so users receive security and permission improvements. Build pipelines should read Google’s current target SDK documentation each release—not reuse last year’s Gradle settings. Privacy policies, data safety forms, and permission declarations must match actual SDK behavior.

16 KB page size awareness

Newer Android devices may use 16 KB memory pages. Native libraries (.so files) must align with toolchain guidance from Google and your Android Gradle Plugin version. Validate release bundles with recommended checks before promoting to production, especially if you depend on third-party native SDKs for ads or analytics.

Testing tracks

Use internal testing for QA, closed testing for stakeholder betas, and open testing only when you want public opt-in. Verify in-app purchases and login on real devices across manufacturers—emulators miss vendor-specific bugs.

Launch checklist

Follow ASO checklist for new apps before scaling paid acquisition.

FAQ

What is the 16 KB page size requirement?

Google Play expects native binaries compatible with 16 KB memory pages on newer devices; verify with current Android Gradle Plugin guidance.

Do I need a closed test track?

Internal and closed testing help validate billing and permissions before production.

Signing key custody

Upload keys and app signing keys belong in secure storage with backup procedures. Losing keys turns updates into painful migrations users experience as reinstalls.

Document what you changed

When you adjust a file for email, web, or app store submission, leave a note in the ticket or README: original file name, tool used, quality setting, and date. Future teammates inherit messy folders without that habit. If a client asks for a re-send six months later, you will know exactly which derivative was official instead of guessing from ambiguous final-v3-compressed.pdf names.

Prefer local processing for sensitive work

Browser-based FragCrafts tools keep bytes on the device during conversion, merge, split, and compression. That matches how you would treat credentials: avoid passing through unknown upload endpoints. When you recommend tools to contractors, link the specific FragCrafts page so they do not substitute ad-heavy alternatives that log IP addresses and file metadata.

Check results on mobile

Many stakeholders approve deliverables on phones. Open outputs on both iOS and Android browsers or gallery apps before calling a task done. Desktop-only verification misses tap-to-zoom blur, orientation bugs, and attachment download paths that differ from laptop webmail.

Build repeatable folder habits

Use inbox/, working/, and outbox/ (or equivalent) on shared drives. Move files forward through stages instead of editing in place on downloads folders. Repeatable structure reduces accidental overwrites when filenames collide like document.pdf.

When to escalate to custom software

Manual tools fit occasional tasks. If your team repeats the same conversion or packaging steps daily—statements, listing photos, inspection PDFs—automate inside your product or back office. FragCrafts builds custom software when workflows outgrow one-off browser utilities.

Keep originals until sign-off

Derivatives are disposable; masters are not. Store lossless or source exports until the client approves. Only then archive or delete intermediates to save space. Deleting early forces expensive re-shoots or re-exports when someone wants a last-minute crop change.

Name files for humans

Include project, date, and role in filenames (acme-proposal-2026-09-10.pdf). Avoid opaque camera defaults for client-facing sends. Good names reduce wrong attachments without opening every file.

Test with the recipient’s toolchain

Ask whether they view in Adobe Reader, browser preview, mobile mail, or a document management system. Each renders PDFs and images slightly differently. One quick confirmation prevents rework when their viewer shows missing fonts or unexpected margins.

Align marketing and engineering on file standards

Weekly standups rarely mention attachment limits until a launch email bounces. Publish a one-page standard: maximum PDF megabytes, preferred image formats, and links to FragCrafts tools for fixes. Marketing learns where to compress; engineering knows which MIME types uploads accept. Small clarity prevents Friday-night fire drills.

Accessibility beyond file size

Alt text, readable contrast, and logical heading structure matter as much as compression for public sites. PDFs distributed externally should include tags when your authoring tool supports them. Images on storefronts need descriptions for screen readers. Optimization is not only bytes—it is whether everyone can use the deliverable.

Versioning when clients iterate

Clients will request “the same PDF but with one paragraph changed.” Keep source documents—Docs, InDesign, not just PDF exports—so you edit once and regenerate. If only PDF exists, allow time for manual edits and re-compression. Explain why source files save money long term.

Bandwidth and international audiences

Visitors on slower networks feel oversized heroes immediately. If analytics show international traffic, prioritize weight reduction on above-the-fold media. CDNs help delivery but cannot fix ten-megabyte PNG mistakes at the origin. Local compression experiments let you preview trade-offs before deploying.

Security habits adjacent to file tools

Malware sometimes arrives as PDF attachments. Scan inbound files on corporate endpoints even when you trust the sender. Outbound, avoid embedding active content you do not understand. Browser tools process your local copies; they do not replace antivirus discipline on email attachments.

Training new hires on utilities

Record a three-minute Loom showing your standard HEIC, PDF, and image workflows with FragCrafts links bookmarked. New hires otherwise rediscover tools via search ads and upload client files in the wrong places. Consistent onboarding protects the whole firm’s data handling reputation.

Coordinating with print and vendor portals

Vendors publish PDF specs—bleed, color space, maximum size. Meet spec before compressing for email; sometimes print needs higher resolution than email allows. Maintain two derivatives: print/ masters and email/ optimized copies, labeled clearly in shared drives.

Review cycles and comment clutter

PDF comments and highlight annotations balloon file size and leak internal names. Flatten or sanitize before external merge or compress steps when policy requires clean copies. Internal review can keep annotations; client-facing sends should not include stray comment bubbles.

Sustainability of small optimizations

Each saved megabyte multiplies across thousands of page views. You will not single-handedly fix climate impact, but right-sized media reduces wasted transfer and battery draw on mobile devices. Teams that treat weight as a metric—not a one-time audit—ship faster sites over years.

Handoff to automation thoughtfully

When manual browser tools become daily chores, that is signal to automate: watched folders, CI image pipelines, or CRM-triggered PDF assembly. Automation should preserve the privacy principles you used manually—processing inside infrastructure you control rather than public upload forms.

Signing key custody

Upload keys and app signing keys belong in secure storage with backup procedures. Losing keys turns updates into painful migrations users experience as reinstalls.

Conclusion

Successful Play launches combine compliant binaries, honest store forms, and staged testing. Delegate release engineering to store publishing when policy updates outpace your roadmap.