|This article or section may not have content matching Scratch Wiki editing standards. Please improve it according to Scratch Wiki:Guidelines and Scratch Wiki:Editing Conventions. (March 2019)|
|This article is a stub. It may be incomplete, unfinished, or have missing parts/sections. If the article can be expanded, please do so! There may be suggestions on its talk page. (June 2020)|
Running Scratch Projects on smartphones or other mobile devices was a highly demanded feature. Since its beta, Scratch 3.0 does not need Adobe Flash (which mobile devices don't have) and is mostly compatible with mobile devices.
Why Scratch on Mobile?
Some users prefer touching the screen while coding or viewing projects rather than using a mouse or mousepad. Many users are also interested in writing apps for their mobile devices.
Typical Scratch projects use a small screen resolution and are not particularly long, which would usually fit the criteria of a mobile device quite well.
No Sensor Access
Scratch currently does not have any blocks for reading data from the sensors in mobile devices. As an example, built-in tilt-sensors (gyro and accelerometer) are often used to let the user control the game by moving or tilting their device. For example, users can steer an in-game character like this. Scratch programmers would have to go without using these types of interaction. Another big caveat is the lack of a physical keyboard on most mobile devices. Unless the user can connect an external keyboard, there is no way to press specific keys while running a project.
Due to safety concerns, Scratch does not offer any networking except for cloud variables. While this is a positive aspect regarding security, it makes it impossible to connect with any other networking-capable programs/apps without difficult workarounds.