Olymp Trade App Download: Quick Reference
Download Sources at a Glance
Four routes exist and no more: the two official app stores, the operator own site for the Android package and the desktop app, and the browser platform that needs no download at all.
Nearly every problem on this topic traces back to where the file came from. Settle that first and the rest is routine. The table below is the whole of the source question, and there is nothing to add to it.
| Your device | Route | What the operator publishes |
|---|---|---|
| Android phone or tablet | Google Play | Google Play is the only Android store named |
| Android, without the store | The package on the operator own site | Size stated at approximately 40 MB |
| iPhone or iPad | The App Store | Availability stated on both iPhone and iPad |
| Windows or Mac | The operator main page | Both systems stated as supported |
| Anything else | The browser platform | Trading from any device, no install required |
Play Store and App Store
For most readers this is the answer and the rest of the page is background. The stores install the app, keep it current, and give you a listing you can inspect before tapping anything. Reach that listing through the operator own site rather than through a search result, so you are looking at the listing the operator points to.
The operator pages also mention the app being available in multiple stores without naming any beyond Google Play. This site does not fill in the missing names, because a guessed store name is exactly the kind of pointer that sends someone somewhere they should not be.
Direct APK
The operator publishes an Android package on its own site, at approximately 40 MB, for people who do not want or cannot use the store. It is a legitimate route on the operator own domain and nowhere else. It puts two things on you: a permission to grant during installation, and updating afterwards, since nothing will do that for you. Our pages on the APK download and installing it step by step cover both.
Desktop and web
The desktop client is supported on Windows and Mac, and the operator directs users to its main page for the current version. The browser platform is the same account opened as a page, with nothing installed and nothing to maintain. If you are undecided about installing anything, start there. Our comparison of the app and the web platform sets out the trade-offs, and the app versus a mobile browser does the same for phones.
If a download did not come from Google Play, the App Store or the operator own domain, it is not a file to install.
Install and Update Steps
Store installs need nothing from you beyond tapping install. The direct package needs a permission granted and then turned back off. Updates follow the route you chose.
Each route in one short procedure, in the order you would actually do it.
Standard installs
A store install is the shortest route and the one to use whenever it is available to you. The store deals with the file, the signature and the updates, which leaves you only the checks that a store cannot make on your behalf.
- Open the operator own site and follow its link to the store listing for your device.
- On the listing, check the publisher name matches the operator before anything else.
- Read the declared permissions on the listing and note anything that looks unrelated to trading.
- Install, then open the app and sign in, or register if you do not yet have an account.
- Confirm whether the app has opened on the demo balance or the real one before you place anything.
- Set your security options and your notification preferences while you are there.
Two or three minutes, and the checks in steps two and three are the ones that matter most. Our page on account setup in the app covers the first-run screens.
Sideloading the APK
Installing a package outside the store requires Android's permission to install unknown apps, granted to whichever browser or file manager is handling the file. That permission is not harmless: it lets that one app install software on your phone, which is why the system asks rather than assuming.
- Open the operator own site directly and confirm the address bar shows its domain before downloading.
- Download the package, which the operator states at approximately 40 MB.
- When Android asks, grant the install permission to the specific app handling the file, not broadly.
- The operator own page instructs users to continue when the standard warning appears; do that only once you have confirmed the file came from its domain.
- Tap Install and wait for it to finish.
- Go back into your settings and turn that install permission off again.
- Open the app, sign in, and review its permissions in your phone settings.
Step six is the one people skip. Leaving the permission on means the next thing that arrives through that app can install too, and there is no reason to leave it open once you are done.
Staying updated
- Store installs: enable automatic updates in your store settings once, then forget about it.
- Direct package: nothing updates it, so return to the operator download page periodically.
- Desktop: fetch the current version from the operator main page when you want to refresh it.
- Browser platform: nothing to do, since you always get what is currently served.
Updates on a financial app carry security fixes as well as changes you notice, which is why the direct-package route deserves a calendar reminder. Our page on keeping the app updated covers both cases in full.
If you sideload, turn the install permission back off immediately afterwards, and remember that a directly installed build never updates itself.
Requirements Checklist
Very little about requirements is published, so the honest checklist points you at the store listing on your own device, which states them precisely for that device.
This is the section where invented numbers are most common across the web. No minimum operating system version, no memory figure and no installer size beyond the Android package appears on the operator own pages, so none appears here as fact.
Android and iOS: where the requirement is stated
Your own store listing is the answer, and it answers for your device rather than in general. Open Google Play or the App Store, search for the app, and read what the listing tells you. If the store will not offer the install, that is usually the requirement speaking, and no amount of trying again will change it.
- A reasonably current operating system is the practical expectation.
- The listing states compatibility for the device you are holding.
- A device too old for the app can still use the browser platform.
- Free storage matters as much as the version, since a full phone fails installs.
Windows and Mac: what is and is not published
The operator states that both Windows and Mac are supported and points users to its main page for the current desktop version. It markets the desktop app as fast with minimal memory use, which is its own description rather than a measurement anyone has published. No minimum system version and no installer size is given for either build.
If your computer is old enough that this is a genuine question, the browser platform removes it entirely, since it runs in the browser you already have.
Storage
The Android package is stated at roughly 40 MB. Installed size is normally larger than the download, because app data and cache build up with use. That growth is ordinary and manageable: clearing cache from your phone settings frees space without touching your account, which is held on the platform rather than on your handset.
If free space is tight enough that 40 MB is a decision, use the browser platform on that device. A phone at capacity generates install failures, update failures and crashes that look like app faults and are not. Our page on storage and performance covers the housekeeping, and system requirements covers what can and cannot be established.
Read requirements from the store listing on your own device, and treat free storage as part of the requirement rather than an afterthought.
Safety Checklist
Five habits cover nearly all of the practical risk: right source, checked listing, reviewed permissions, closed install permission, and an account protected independently of the device.
The risk on this topic is rarely the app itself. It is installing something that resembles it. These checks take a couple of minutes in total and they generalise, so they work the next time you install anything financial.
Official sources
Everything else in this checklist is secondary to this first item. A file from the right place with unchecked permissions is a minor problem; a file from the wrong place with everything else done carefully is still a file you cannot verify.
- Start at the operator own site and follow its links, rather than starting at a search result.
- Confirm the address bar shows the operator domain before any download begins.
- Install only from Google Play, the App Store, or that domain.
- Treat a link that arrived in a message, a group chat or an advert as a reason to go to the site yourself instead.
That fourth point is the one that catches experienced people, because a convincing link arrives at a moment when you were already going to install.
Fake-app checks
Imitation listings exist for popular financial apps as a category. Reading the listing rather than the icon is how you tell:
- Publisher or developer name, checked against the operator rather than against the app name.
- Listing age and history, since a brand-new listing for a platform operating since 2014 is a warning.
- Declared permissions, weighed against what a trading app plausibly needs.
- Review patterns, where a large number of near-identical short reviews is a signal worth heeding.
- Anything that does not match: close it and reach the listing again from the operator site.
Our pages on official versus fake apps and aggregator risks go through both patterns properly. On aggregators the reasoning is structural rather than an accusation: a copy of an installer hosted by a third party cannot be verified by you, and an altered file carries no warning label.
Permission review
The operator does not publish the permission list its app requests, so no page can hand you an authoritative one. Reading them yourself is better information anyway, because it reflects the build actually on your phone.
- Open your phone settings, find the app, and open its permissions.
- Ask of each one whether trading needs it.
- Revoke anything you are unsure about; the app will ask again if it needs it.
- Repeat after a large update, since a new build may request more.
- If you sideloaded, confirm the install permission you granted has been turned back off.
Alongside the device, protect the account: a password used nowhere else, two-factor login if your account offers it, and a deliberate sign-out on any machine that is not yours. Our page on app permissions and data safety covers the detail.
Right source, checked publisher, reviewed permissions, install permission closed again, and a password used nowhere else.
Fixing Common Problems
Most download and install failures come from a small set of causes. This table matches the symptom to the thing worth checking first, so you spend a minute rather than an afternoon.
Work down the table to the row that matches what you are seeing. Each row names what to check, not what the platform is doing, because the cause is usually on the device rather than on the platform.
| Symptom | Most likely cause | What to check first |
|---|---|---|
| Download stops partway or never finishes | Connection dropping, or no room for the file | Free storage, then retry on a stable network |
| Store will not offer the install | Device compatibility or storefront | What the listing states for your device |
| Install fails at the end | Insufficient free space, or a partial earlier install | Free space, then remove any previous copy and retry |
| Android blocks a downloaded package | The install permission was not granted to that app | The install-unknown-apps setting for that browser or file manager |
| App installs but will not open | An interrupted install, or a device very short of memory | Restart the device, then reinstall from the same source |
| App closes during use | Free memory or storage under pressure | Close other apps, clear cache, check free space |
| Sign-in fails on one device only | Something local to that device or client | Whether the same credentials work in the browser platform |
| Balance looks wrong on a second device | Being on the demo balance rather than the real one | The balance mode indicator, before anything else |
| App feels out of date | Installed directly rather than from a store | Whether automatic store updates are on, or fetch a current package |
Failed downloads
Before working through anything below, restart the device once. It is the least interesting piece of advice on this page and it resolves more cases than any other single step, because it clears the temporary state that most partial installs leave behind.
A download that stalls is almost always the network or the free space, in that order. Retry on a stable connection, clear enough room for the file plus headroom, and start the download again from the beginning rather than resuming a partial one. If the store itself is the problem, signing out and back into the store account resolves a surprising share of cases. Our page on download errors works through the specific messages.
Crashes
An app that will not open or closes during use is usually a device under pressure rather than a broken build. Restart the phone first, because it costs thirty seconds and fixes a real proportion of cases. Then check free storage, clear the app cache from your phone settings, and confirm the app is current. If it persists, reinstalling from the same official source is the next step. Our page on an app that will not open or keeps crashing covers the sequence, and installation problems covers failures that happen earlier.
Reinstalling
Reinstalling is safer than it sounds and it is the general fix for a client behaving oddly. Your account, balance and trade history are held on the platform, not on the handset, so removing the app does not remove any of them. What you lose is local settings.
- Make sure you know your sign-in credentials before you remove anything.
- Uninstall the app through your device settings or by holding its icon.
- Restart the device, which clears leftover state.
- Install again from Google Play, the App Store or the operator own site.
- Sign in, then confirm whether you are on the demo or the real balance.
- Set your notification and chart preferences again, since local settings do not survive.
Our guide to uninstalling and reinstalling covers the process in detail, and if the trouble is on more than one device, the multi-device page has the checks for that.
For anything specific to your account, the platform own support is the correct destination and the only party that can see it. If a genuine dispute is not resolved, the operator is a member of the Financial Commission, an independent dispute-resolution body, and has been since 22 February 2016. Its own wording is that you contact Customer Support first; if your issue was not resolved within 35 days and Customer Support did not escalate it, you can contact the Customer Service Executive team; and you may file a formal complaint with the Financial Commission within 45 days after the incident occurred. Note that the 45 days run from the incident rather than from the escalation, so record the date anything happens on the day it happens. The fund pays a maximum of 20,000 euros per proven claim, which is a ceiling rather than a guarantee, and the Financial Commission is not a regulator, not a licence and not deposit insurance.
Everything on this page was checked against the operator own pages at the time of writing, and where those pages say nothing, this page says so rather than guessing. Trading carries a risk of losing money. A clean install does not change that, but it does mean the platform is not the thing standing in your way. Getting started costs little: the minimum deposit is $10, trades start at $1, durations run from five seconds, and the free demo account holds 10,000 in virtual funds if you would rather practise first.
Match the symptom to a row, check free storage and the source before anything else, and reinstall knowing your account lives on the platform rather than the device.
Frequently asked questions
What is the fastest safe way to get the app?
Open the operator own site, follow its link to the store listing for your device, check the publisher name on the listing, then install. That sequence takes about a minute and removes almost all of the practical risk, because you never leave a source the operator points to.
Do I have to install anything at all?
No. The operator lists a browser platform described as trading from any device with no install required, and it opens the same account as any installed client. That route avoids every question about installers, sources and permissions, which makes it a sensible way to start.
What do I do after installing a package directly rather than from a store?
Turn the install-unknown-apps permission back off for whichever browser or file manager you granted it to, then review the app own permissions in your phone settings. Also remember that a directly installed build will not update itself, so revisit the operator download page from time to time.
The install keeps failing. What should I check first?
Free storage, then the network, then any previous partial copy of the app. Those three account for most failures. If the store refuses the install rather than failing partway, that is usually device compatibility, which the store listing states for your device.
Will reinstalling lose my account or my trade history?
No. Your account, balance and history are held on the platform rather than on your device, which is why signing in after a reinstall shows everything as it was. What you lose is local settings such as chart layout and notification preferences, so plan to set those again.
How do I know the listing I am looking at is the real one?
Check the publisher name rather than the app name, look at how long the listing has existed, and read the permissions it declares. Reaching the listing through the operator own site rather than through a search result is the single strongest habit, because it removes the question entirely.