Revision as of 05:48, 12 August 2019 by Congyingzhou (talk | contribs) (More clarification + hidden text revealed)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Document stub.png 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)

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?

Most young Scratch users use mobile devices frequently. Many are interested in writing apps for their devices.[citation needed]

Typical Scratch projects use a small screen resolution and are not particularly long, which some say[who?] fits the criteria of a smartphone app very well.

Limitations

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.

Networking Capabilities

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.