Scratch 3.0 has arrived, and with it, we are finally able to run projects on phones and tablets! But since they don't have a keyboard, how can we adapt projects to work using their specifications? Click or tap the 'Next' button to advance in the project, and interact with the examples. There are no keyboard inputs; this project is entirely mobile-friendly! #mobilefriendly #mobile-friendly #mobile-friendliness #tutorial #tutorials #scratch3 #compatibility
All the scripts are by me, and all art is by me except for the Scratch Cat and the scripts. The music is by me as well; you can find more of my music at https://scratch.mit.edu/projects/264397302/ . I've made an Engine Pack for making more mobile-friendly things, so please check out https://scratch.mit.edu/projects/309424414/ ! If you've made a mobile-friendly project, go visit the Mobile-Friendly Projects studio! And if you're looking for a mobile-friendly control scheme, visit the Mobile-Friendly Resources studio! Thanks everyone for getting this into the Top Loved row! (11-16 January 2019) Also thanks to the Scratch Team members , , , and for loving this as well. This project was created to advocate for mobile-friendly projects in the countdown to Scratch 3.0. I had been making a similar concept for about a year before sharing this, and fully realised the idea in the week before sharing. Any feedback is definitely appreciated! I know that the lines don't match up with the actual regions in the ball movement demo, but I couldn't work out how to make them line up. My Mobile Engine Pack contains an 8-directional movement script that works. (In an early version of this project, all the calculations were done off the origin, not the player's position, and the regions were shown in a backdrop.) Here's some notes on how mobile input works: The pointer's position is wherever the your finger was last, even if you're not touching the screen anymore. It's impossible to move the pointer without having the <mouse down> block activated. You also can only have 1 mouse input at a time, so pressing 2 buttons at once is impossible. It is possible to input text into [ask [] and wait] blocks.
