Expand Startup Lazy Loading

📋 Summary

Improve LaunchBox startup responsiveness by deferring more non-essential systems until after the main interface is usable.

❗ Problem

LaunchBox can take longer to start on large or complex setups, especially when many systems, media files, plugins, or online services are involved.

When too much work happens before the UI appears, users may feel like LaunchBox is frozen or stuck, even if it is still loading in the background.

💡 Proposal

Load only the core data needed to show the main interface first, then continue loading secondary systems in the background.

Potential candidates for deferred loading could include:

• Media caches

• Non-visible views or panels

• Related games or discovery data

• Online service checks

• Plugin initialization where safe

• Optional background services

🧩 Use Cases

• Large libraries reach the main interface faster

• Users can begin browsing before every secondary system is ready

• Background loading remains visible after startup

• Slow startup components become easier to identify

📦 Benefits

• Faster perceived startup time

• Fewer cases where LaunchBox appears frozen

• Better experience for large libraries

• More modern and responsive startup behavior

⚠️ Considerations

Some features may need to remain temporarily unavailable until their background loading completes. Startup messaging should also clearly show what is still loading.