As Forge apps grow, performance and cost can drift quickly. This session shares a practical playbook for reading Developer Console metrics and optimising the services that most affect latency, reliability and spend.

We’ll cover high-impact patterns such as choosing the right renderer, filtering events at the manifest level, batching and caching storage operations, reducing noisy logging, tuning memory and using async consumers for heavier workloads.

Key takeaways

• Design for performance: Best practices to keep your Forge app fast — choose UI Kit over Custom UI where possible, tree-shake and minify bundles, batch storage calls, keep event handlers idempotent and quick, defer heavy work to async consumers and use narrow manifest filters so only relevant events reach your code.
• Keep costs under control: Understand which Forge usage drives spend, then reduce avoidable invocations and billable activity. Use Developer Console usage metrics and alerts, filter events in the manifest before functions run, batch and cache storage calls, tune compute memory and duration and keep production logging intentional.
• Tune the right levers: Each Forge service has controls that affect scale, performance and cost. So focus on the settings and patterns that reduce wasted resources, improve responsiveness and keep workloads predictable.