UPDATE: Navigating Apple's New HTML5 Update

Last time, we unpacked Apple’s update in Section 4.7.4 of their guidelines, giving you a clearer path for HTML5 streaming in apps. We went hands-on with crafting an index file that meets Apple's standards without pulling your hair out. But guess what? We’ve got some important updates!

Quick Update!

In my last article, I mentioned that the index file for streaming HTML5 games had to be submitted with every build and hosted online. That was incorrect. Here’s the real deal:

Index File

This file only needs to be supplied to Apple when they request it. So, you don’t need to worry about submitting it with every build. Just have it ready.

Play It Safe

To avoid any hiccups, I'll be submitting this file with my first submission. Better safe than sorry, right?

Game Listings

Apple has now clearly stated that if you have all your games listed within the app (i.e., not showing a limited amount due to personalization or ML), then you’re in the clear. They just don't want hidden streaming games due to an algorithm. Keep everything transparent, and you’re good to go.

Recap: Simplifying Your HTML5 Game Index

To revisit our previous discussion, Apple’s index file requirement can seem like a lot of work. Listing your suite of mini-games with comprehensive metadata might sound like an intricate dance of details. But here’s how you should ideally format your index entries:

Name of Game: LissiLand Game Name X

Deep Link/Universal Link to the Game: This should drop Apple directly into the game

Real-World Examples

Here’s a couple of developers who nailed it:

• GamePortal's HTML5 Hub: A simple, straightforward list where each game title is a clickable link that leads directly to the game. No fuss, no muss.
• HTML5 Games Showcase: Another clean example, providing direct links embedded in each game’s title.

These examples show that simplicity not only helps with compliance but also makes for a better user experience. Direct links ensure reviewers can access your games without navigating through unnecessary complexity, which is key for Apple’s straightforward access requirement.

Final Tips

• PDF Submission: Initially, we talked about hosting this file online. But if your users need to sign in, scrap that. Since the file is by request only, make it a PDF that can be shared. To be safe, include this PDF file with your first submission to Apple.
• Avoid Search Engine and AI Indexing: Don’t index this file with search engines. If you're hosting it on a web server, consider hiding it. The best move is to list it in a document and attach it to your submission, along with test credentials and details.

Conclusion

As you prep your index file, make sure those Universal Links to your content is accurate. Keep it simple, compliant, and user-friendly. Let’s keep those apps rolling smoothly through Apple’s review process!

Have thoughts or questions on this approach? I’d love to hear from you at cbluford@lissiland.com. Let’s make sure your next app update is smooth sailing through Apple’s review process!