Progressive and Ordered Loading
The previous snippet assumes the game is made up of 128 separate items, all of the same priority. If the game includes a main UI, as well as separate sections for chat, the player’s inventory, and a market for players to exchange items, the player needs to wait for everything to load, even if they don’t care about today’s prices for Fizzblonium. The next step is to break up the game into components. Each section of functionality (UI, inventory, chat, market) will have all of the parts required for operation in its own load observable.
This way, each component of the game interface can decide what needs to be loaded for that component. Additionally, this would let us control the order that the app’s component parts ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access