Exness Trading App

What the Exness app does

• Anything the app was told to announce arrives on its own initiative and does not wait for the screen to be looked at.
• Anything else is fetched when the app is opened, which means its age is the time since it was last opened rather than the time since it changed.
• A screen that has been left open sits somewhere between the two: it refreshes what it is showing and usually not what it is not.
• A phone that has been asleep has been fetching nothing, so the first screen after waking is the moment the catching-up happens.
• The short disagreement between a phone and another screen is almost always this catching-up in progress rather than two different figures.
• The disagreement closes on its own once both screens have asked the same question at the same moment.

Pushed and fetched are two different arrival times

Anything announced without being asked for travels on its own schedule: it is created somewhere, sent onward, and appears whether or not anyone is holding the phone. Its age is the time it spent in transit, which is short and roughly constant.

Everything else works the opposite way round. It is not sent at all; it is requested, and the request happens when the app is opened. Its age is therefore the gap since the last opening, which can be a minute or a week, and nothing about the figure itself indicates which.

This is why two people looking at the same account on two phones can see different things without either phone being wrong. They are not showing different data; they are showing answers to questions asked at different moments.

The screen you are looking at is the one being kept current

An open app is not refreshing everything it could refresh. It keeps the visible screen current because that is what somebody is reading, and it lets the rest go stale because nothing is reading it. Moving between screens is therefore itself an update event — not because the screens are slow, but because they only ask when they are shown.

Backgrounding the app is the extreme version of this. A phone that has been in a pocket has asked for nothing at all, and every screen inside it is exactly as old as the moment it was put away. The first thing that happens on reopening is a burst of catching-up, and that burst is visible as figures moving on their own for a second or two.

None of this is unique to a phone; it is simply more noticeable on one, because phones spend most of their existence closed and desktops spend most of theirs open.

Why two screens disagree, and how long for

A short disagreement between a phone and another screen is the ordinary case rather than an anomaly. One of them fetched an answer at one moment, the other fetched an answer at a different moment, and in between something changed. Both are accurate reports of the moment they were taken.

The way to settle it is not to decide which screen is right but to make both ask at the same time. Refreshing both and comparing the results afterwards resolves nearly every instance, and if a difference survives that, it is a genuine difference rather than a timing artefact.

The one figure where this matters most is any figure that moves continuously, because a stale reading of something that moves looks precisely like a fresh reading of something that has moved. Anything static — a name, a setting, a completed record — cannot produce this confusion at all.

Reading an age instead of a number

The useful habit is to ask how old a figure is before asking whether it is right. On a phone the answer is usually the time since the app was last opened, and that is a question about your own behaviour rather than about the account.

Announcements are the exception and are worth treating as a separate class. They are the only things whose arrival time is independent of attention, which makes them the only reliable indication that something happened while nobody was looking.

Everything else follows one rule: a phone knows what it last asked about. Opening it is asking; leaving it closed is not asking; and the difference between those two is the entire explanation for most of what looks like inconsistency.

Settling a disagreement between two screens

1. Ask how old each reading is before asking which is correct. On a phone that is the time since it was last opened.
2. Refresh both screens and compare afterwards, rather than comparing a fresh reading with one taken earlier.
3. Treat a screen that has just been reopened as still catching up for a moment; figures moving on their own are the catching-up, not a change.
4. Separate announcements from everything else. Only they arrive without being asked for, and only they indicate something that happened while nobody was looking.
5. For anything that moves continuously, take both readings within the same short interval or accept that they describe different moments.
6. For anything static, stop looking for a timing explanation — a name or a completed record cannot go stale this way.

This page is about when information reaches a screen, not about what the app can do. Current figures always come from the account itself.

What arrives on its own and what waits to be asked

Only the middle two rows can produce a disagreement, and both close by themselves once each screen has asked again.

Related Exness pages