Niyam Opens Faster Now

What changed

Niyam now loads quickly even after the app has been idle for an extended period. On cloud-hosted services, a gap in activity causes services to reduce their resource usage, and the next request has to wait while they return to full readiness. We have substantially reduced that wait across the parts of Niyam you interact with first: the sign-in flow, your matter list, your library, and the initial screens of Research and Draft. The result is that opening the app after a quiet period feels much closer to opening it in the middle of an active session.

This work focused specifically on the startup path — the sequence of steps that runs between you opening Niyam and the moment it is ready for your first action. By trimming unnecessary work from that path and making services return to activity faster, we reduced the gap between your intention to use the app and your ability to act on it.

How to use it

Nothing changes on your side. Open the app the same way you always do. The improvement is automatic and works in the background. You should simply notice that the app responds quickly from the start, including:

• First thing in the morning when you have not used Niyam since the previous day.
• After a long break during the working day — returning from court, a meeting, or a client call.
• When opening the app for the first time in a session on a different device.

If you previously had a habit of opening Niyam a minute early to let it load before you needed it, you should no longer need to do that.

Why it matters

A research and drafting tool earns its place by being ready when the need arises, not by being something you have to plan around. The previous cold-start behaviour created friction at exactly the wrong moments: when you returned to Niyam quickly before a hearing, when an unexpected question came up mid-task, or when you needed to look something up between calls. Small delays compound when a tool is part of your daily routine.

Faster cold starts also reduce uncertainty. When you do not know whether the app will load slowly or quickly, you adapt your behaviour to account for the worst case — opening it earlier than you need to, or hesitating before reaching for it. Once the app reliably opens quickly, you can use it without that calculation, which is the right relationship to have with a tool you depend on.

The change also removes a contributing factor in the intermittent sign-in errors that some users experienced. Making the authentication service start faster eliminates much of the delay that was causing timeout errors on first load.

Good to know

• This change reduces cold-start delays on our side. Total loading time still depends partly on your network connection. On a slow connection the app may still take a moment, but the delay introduced by our infrastructure is now much smaller.
• The improvement is most noticeable the first time you open the app after a gap. Once it is running actively, there is no material difference in how it behaves.
• This work pairs with the fix for intermittent sign-in errors. Together they make the first moments of using Niyam more reliable.
• We will continue monitoring startup times and looking for further improvements as usage patterns evolve.