In this article
A mini app can ask to read how the phone is being held and moved — tilted forward, rolled sideways, turned around, shaken. Grant it and you can steer a game by leaning, or look around a photograph by turning the handset.
It is also the one permission on this list that says almost nothing about you, which makes it the one worth understanding rather than refusing on reflex.
What you will be able to do
- check_circle Say what a motion permission actually hands over.
- check_circle Tell which apps have a reason to ask for it.
- check_circle Know why it does nothing on a computer.
- check_circle Judge what it costs in battery and heat.
The picture follows the handset rather than a finger — the phone itself has become the controller.
sensors The permission that does not describe you
Most of what an app can ask for is a fact about your life. Location says where you are standing. Contacts say who you know. A photograph says what your room looks like. Motion says which way a piece of glass is currently pointing, and that is a category apart: there is no version of it that identifies you, finds you, or survives being written down.
That matters because the sensible habit of refusing everything has a cost here. The apps this permission exists for — a driving game you steer by tilting, a room you look around by turning, a ball you roll through a maze — simply do not work without it, and there is nothing to be gained by making them fail.
It is not quite nothing, though. A continuous, fast stream of movement is still a record of how a person was moving, and a mini app that is not animating anything on screen has no reason to want one. The useful question is not whether the data is sensitive but whether the app has anything to do with it.
What is the app actually reading?
Two things, both about the handset rather than about you. Orientation is which way it is facing — tilted forward or back, rolled left or right, turned around like a compass needle. Acceleration is how it is being moved: a flick, a shake, a swing. Between them they describe a piece of hardware in space, and nothing else.
Why did my iPhone ask and my friend's Android did not?
Because the two systems disagree about how freely a web page should be able to read motion, and a mini app is a web page. On iPhone a page has to ask before it can listen, so you get an explicit prompt the first time a motion-driven app starts. That is a rule of the operating system rather than something Telegram chose, which is also why the wording does not look like the rest of the app.
The tilt controls do nothing on my computer.
A laptop has no gyroscope to read. A well-built mini app checks for that and offers something else — dragging with the mouse, the arrow keys, an on-screen stick — because the check is straightforward to make. One that simply does not respond was written for phones and never tested anywhere else, which is worth knowing about a developer before you spend anything inside their app.
Does it drain the battery?
Sampling a sensor many times a second is real work, but it is small next to what is happening around it. If a motion game runs your phone warm, the heat is coming mostly from the screen at full brightness and from drawing a moving scene, not from the gyroscope. The honest version is that these apps cost about what any game costs, and that they stop costing it the moment you leave.
When is it worth granting?
When movement is the control. Steering, aiming, looking around a panorama, holding a view steady over the real world — in all of those the permission and the point of the app are the same thing. When the app is a shop, a form, a wallet or a dashboard, there is nothing on screen for your wrist to move, and a request for motion access in that context is a question worth not answering.
Can I take it back afterwards?
Leaving the app ends the stream immediately, which covers most of what people mean by the question. For a longer-term answer, the permission belongs to that particular mini app rather than to Telegram as a whole, so removing the app from your attachment menu and not opening it again closes the door properly. Nothing you granted to one app carries over to another.
sports_esports What good motion control feels like
The difference between a novelty and something you keep playing is almost entirely about how much movement is required. A game that asks for a gentle lean can be played on a sofa, on a train, in a waiting room. A game that asks you to swing the phone can be played almost nowhere, because people are rarely alone and rarely want to look like that.
The second mark of a good one is that it lets you recentre. Your comfortable holding angle is not flat, so an app that treats flat as neutral will feel wrong from the first second and keep drifting afterwards. Being able to set "this is straight ahead" wherever your hands happen to be is the difference between a control scheme and a fight.
settings Using it sensibly
- Ask what is supposed to move If nothing on screen does, decline.
- Accept the system prompt on iPhone It is the operating system asking, not the app.
- Recentre before you start Hold the phone the way you actually will.
- Expect a fallback on desktop Its absence says the app was never tested there.
- Treat the heat as a game, not a leak The screen costs more than the sensor.
- Leave to end it The feed does not survive the app being closed.
This page is one thing a mini app can reach for. The curriculum step is the boundary it sits inside: what a mini app is underneath, what the client will and will not hand it, and where Telegram stops and a developer's server begins.
At a glance
- 1Motion sensors
Tilt and movement data about the device only.
- 2Who needs it
Games and visual effects; others should not ask.
- 3Only while open
It stops when you close the app.
Updated
