Faster page loads and smoother motion

If FirstSales felt slower than it should when you moved between pages, especially ones you'd already visited, that's fixed. Pages now reuse the data they've already loaded instead of fetching it again every time, and the motion across the app has been tuned to settle faster and respect your system's motion preferences.

What changed

A number of pages across the app, including contacts, were quietly re-fetching the same data every time you navigated to them, even if you'd just loaded that exact data a moment earlier. Switching between a contact list and a contact's detail view, for example, could trigger the same request multiple times in a row. That's been rebuilt: pages now share and reuse data they've already fetched, so navigating back to a page you were just on doesn't mean waiting on a new network request for information that hasn't changed.

Alongside that, the motion used for page transitions and UI animations across the app has been tuned. Transitions use a stronger ease-out curve, which means animations decelerate more naturally and settle into their final position sooner, instead of drifting for an extra beat after you've already moved on. The practical effect is that the app feels like it's keeping up with you rather than catching up a moment later.

FirstSales also now honors your operating system's reduced-motion setting everywhere, not just in isolated parts of the app. If you have reduced motion turned on at the OS level, whether for comfort, a vestibular condition, or just personal preference, FirstSales scales back or removes animation across the whole product to match, instead of only respecting that setting in a handful of places.

The data reuse change is broad rather than limited to one screen: any page that shares data with another part of the app, a contact you view from your inbox and then again from your contacts list, a campaign you check from your dashboard and then again from the campaigns section, benefits from not re-fetching what's already been loaded recently. The overall effect compounds the more you move around the app in a normal working session, since most people don't visit a page once and never return to it; they go back and forth between a handful of screens throughout the day.

On the motion side, the stronger ease-out curve is a deliberate choice about how animation should feel, not just how long it takes. An animation that eases out sharply reaches its resting position and stays there, so your eye can move on to reading the actual content. An animation that lingers, even briefly, keeps drawing attention to itself after it's no longer useful. Tuning the curve toward a faster settle isn't about shaving milliseconds off a stopwatch, it's about the interface stopping short of being distracting.

How to use it

There's nothing to turn on for the data reuse improvement; it applies automatically as you navigate the app. You should notice it most clearly in places you move between frequently, like going from your contacts list into an individual contact and back, or switching between campaign views. Pages that already have fresh data load close to instantly instead of showing a loading state again.

The motion improvements are also automatic and apply across the app's page transitions and UI animations.

If you want FirstSales to reduce or remove animation, turn on the reduced-motion setting in your operating system: on macOS, that's under Accessibility settings for Display, and on Windows, it's under Ease of Access settings for Visual effects. FirstSales checks that system-level setting and adjusts its own animation to match, so once it's set at the OS level, you don't need to change anything inside FirstSales itself.

If you're the kind of user who keeps several FirstSales tabs open at once, contacts in one, a campaign in another, your inbox in a third, the data reuse change is where you'll likely notice the biggest difference, since switching between tabs that are showing related or overlapping data no longer means each tab re-fetches independently every time you bring it back into focus.

Why it matters

Repeated, unnecessary data fetching adds up fast in an app you use throughout the day. Every extra request is a moment you spend staring at a loading spinner for data you already had a few seconds ago, and it adds real load to the backend for no benefit. Fixing pages to reuse data they've already fetched means less waiting for you and less redundant traffic overall, and it's especially noticeable on pages you move in and out of a lot, like contacts.

Motion that lingers a beat too long after a transition, or animation that ignores a user's stated preference, is more than a cosmetic issue for some people. Motion that ignores a reduced-motion setting is an accessibility problem, not a matter of taste. Honoring that setting consistently across the whole app, rather than in a subset of screens, means FirstSales behaves the way you've told your operating system you want software to behave, everywhere in the product, not just in the places someone happened to remember to check.

Together, these changes are about the app matching your pace: less time waiting on data you already had, and animation that gets out of your way instead of holding up the next thing you're trying to do.

Neither change required you to clear a cache, update a setting, or do anything on your end to benefit from it; both apply the moment you load FirstSales after the release, and both are meant to be the kind of improvement you notice by the app simply feeling quicker and calmer to use rather than by reading about a specific number.

The combined effect is subtle by design: you're not meant to notice a specific animation curve, you're meant to notice that the app doesn't feel like it's lagging behind your clicks.

Availability

Both changes are live for all accounts and require no setup on your end, beyond your operating system's own reduced-motion preference if you want FirstSales to scale back animation.