well if apple considers scratch real code then scratch would have to create every single output possible by-hand instead of it just reading and executing the code.

could say support, but to be fair, that is not going to happen.
the ST already tried to make a scratch APP for iOS in the past, and guess what: apple removed it from the app store due to that guideline!
proof: https://en.scratch-wiki.info/wiki/Scratch_Viewer
the idea is good, but apple wont let that happen. if you want a scratch APP for iOS, i suggest start to beg apple until they allow a scratch app.

patrovich wrote:

could say support, but to be fair, that is not going to happen.
the ST already tried to make a scratch APP for iOS in the past, and guess what: apple removed it from the app store due to that guideline!
proof: https://en.scratch-wiki.info/wiki/Scratch_Viewer
the idea is good, but apple wont let that happen. if you want a scratch APP for iOS, i suggest start to beg apple until they allow a scratch app.

I don't remember asking for an app. My cousin (@0invalid_name0), does Scratch on his iPhone! The reason I made this post is because I was at my Mim and Pipi's house and my Mim had an iPad, which I tried to do Scratch. But I was allowed to do hardly anything! (At least not anything useful) Thats because my Mim's iPad was very old and on a very old version!

XCraftYTLinc wrote:

patrovich wrote:

could say support, but to be fair, that is not going to happen.
the ST already tried to make a scratch APP for iOS in the past, and guess what: apple removed it from the app store due to that guideline!
proof: https://en.scratch-wiki.info/wiki/Scratch_Viewer
the idea is good, but apple wont let that happen. if you want a scratch APP for iOS, i suggest start to beg apple until they allow a scratch app.

I don't remember asking for an app. My cousin (@0invalid_name0), does Scratch on his iPhone! The reason I made this post is because I was at my Mim and Pipi's house and my Mim had an iPad, which I tried to do Scratch. But I was allowed to do hardly anything! (At least not anything useful) Thats because my Mim's iPad was very old and on a very old version!

oh, was it ipad 2/ipad 1/ipad 3/ipad 4/ipad mini 1 or 2/ipad air 1. makes sense.
also if you installed it prob said not compatible

Support, but apple rejected Scratch in the app store

Maybe there's a way for us to petition Apple to reconsider. Kind of like what Epic did, except without the lawsuit.

CZSuperboy wrote:

Maybe there's a way for us to petition Apple to reconsider. Kind of like what Epic did, except without the lawsuit.

I've said this before, but Apple rejected a Scratch Project Player, not a Scratch Editor. Apps that interpret code must allow the user to modify that code, and Scratch does. Apple does not need to reconsider.

But why did Apple reject it? I understand not allowing a C++ or even a Python editor (because those are easier to develop malware with), but Scratch? Scratch is harmless (and works more like a self-modifying JS application than an actual interpreter from what I've seen).

CZSuperboy wrote:

But why did Apple reject it? I understand not allowing a C++ or even a Python editor (because those are easier to develop malware with), but Scratch? Scratch is harmless (and works more like a self-modifying JS application than an actual interpreter from what I've seen).

Because it wasn't an editor, it was just a project viewer.

C++ and Python editors are allowed.

CZSuperboy wrote:

But why did Apple reject it? I understand not allowing a C++ or even a Python editor (because those are easier to develop malware with), but Scratch? Scratch is harmless (and works more like a self-modifying JS application than an actual interpreter from what I've seen).

Sololearn
Mimo
Codecademy
Etc

dhuls wrote:

Everyone, just stop with the Guideline thing. If ScratchJr. could get past it, then Scratch definitely can.

Scratch Jr and Hopscotch got past the guidelines because they aren't turing complete, so you aren't *really* writing code. Scratch on the other hand, is turing complete, and thus, is violating the guidelines.

reallysoftuser wrote:

dhuls wrote:

Everyone, just stop with the Guideline thing. If ScratchJr. could get past it, then Scratch definitely can.

Scratch Jr and Hopscotch got past the guidelines because they aren't turing complete, so you aren't *really* writing code. Scratch on the other hand, is turing complete, and thus, is violating the guidelines.

App Store Review Guidelines wrote:

2.5.2 Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps. Educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code provided that such code is not used for other purposes. Such apps must make the source code provided by the app completely viewable and editable by the user.

https://developer.apple.com/app-store/review/guidelines
No where does it say anything about Turing completeness

So in that case, wouldn't MS Word fall under that category? Extract a .docx file with 7-zip. It looks and behaves very similarly to a Scratch project. Word documents bevave like code, so why is Word allowed on the App Store? If malware/exploits is the primary reason, it's much easier to hide malware in a .docx than a Scratch project.

CZSuperboy wrote:

So in that case, wouldn't MS Word fall under that category? Extract a .docx file with 7-zip. It looks and behaves very similarly to a Scratch project. Word documents bevave like code, so why is Word allowed on the App Store? If malware/exploits is the primary reason, it's much easier to hide malware in a .docx than a Scratch project.

Can you just stop ignoring the fact that the rejected a player, not an editor?

Plus, the only Word files that could cause any harm are .docm (Word 2007 Macro-enabled document) and .dotm (Word 2007 Macro-enabled template) files. I don't think you can put macros in a standard .docx or .dotx.

The fact still remains that Word has the potential to cause harm to an iDevice.

dhuls wrote:

Can you just stop ignoring the fact that the rejected a player, not an editor?

I'm not ignoring this. I thought the whole point of this forum is to discuss why there isn't an editor. I'm also saying that it's incredibly anti-consumer to block an app that can help people to learn.

CZSuperboy wrote:

The fact still remains that Word has the potential to cause harm to an iDevice.

Word for iOS doesn't support macros (that was from 2018, but that has likely not changed)

CZSuperboy wrote:

I'm not ignoring this. I thought the whole point of this forum is to discuss why there isn't an editor. I'm also saying that it's incredibly anti-consumer to block an app that can help people to learn.

I don't see how a project player allows one to learn, unlike an editor.

Can it be on kindle, too?

dhuls wrote:

I don't see how a project player allows one to learn, unlike an editor.

I don't understand. I thought we were talking about an editor all along. I have no use for a player, therefore I am not in favor of an app like that.

tinycoder8675 wrote:

Can it be on kindle, too?

Yes, if you use this tutorial to install the Google Play Store.

ThatOneWeirdDude wrote:

garnetluvcookie wrote:

KittyFireSt0rm wrote:

garnetluvcookie wrote:

-snip-

They can change things.

Like what? What do you think they can change while still keeping scratch fairly the same?

Take away the sharing from the app, but the user can download the project and share it from there, similar to the PC/MAC offline editor.

Again, apple says that the user isn't even allowed to run code, so basically you want to remove the editor?

I use iOS to do Scratch and I found it pretty annoying that there’s no app

PyraEthan12 wrote:

I use iOS to do Scratch and I found it pretty annoying that there’s no app

Especially since Safari is pretty much the only browser that can run Scratch without lagging/crashing, and even then Scratch still lags and crashes. A native Scratch app for iOS would effectively mitigate this issue.