Publishing Updates
Update your published games.
Introduction
Update your published games. This page provides a complete guide to publishing updates in Appley, covering everything from setup to advanced techniques.
Publishing is a core area of Appley. Understanding publishing updates will help you build better games and use the platform more effectively. This documentation is designed for intermediate level users.
Requirements
Before working with publishing updates, ensure you have the following:
- A completed, tested game project
- An Appley account in good standing
- Game metadata (title, description, category, tags)
- A game thumbnail image
Estimated Completion Time
Step-by-Step Guide
Follow these steps to work with publishing updates in your Appley project:
Finalize your game
Ensure your game is complete, tested, and free of errors related to publishing updates.
Open the Publish dialog
Click the Publish button in Creator Studio to open the publishing wizard.
Fill in metadata
Enter the title, description, category, tags, and thumbnail.
Submit for moderation
Click Submit. The automated moderation system will review your game.
Go live
Once approved (usually under 1 minute), your game is live and playable.
FluxScript Example
Below is an Appley Scripting (Flux Scripting) code example demonstrating publishing updates:
// Publishing — Publishing Updates
on start {
checks = [
{ name: "Scripts compile", test: validateScripts },
{ name: "No missing assets", test: checkAssets },
{ name: "Scene loads", test: loadScene },
{ name: "Player can spawn", test: spawnPlayer },
{ name: "UI renders", test: checkUI }
]
passed = 0
for i = 0 to checks.length {
result = checks[i].test()
if result.ok {
passed += 1
print("OK: " + checks[i].name)
} else {
print("FAIL: " + checks[i].name + ": " + result.error)
}
}
if passed == checks.length emit("readyToPublish")
}Node Script Example
The same logic can be implemented using Node Scripting. Here is the equivalent node graph:
[On Start] ──► [For Each Check] ──► [Run Test]
├─ OK ──► [Print OK] ──► [passed++]
└─ Fail ──► [Print FAIL]
──► [Branch: passed == total] ──► [Emit "readyToPublish"]Interchangeable Systems
Common Mistakes
Avoid these frequent mistakes when working with publishing updates:
Publishing without testing on mobile
Always test in mobile preview before submitting.
Not filling in game description and tags
Complete all metadata fields for better discoverability.
Publishing games with smoke test failures
Fix all failures first — they indicate broken gameplay.
Ignoring age rating guidelines
Set appropriate age ratings to avoid rejection.
Troubleshooting
If you encounter issues with publishing updates, try these solutions:
Game was rejected by moderation
Game is not appearing in search
Cannot publish — button is disabled
Published game shows old version
Performance Tips
Optimize your use of publishing updates with these performance tips:
- Fill in all metadata fields — title, description, tags, and category improve discoverability.
- Add a high-quality thumbnail — it significantly impacts click-through rate.
- Test on mobile before publishing — touch controls must work.
- Use relevant tags that match your games genre and features.
Related Pages
Explore these related documentation pages:
Example Project
Download a complete example project demonstrating publishing updates:
